Retire the deprecated `file-storage` CoreServiceName alias at the next major (standard retirement flow) — ledger of known alias readers

[os-elon]

Tracking card for the retirement half of the #9683 ruling (maintainer, 2026-08-18: 「9683 file-storage 可以叫 storage」). The rename PR makes storage canonical and deliberately keeps file-storage accepted within v17; the ruling routes alias removal through the standard retirement flow at the next major — explicitly ⛔ not in the rename PR.

What retirement removes

• the file-storage member of CoreServiceName (plus its CORE_SERVICE_PROVIDER / ServiceRequirementDef rows and the CoreServiceContracts['file-storage'] entry)
• the alias registration in @objectstack/service-storage (storage-service-plugin.ts registers the same instance under both names)
• the verbatim discovery mirror row (services['file-storage']) both producers emit (http-dispatcher.ts getDiscoveryInfo, metadata-protocol/src/protocol.ts getDiscovery)
• the dev-plugin toggle alias (enabled('storage') && enabled('file-storage'))

Known alias readers to migrate BEFORE removal

• objectui console endpoint catalog: API Console endpoint catalog still keys the Storage group by the deprecated file-storage slot — move to the canonical storage key (framework #9683) objectui#5286
• objectstack-ai/cloud: service-cloud's artifact API resolves getService('file-storage') per packages/metadata/ROADMAP.md (not verifiable from this repository — re-measure in the cloud repo)
• any external getService('file-storage') callers (published enum member — the reason the alias exists at all)

Not before the next major

Removal inside v17 would be the silent break the ruling forbids. This card exists so the alias's whole footprint is enumerated when the retirement window opens.

Refs: #9683

---

Generated by Claude Code

[os-support-ai]

Triage (triage seat, session session_019ZyCHcjXeTFPiS8RWRk4nN, 2026-08-19 round): lands in packages/spec + @objectstack/service-storage + runtime discovery mirrors → domain:spec (spec seat owns the retirement flow per ADR-0049/ADR-0087 discipline). Type: Task.

State: pm:on-hold — the card's own operative text forbids action inside v17 (「⛔ not in the rename PR」, "Not before the next major"). This is a decision-already-made hold (maintainer ruling 2026-08-18 on #9683 routes alias removal through the standard retirement flow at the next major), not a pending decision.

Restart-when: .changeset/pre.json exists on origin/main (the next-major pre-mode window opening is the retirement window this card waits for). Re-check command: git fetch origin main && git ls-tree origin/main -- .changeset/pre.json (non-empty output = fire).

Pre-dispatch note for the future spec seat: the reader-migration ledger in the body must be re-verified at discharge (objectui#5286 should be MERGED-closed first; the cloud service-cloud reader is not verifiable from this scope and needs a cloud-seat reading before removal).

Rationale: filing is by the spec seat off a recorded maintainer ruling; premise verified against #9683's ruling comment. Not needs-user-decision (decision is already made), not target:v17 (explicitly out of v17).

---

Generated by Claude Code