Follow-up from T248570. Many MCS/PCS endpoints are designated as unstable or (more often) experimental despite having supported stable client releases for months or years. As a courtesy to current and prospective clients, we should audit the API endpoint stability designations for MCS & PCS.
**AC**
[x] Create a table of all current MCS/PCS API endpoints, with columns presenting their current stability designation, and whawith columns presenting their current stability they should have nowdesignation and proposed stability.
[] Create and deploy a RESTBase change updating endpoint stability designations as agreed based on the above chart
**Result **
| Endpoint | Current stability | Proposed stability
| -- | -- | --
| /page/mobile-sections[-lead, -remaining] | unstable | **deprecated **
| /page/summary | stable | stable
| /page/definition | stable | stable
| /page/mobile-html | experimental | experimental
| /page/mobile-html-offline-resources | none specified | **experimental**
| /page/media-list | experimental | **unstable**
| /page/talk | none specified | **experimental**
| /data/css/mobile | experimental | **unstable**
| /data/javascript/mobile | experimental | **unstable**
| /data/i18n/mobile | experimental | experimental
| /transform/wikitext/to/mobile-html | stable | stable