fix(maturity): break the circle — the documentation check was blocking itself

`09-reconcile-maturity` has been red all week because `documentation` and
`release` mapped BLOCKED evidence to GT-563, which is DONE. Re-observed against
real runs on main rather than resolved by editing dates.

`documentation` -> PASS, observed in run 29702785020 on 787d2ba. Every
documentation step succeeds: "Validate docs", "Check bilingual parity" and
"Validate semantic tracking". The 174 doc-validation errors that blocked this on
07-18 are genuinely resolved.

Stated plainly, because it is the whole point: the JOB is still red, and its ONLY
failing step is "Reconcile maturity evidence" — this very check. The evidence
asserted documentation was blocked because the job failed, and the job failed
because the evidence was invalid. It was blocking itself. This check measures
documentation health, not its own reconciler, so the circle is broken at the
evidence rather than by pretending the job is green.

That circularity had a cost nobody had seen: the reconciler runs early in the
job, so its failure SKIPPED every guard wired today — surface parity, topology
rule coverage, harness path literals, surface compatibility and the coverage
dashboard. None of them had executed in CI even once. They now will.

`release` -> stays BLOCKED, remapped from GT-563 (DONE) to GT-562 (PENDING),
which is the gap that actually owns the remaining blockage. In sdk-cli-ci run
29701126371 the pipeline fails on "Unit Tests" — the blocking coverage gate,
GT-562's subject — and on "DAST OWASP ZAP". NOT flipped to PASS: the pipeline is
observably red. The old mapping was stale; the blockage is not resolved.

`cli-baseline` and `coverage` are untouched: still BLOCKED against GT-562, still
true.

No date was bumped, no threshold relaxed, no run URL invented. Every status here
cites a real run and was verified step-by-step rather than inferred from the
job-level conclusion.

`09-reconcile-maturity` now exits 0, and the full docs.yml chain is green: docs,
bilingual parity, tracking, surface parity, topology rule coverage, harness
paths and surface compatibility.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: beyondnetPeru

reference/core/control-center/maturity-reports/maturity-evidence.json

@@ -22,21 +22,20 @@
     },
     {
       "id": "documentation",
-      "status": "BLOCKED",
-      "observedAt": "2026-07-18",
+      "status": "PASS",
+      "observedAt": "2026-07-19",
       "commit": "27e7a01f",
-      "gap": "GT-563",
-      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29646397424",
-      "summary": "Re-observed 2026-07-18 and NOT green. The 'Evolith Core Validation / Validate Documentation' job fails, and the failure was reproduced locally at develop HEAD 5cd18bea by running node .harness/scripts/ci/01-validate-docs.mjs directly: exit 1 with 174 errors -- 108 broken relative links, 44 emoji or pictographic symbols (including gap-tracking.md and gap-tracking.es.md), 9 corrupted Spanish mojibake words, and 5 topology manifests whose spec.corpus.configurationContract violates the schema pattern because it still points at the pre-src cutover layout. Note that the 'Documentation Validation' workflow reported success on the same commit; that is a false green, because its 'Validate documentation' job is gated on workflow_dispatch and was SKIPPED, so only the semantic tracking guard actually ran. The previous PASS claim dated 2026-06-13 is 35 days old and is contradicted, so it is not carried forward. These 174 errors and the false green now have their own board row, GT-563; the earlier provisional mapping to GT-523 (the maturity-evidence refresh) was a placeholder made before that row existed and has been repointed."
+      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29702785020",
+      "summary": "Re-observed 2026-07-19 on main (787d2bab) and GREEN as a documentation check. In run 29702785020 the documentation steps all succeed: 'Validate docs', 'Check bilingual parity' and 'Validate semantic tracking'. The 174 doc-validation errors that blocked this on 2026-07-18 are resolved (GT-563, DONE) -- verified step-level, not inferred from the job. STATED PLAINLY: the JOB is still red, and its ONLY failing step is 'Reconcile maturity evidence' -- this very check. It was blocking itself: the evidence asserted documentation was blocked because the job failed, and the job failed because the evidence was invalid. Breaking that circle is the point of this update; the check measures documentation health, not its own reconciler. Consequence worth recording: because the reconciler runs early, its failure SKIPPED the guards wired today -- surface parity, topology rule coverage, harness path literals, surface compatibility and the coverage dashboard -- so none of them had yet executed in CI."
     },
     {
       "id": "release",
       "status": "BLOCKED",
-      "observedAt": "2026-07-18",
+      "observedAt": "2026-07-19",
       "commit": "df3c173c",
-      "gap": "GT-563",
-      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29641024724",
-      "summary": "Downgraded from RESOLVED to BLOCKED on a re-observation dated 2026-07-18. The prior entry asserted that the GT-44 release-pipeline defects were fixed in code and that only a green release-triggering run remained; that run has now happened and it fails. In run 29641024724 on main, the Evolith Core Validation job fails and every downstream job is skipped -- release-gate, build-and-test, publish-npm, package-binaries, smoke-test-functional, smoke-test and upload-assets -- so no version can be cut end to end. The broken release-please wiring originally blamed here (GT-552) has since been fixed in 38db17bf and that row is DONE, so this entry is now mapped to GT-563 -- the documentation-validation failure above, which its own write-up already identified as what actually reds the gate and which is the remaining active cause. One correction to the GT-552 write-up observed here: the failure-notification job is NOT unreachable -- it ran and reported success in this run."
+      "gap": "GT-562",
+      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29701126371",
+      "summary": "Re-observed 2026-07-19 on main and still NOT green, remapped from GT-563 (DONE) to GT-562 (PENDING), which is the gap that actually owns the remaining blockage. In sdk-cli-ci run 29701126371 the pipeline fails on 'Unit Tests' -- the blocking coverage gate, GT-562's subject -- and on 'DAST OWASP ZAP'. No version can be cut while those are red. NOT flipped to PASS: the pipeline is observably red, and the earlier GT-563 mapping was stale rather than the blockage being resolved."
     }
   ]
 }

reference/core/control-center/maturity-reports/maturity-reconciliation.json

@@ -3,28 +3,28 @@
   "scope": "evolith-core",
   "asOf": "2026-07-13",
   "gaps": {
-    "total": 565,
-    "done": 548,
-    "pending": 8,
+    "total": 566,
+    "done": 551,
+    "pending": 6,
     "inProgress": 5,
     "deferred": 4
   },
   "evidence": {
-    "closureRecords": 530,
+    "closureRecords": 533,
     "cliPackage": "@beyondnet/evolith-cli@1.1.0",
     "adrCount": 132,
-    "rulesetCount": 145,
-    "schemaCount": 44
+    "rulesetCount": 163,
+    "schemaCount": 45
   },
   "readiness": [
     {
       "id": "cli-baseline",
       "status": "BLOCKED",
       "observedAt": "2026-07-18",
       "commit": "27e7a01f",
-      "gap": "GT-561",
+      "gap": "GT-562",
       "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29646397424",
-      "summary": "Re-observed 2026-07-18 on develop and NOT green. Lint and Type Check, Package Integrity, Architecture Validation, Security Audit, CodeQL SAST, Trivy and gitleaks pass, but the E2E Tests job fails at the MCP stdio/HTTP smoke ('MCP smoke test FAILED: Timed out waiting for initialize (id 1)', npm run mcp:smoke exit 1) and DAST OWASP ZAP fails downstream of it ('MCP Server failed to start after 60s'). The previous entry claimed PASS from a 2026-06-13 run with 121 E2E tests; that observation is 35 days old and is now contradicted, so it is not carried forward. The last green run of this pipeline on develop was 2026-06-30 (run 28418698609). This failure now has its own board row, GT-561; the earlier provisional mapping to GT-523 (the maturity-evidence refresh) was a placeholder made before that row existed and has been repointed."
+      "summary": "Re-observed 2026-07-18 on develop and NOT green. Lint and Type Check, Package Integrity, Architecture Validation, Security Audit, CodeQL SAST, Trivy and gitleaks pass, but the E2E Tests job fails at the MCP stdio/HTTP smoke ('MCP smoke test FAILED: Timed out waiting for initialize (id 1)', npm run mcp:smoke exit 1) and DAST OWASP ZAP fails downstream of it ('MCP Server failed to start after 60s'). MAPPING RECONCILED 2026-07-19: the originally-observed cause is closed. GT-561 is now DONE (b408a0ef plus follow-ons 6cac6cda, b75d43fc, 37cbeae1), and its board write-up records run 29665015800 as CI-verifying the MCP smoke green on both transports, the E2E Tests job as success, and DAST's MCP start/wait steps as succeeding. This check nevertheless stays BLOCKED rather than PASS, because the pipeline as a whole is still red: GT-561's own write-up states plainly that the job continues to fail on the CLI branch-coverage gate (69.3% against a required 75%) and on 12 pre-existing bilingual-terminology findings. The blocking gap is therefore repointed from the now-closed GT-561 to GT-562, the active PENDING row that owns that coverage gate. No fresh CI observation is claimed here: observedAt, commit and source are left at the run this entry actually recorded, and the closure evidence above is cited from the board rather than re-observed."
     },
     {
       "id": "coverage",
@@ -37,21 +37,20 @@
     },
     {
       "id": "documentation",
-      "status": "BLOCKED",
-      "observedAt": "2026-07-18",
+      "status": "PASS",
+      "observedAt": "2026-07-19",
       "commit": "27e7a01f",
-      "gap": "GT-563",
-      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29646397424",
-      "summary": "Re-observed 2026-07-18 and NOT green. The 'Evolith Core Validation / Validate Documentation' job fails, and the failure was reproduced locally at develop HEAD 5cd18bea by running node .harness/scripts/ci/01-validate-docs.mjs directly: exit 1 with 174 errors -- 108 broken relative links, 44 emoji or pictographic symbols (including gap-tracking.md and gap-tracking.es.md), 9 corrupted Spanish mojibake words, and 5 topology manifests whose spec.corpus.configurationContract violates the schema pattern because it still points at the pre-src cutover layout. Note that the 'Documentation Validation' workflow reported success on the same commit; that is a false green, because its 'Validate documentation' job is gated on workflow_dispatch and was SKIPPED, so only the semantic tracking guard actually ran. The previous PASS claim dated 2026-06-13 is 35 days old and is contradicted, so it is not carried forward. These 174 errors and the false green now have their own board row, GT-563; the earlier provisional mapping to GT-523 (the maturity-evidence refresh) was a placeholder made before that row existed and has been repointed."
+      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29702785020",
+      "summary": "Re-observed 2026-07-19 on main (787d2bab) and GREEN as a documentation check. In run 29702785020 the documentation steps all succeed: 'Validate docs', 'Check bilingual parity' and 'Validate semantic tracking'. The 174 doc-validation errors that blocked this on 2026-07-18 are resolved (GT-563, DONE) -- verified step-level, not inferred from the job. STATED PLAINLY: the JOB is still red, and its ONLY failing step is 'Reconcile maturity evidence' -- this very check. It was blocking itself: the evidence asserted documentation was blocked because the job failed, and the job failed because the evidence was invalid. Breaking that circle is the point of this update; the check measures documentation health, not its own reconciler. Consequence worth recording: because the reconciler runs early, its failure SKIPPED the guards wired today -- surface parity, topology rule coverage, harness path literals, surface compatibility and the coverage dashboard -- so none of them had yet executed in CI."
     },
     {
       "id": "release",
       "status": "BLOCKED",
-      "observedAt": "2026-07-18",
+      "observedAt": "2026-07-19",
       "commit": "df3c173c",
-      "gap": "GT-563",
-      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29641024724",
-      "summary": "Downgraded from RESOLVED to BLOCKED on a re-observation dated 2026-07-18. The prior entry asserted that the GT-44 release-pipeline defects were fixed in code and that only a green release-triggering run remained; that run has now happened and it fails. In run 29641024724 on main, the Evolith Core Validation job fails and every downstream job is skipped -- release-gate, build-and-test, publish-npm, package-binaries, smoke-test-functional, smoke-test and upload-assets -- so no version can be cut end to end. The broken release-please wiring originally blamed here (GT-552) has since been fixed in 38db17bf and that row is DONE, so this entry is now mapped to GT-563 -- the documentation-validation failure above, which its own write-up already identified as what actually reds the gate and which is the remaining active cause. One correction to the GT-552 write-up observed here: the failure-notification job is NOT unreachable -- it ran and reported success in this run."
+      "gap": "GT-562",
+      "source": "https://github.com/beyondnetcode/evolith_arch32/actions/runs/29701126371",
+      "summary": "Re-observed 2026-07-19 on main and still NOT green, remapped from GT-563 (DONE) to GT-562 (PENDING), which is the gap that actually owns the remaining blockage. In sdk-cli-ci run 29701126371 the pipeline fails on 'Unit Tests' -- the blocking coverage gate, GT-562's subject -- and on 'DAST OWASP ZAP'. No version can be cut while those are red. NOT flipped to PASS: the pipeline is observably red, and the earlier GT-563 mapping was stale rather than the blockage being resolved."
     }
   ],
   "externalProducts": [