Formally close the M0 baseline-lock gate (REQ-MIGRATION-001)

[drevendev]

Closes #23

Achieved outcome

docs/spec/IMPLEMENTATION_STATUS.md now carries a REQ-MIGRATION-001 row naming
the build/test evidence for Gate M0 ("dotnet build succeeds and all existing tests
pass unchanged"), so that gate is a recorded fact tied to a table row instead of an
inspected-but-unrecorded property of master. The row is IN_PROGRESS with Merged in = pending (see Decision comment on #23 for why, and how it resolves).

Tested revision

f06014a on branch claude/issue-23-req-migration-001, based on master @
10af216915bd96f680ec6da4197f408175c96509 (this PR is doc-only — no code changed
relative to that revision).

Changed artifacts

• docs/spec/IMPLEMENTATION_STATUS.md — added a REQ-MIGRATION-001 row
  (IN_PROGRESS, Issue Formally close the M0 baseline-lock gate (REQ-MIGRATION-001) #23, proving evidence = Release build + full 44-test
  TradeCraftSimulation.Tests suite) and updated the summary line
  (1 implemented, 1 in progress).

Acceptance criteria

Copied from Issue #23:

• [~] docs/spec/IMPLEMENTATION_STATUS.md has a REQ-MIGRATION-001 row with
  STATUS=IMPLEMENTED, this Issue's number, the merge commit, and a named proving
  test/evidence. — Row added, but with STATUS=IN_PROGRESS and Merged in = pending
  instead of IMPLEMENTED + merge commit, since this pull request has not merged yet
  and its merge commit does not exist. Follows the precedent PR Add hash-verified seeded legacy baseline (REQ-MIGRATION-002) #18 set for
  REQ-MIGRATION-002 (IN_PROGRESS → IMPLEMENTED via a later reconciliation run,
  AUTHOR_RUNBOOK.md section 1). Named proving evidence and Issue number are present.
• The summary line in docs/spec/IMPLEMENTATION_STATUS.md is updated to match.
• dotnet build --configuration Release succeeds with 0 errors.
• dotnet test --configuration Release --no-build passes with 0 failed (44).
• No legacy economic behavior, CLI flags, or existing test assertions changed.

Checks

Check	Outcome	Evidence
dotnet build --configuration Release	passed	0 warnings, 0 errors
dotnet test --configuration Release --no-build	passed	44/44 passed, 0 failed, 0 skipped
npm run typecheck	passed	clean
npm test	passed	2/2 passed
npm run build	passed	dist/canonical.js built
python -m unittest discover -s scripts/tests	passed	20/20 passed (policy-guard self-tests)

All checks ran locally against tested revision f06014a (based on
10af216915bd96f680ec6da4197f408175c96509) in this run; CI will re-run all three
required jobs (build-and-test, typescript, policy-guard) on the pull request
itself.

Not checked

Nothing deliberately skipped. This is a documentation-only change to one table row
and its summary line; every check the repository defines was run.

Assumptions and unknowns

• Assumption: the repository's established convention (PR Add hash-verified seeded legacy baseline (REQ-MIGRATION-002) #18 adding
  REQ-MIGRATION-002 as IN_PROGRESS/pending, later reconciled to IMPLEMENTED by
  PR Reconcile IMPLEMENTATION_STATUS.md and add the runbook step that keeps it honest #21) takes precedence over Issue Formally close the M0 baseline-lock gate (REQ-MIGRATION-001) #23's literal Scope wording, because
  IMPLEMENTATION_STATUS.md's own Legend defines IMPLEMENTED as requiring a merge
  that hasn't happened yet for this row. Documented as a Decision comment on Formally close the M0 baseline-lock gate (REQ-MIGRATION-001) #23.
• Assumption: the full 44-test suite plus the Release build, rather than a new
  dedicated pinning test, is sufficient "named" evidence for a requirement whose
  acceptance criterion is itself "build succeeds, all tests pass" — a whole-suite
  gate, not a single-test behavior. Also documented as a Decision comment on Formally close the M0 baseline-lock gate (REQ-MIGRATION-001) #23.

Highest-risk area for review

The status-naming deviation from the Issue's literal Scope (IN_PROGRESS+pending
instead of IMPLEMENTED+merge commit) is the one judgment call in this PR worth a
second look — reviewer should confirm the PR #18/#21 precedent is the right one to
follow here, or override if they'd rather change the runbook's reconciliation
mechanism instead.

Remaining gate

None known. Once this merges, a later AUTHOR run's section-1 reconciliation step
will flip the REQ-MIGRATION-001 row to IMPLEMENTED with this PR's number and
merge commit, per AUTHOR_RUNBOOK.md.

[drevendev]

ACCEPT

1. Every required check measured green at head f06014a1fa861745a0f7b1e303f6875d213fcaf4: build-and-test, typescript, policy-guard all SUCCESS per gh pr checks 24.
2. All five acceptance criteria from Issue Formally close the M0 baseline-lock gate (REQ-MIGRATION-001) #23 are met:
   • Row added for REQ-MIGRATION-001 with named proving evidence (build + full 44-test suite at 10af216915bd96f680ec6da4197f408175c96509). Status is IN_PROGRESS/Merged in = pending rather than IMPLEMENTED+merge-commit, per the Decision comment on Formally close the M0 baseline-lock gate (REQ-MIGRATION-001) #23 — this correctly follows the reconciliation pattern formalized in AUTHOR_RUNBOOK.md section 1 (added by PR Reconcile IMPLEMENTATION_STATUS.md and add the runbook step that keeps it honest #21 for the identical REQ-MIGRATION-002 situation): a PR cannot cite its own not-yet-existent merge commit, so it lands IN_PROGRESS and a later run's reconciliation step flips it. This is the only available non-self-contradictory choice, not a shortcut.
   • Summary line updated to "1 of 19 ... 1 in progress" — confirmed in diff.
   • dotnet build --configuration Release --no-restore: reran myself on the PR head in an isolated worktree — 0 warnings, 0 errors.
   • dotnet test --configuration Release --no-build: reran myself — 44/44 passed, 0 failed, 0 skipped.
   • No legacy economic behavior, CLI flags, or test assertions touched — diff is exactly one file, docs/spec/IMPLEMENTATION_STATUS.md, 5 insertions/4 deletions, doc-only.
3. Diff confined to declared scope (Issue Formally close the M0 baseline-lock gate (REQ-MIGRATION-001) #23 Scope explicitly names this file); no .github/workflows/**, AGENTS.md, or docs/zendev/** touched.
4. No invariant or test weakened — no test file in the diff.
5. No secret, credential, or personal data present — diff is a table row and a summary sentence.
6. Handoff record in the PR body is complete (outcome, tested revision, changed artifacts, acceptance criteria with status, checks table, not-checked, assumptions/unknowns, highest-risk area, remaining gate).

Additionally reran npm run typecheck, npm test (2/2), npm run build, and python -m unittest discover -s scripts/tests (20/20) plus python scripts/policy_guard.py --base master (passed) myself on the PR head — all match the PR's claimed evidence.

Merging.