Migrate the remaining 28 hand-authored MCP output schemas to their owning command modules #2819

Purpose

src/mcp/command-output-schemas.ts is still ~863 lines of hand-authored per-command MCP
outputSchemas. #2810 landed the seam that lets a command family author its result schema beside its
command descriptor and project it into this map, and migrated the first family (replay: replay,
test). 28 entries remain, so 28 commands still have their published result shape declared three
layers from the code that produces it — which is why the file churned 11 times in the last 200 commits.

Required behavior

For each migrated command family:

1. Export a frozen schema map from the family's owning command module, keyed by command name.
2. Register that module in the seam's projection list in src/mcp/command-output-schemas.ts, and delete
   the hand-authored entries it replaces. The map's satisfies Record<keyof CommandResultMap, JsonSchema>
   totality check must stay intact — do not route composition through a generic helper whose members are
   constrained to Record<string, JsonSchema>, because the resulting index signature stops the map from
   proving per-command coverage.
3. Add the family to PROJECTED_FAMILIES in
   src/mcp/__tests__/command-tools-replay-schemas.test.ts. That is the guard against silent
   last-wins shadowing between two projected families; a family that skips registration is unchecked,
   and registration is the step that makes it checked.
4. Move the family's shape assertions with it, keeping the reference-equality proof that the published
   entry is the module's object and not a copy.

Remaining entries, grouped by owning module

Measured from COMMAND_OUTPUT_SCHEMAS (30 keys, 2 projected) with ownerFilesForCommand:

Observable completion conditions

• Every migrated command's published schema is reference-equal to the entry its own module exports, and
  the composed map is unchanged for all 30 keys (byte-compare the published schemas against the base).
• PROJECTED_FAMILIES covers every family the seam spreads; a planted second family claiming a
  migrated command fails the disjointness test.
• No new production export beyond the schema map each family needs, and no allowlist or baseline added.

Dependencies and sequencing

• Blocked by: nothing. refactor(mcp): project command output schemas from their owning family #2810 supplies the seam.
• Prerequisite question for scroll: it resolves no src/commands/** owner file at all, so it is the
  one entry the seam cannot project even in principle. Decide whether that is an owner-file gap to repair
  first or a deliberate placement, then schedule scroll accordingly.
• src/commands/system/index.ts owns 10 of the 28 and also carries the interactor members that refactor(contracts): make the alert legs optional members and drop their denials #2807,
  refactor(contracts): drop the Limrun iOS denials its facts already make #2815 and refactor(interactors): stop handing web and Vega a full wall of refusals #2816 just made optional. Do that family's schema migration and its fact-cell pass together
  rather than visiting the module twice.
• Land per command family, not one sweep.