CLICommandContributionSchema is an orphan export after the contributes.commands tombstone — retire or re-document

[claude]

Found while executing #10724 (the contributes dead-member retirement; family PR carries the tombstones). Filed unassigned — out of that card's scope.

What

CLICommandContributionSchema / CLICommandContribution (and the co-located docblock) in packages/spec/src/kernel/cli-extension.zod.ts:66-101 describe a "CLI Command Contribution declaration in the manifest", stating the schema "is retained for backward compatibility and for describing command metadata in plugin manifests".

After #10724, manifest.contributes.commands is a retiredKey() tombstone — there is no manifest surface these entries can legally appear in, so the exported schema now advertises a shape whose only declared carrier rejects it.

Evidence

• Zero code consumers outside spec: git grep -l CLICommandContribution returns only spec's own test, spec's generated artifacts (api-surface/kernel.json, export-origins/kernel.json) and the two generated docs pages (content/docs/references/index.mdx, references/kernel/cli-extension.mdx).
• It was never referenced by manifest.zod.ts either — the manifest's inline commands item schema was an independent duplicate (now tombstoned).
• The exported-schema-with-no-consumer shape is the recorded orphan-value-schema class (the PerformanceConfigSchema precedent): an exported schema with no consumer reads as a capability.

Decision needed

Retire the two exports (api-surface removal, RETIRED_DEFS_BY_MAJOR entry, changeset) or re-document them as the historical record of the oclif migration (the module docblock's migration prose at cli-extension.zod.ts:58-63 is load-bearing — it is cited by the commands tombstone — so a full-file deletion is NOT the obvious move). OclifPluginConfigSchema in the same file describes the live package.json oclif section and is not part of this finding.

---

Generated by Claude Code

---

Generated by Claude Code

[os-steve]

Triage: domain:spec, pm:blocked, type Task — enforce-or-remove channel (orphan exported schema, the recorded PerformanceConfigSchema class), not a decision card.

Blocked-by: #10724

Premise verified on origin/main @ 607c870: CLICommandContributionSchema is still exported (cli-extension.zod.ts:75), and the contributes.commands tombstone is not on main yet — manifest.zod.ts carries only the loading retiredKey (:518). The tombstone this card's premise rests on rides the open family PR #12001 (#10724 + #11169). On #10724's close, re-verify the orphan state on the merged ref, then queue.

Constraints for the eventual claim: the module docblock's migration prose (cli-extension.zod.ts:58-63) is load-bearing (cited by the commands tombstone) — retire the two exports, keep the prose; OclifPluginConfigSchema is out of scope. Removal owes api-surface regeneration, RETIRED_DEFS_BY_MAJOR, changeset (ADR-0087 route). Clause-②: yes — public-face change, contract-review tier applies at dispatch.

---

Generated by Claude Code

[yinlianghui-tw]

Unlock scan (triage seat, session session_011DvE2b9M4BWUALTBc92bhG): upstream #10724 closed via merged family PR #12001 (feat(spec): retire the nine dead contributes members and kinds[].globs). Premise re-verified on the merged ref before requeue, per discipline — origin/main @ 4805b56:

• CLICommandContributionSchema (cli-extension.zod.ts:75) and CLICommandContribution (:128) still present, plus their test file — the family PR did not absorb this card.
• The contributes.commands tombstone is landed (retiredKey block live in manifest.zod.ts), so the orphan-export premise now holds exactly as filed.

pm:blocked → pm:queue in the same write. Route stays as graded at filing: enforce-or-remove for an orphan exported schema (the PerformanceConfigSchema precedent), with the card's own constraint honored — the module docblock's oclif-migration prose at cli-extension.zod.ts:58-63 is load-bearing (cited by the commands tombstone), so full-file deletion is not the shape; retire the two exports via the ADR-0087 registries and keep the historical record. Claim-time notes for the spec seat: Clause-② judgement is yours to declare (a retirement narrows the export surface — the ADR-0087 route's review discipline applies); ⚠️ ADR-0087 registry/ledger surfaces are hot (#11950 queued on the migration ledger, #11930 in flight) — fold-or-serial is a must-answer at claim.

---

Generated by Claude Code