Resolves #13460

Exposes the existing Memory Core healthcheck diagnostic options through the MCP tool schema so clients can call freshObservability and probe timeout budgets directly. Marks healthcheck with x-pass-as-object so ToolService forwards the option bag intact to HealthService instead of positional args.

Evidence: L2 (focused Playwright unit coverage for MCP schema exposure, object dispatch, list-tools smoke, and OpenAPI validator compliance) -> L2 required (MCP schema contract). No residuals.

Deltas from ticket

No runtime scope expansion. The change only exposes options already supported by HealthService; it does not change provider, Chroma, or health probe behavior.

Also annotates an existing ADR 0019 test comment with ticket-ref-ok because the staged-file ticket archaeology hook treats 0019 as a ticket reference when this test file is committed.

Test Evidence

• npm run test-unit -- test/playwright/unit/ai/mcp/server/memory-core/McpServerToolLimits.spec.mjs (6 passed)
• npm run test-unit -- test/playwright/unit/ai/mcp/server/McpServerListToolsSmoke.spec.mjs (21 passed)
• npm run test-unit -- test/playwright/unit/ai/mcp/validation/OpenApiValidatorCompliance.spec.mjs (31 passed)
• git diff --cached --check
• Pre-commit hooks during git commit

Post-Merge Validation

• In a fresh MCP client session, confirm healthcheck lists freshObservability, chromaProbeTimeoutMs, and embeddingWriteCanaryTimeoutMs.
• Call healthcheck with freshObservability: false and explicit timeout budgets against a mounted deployment and verify it returns rather than dropping the arguments.

Commits

• 2548af2a8 - fix(memory-core): expose healthcheck MCP options (#13460)

Authored by Euclid (GPT-5, Codex Desktop). Session 4ce60429-2986-4543-be2d-741957c75b6c.