refactor(mcp): project doctor family output schema from its owning module

[thymikee]

Summary

Projects the MCP output schema for the doctor command family out of the central
command-output-schemas.ts registry and into doctor.ts, its owning module, following the
same pattern applied to the other command families in this stacked series. No behavior change:
the published MCP outputSchema for doctor is unchanged, only its declaration site moves.

Part of #2819. Touches 4 files. Stacked on
refactor/mcp-output-schemas-2819-management-prepare-schema.

Validation

Tested commit: ad91cc368ec88b8d7cc05767cd20cd2ad51f3cfe

• pnpm check:affected --run: 165 test files, 1371 tests passed, 0 failed.
• No device needed (pure MCP schema move). Verified the published outputSchema for doctor
  is byte-identical before/after: built a temporary detached worktree of origin/main
  (with node_modules symlinked from this branch to resolve workspace packages), then ran
  node -e "import('.../src/mcp/command-output-schemas.ts').then(m => console.log(JSON.stringify(m.COMMAND_OUTPUT_SCHEMAS.doctor)))"
  on both origin/main and this branch's HEAD. diff reported no difference, and a
  structural-equality check on the parsed JSON also returned true. The verification worktree
  was removed afterward.

No unresolved risk: this is a pure move with no schema-shape or Swift changes.

[github-actions]

Size Report

Metric	Base	Current	Diff
Installed (including dependencies)	4.88 MB	4.88 MB	+18 B
Package (unpacked)	4.88 MB	4.88 MB	+18 B
Package (download)	1.46 MB	1.46 MB	+20 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	29.0 ms	27.9 ms	-1.1 ms
CLI --help	85.4 ms	86.6 ms	+1.2 ms

[cubic-dev-ai]

All reported issues were addressed across 4 files

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[thymikee]

Reviewed at ad91cc3. This looks good: the doctor output schema moves to its owning module with the same text. The one new edge, doctor.ts to kernel/device, was already in the CLI import closure.

The Coverage failure is the same eager-closure budget check as on the rest of this stack, through src/commands/system/index.ts and src/commands/recording/index.ts, which this diff does not touch. Smoke Tests was still running at review time.

[thymikee]

The code at ad91cc3 is unchanged since the last review, and that review stays clean. The branch now conflicts with its base, refactor/mcp-output-schemas-2819-management-prepare-schema, after the prepare PR was rebased. Please rebase this PR onto the updated base. I removed ready-for-human until the conflict is resolved.

[thymikee]

Rebased onto the updated prepare-schema base; new head is 8cb0ff5.

• Duplicate import in doctor.ts (cubic): merged into one named import from command-input.ts, so the namespace import is gone. Fixed in 8cb0ff5.
• Duplicate helpers: none in this link. It uses the shared constSchema from command-input.ts; grep of src/ and packages/ shows a single definition.
• Coverage eager-closure budget: same failure as the rest of the stack, through system/index.ts and recording/index.ts, which this diff does not touch.
• Checks: check:affected passes locally on this head. Smoke Tests, if it fails, is the known iOS fixture flake and not related to this diff.

[thymikee]

Thanks for the update. The conflict from the earlier review (ad91cc3) is fixed, and I found no problems in 8cb0ff5. The doctor family output schema now comes from its owning module, and the checks are green. I did not run the tests locally and relied on the passing checks. I also did not check whether the remaining schema imports in command-output-schemas.ts are all still used, but lint would catch an unused import. Nothing else is needed before merge.