fix(doctor): stamp CURRENT_SCHEMA_VERSION at seed; add stalled-bundle check

[rasatpetabit]

Closes #22. Closes #23.

Found while diagnosing a real failure: a /masterplan brainstorm run on another repo seeded a bundle, then spent a whole session fixing a production outage, auditing three hosts, landing a 36-file branch reconciliation and writing a full spec.md — and made exactly one state-writing mp call (seed). The bundle ended at phase: brainstorm, goals: [], with no events.jsonl at all. doctor reported zero findings for it.

1 — seed stamped a version below the doctor's own floor (#23)

bin/masterplan.mjs hardcoded the literal at the seed call site:

schemaVersion: flags['schema-version'] !== undefined ? Number(flags['schema-version']) : 8,

That silently overrode buildSeedState's schemaVersion = CURRENT_SCHEMA_VERSION (9) default, so every freshly-seeded bundle landed below the floor version-scoped checks gate on:

// lib/doctor/spec-assumptions.mjs:50
if (Number.isNaN(sv) || sv < CURRENT_SCHEMA_VERSION) continue;

Net effect: spec-assumptions skipped 100% of bundles, reporting SKIP no in-scope bundle spec.md to check against a repo holding 11 current bundles with specs. The ## Assumptions section it enforces is documented as a hard pre-approval gate; its only automated enforcement has been inert. It fails open, degrading to SKIP rather than erroring, which is exactly why nobody caught it.

Now symbolic. The pre-existing seed test asserted the buggy literal 8, so it's updated to assert the constant — worth a reviewer's eye, since that's a test change accompanying a behavior change.

Left alone deliberately: migrate-bundle still lands at 8. Grandfathering a genuinely legacy bundle is defensible; stamping a brand-new one below the floor is not. Happy to fold migrate in if you'd rather they converge.

2 — nothing detected a seeded-then-abandoned bundle (#22)

dangling-run covers a run that started a wave and crashed (stranded active_run). Nothing covered a bundle that never started one. That gap is load-bearing: on resume, mp continue sees phase: brainstorm + tasks: [] + active_run: null and offers "continue / restart / stop" — indistinguishable from a bundle seeded thirty seconds ago. Every unrecorded decision is lost at the next compaction.

stalled-bundle WARNs when a pre-execute bundle (brainstorm/plan, non-archived) has a spec.md but no parseable event. A spec proves design work happened; zero events prove none of it was recorded.

Signal choice is deliberately the cheap robust one — no git inspection, no mtime comparison (mtimes reset on fresh checkouts and would flap in CI). Phases past plan are exempt because wave machinery writes its own events and record-result surfaces that gap louder.

Not version-scoped, with a test pinning that. CD-7 is a universal invariant, not a v9 feature — and version-scoping is the precise mechanism that made spec-assumptions dead. A legacy schema-3 bundle must still WARN.

Verification

Full suite: 1578 pass, 0 fail.

New coverage: four severity-prefixed fixtures (warn/pass/skip/skip), plus explicit tests for the non-version-scoped contract, empty-but-present events.jsonl, archived exemption, no-bundles-dir SKIP, seed stamping the constant, and --schema-version still overriding. The registry test moves 17 → 18.