docs(gaps): register GT-633, GT-634 and GT-635 on main

[beyondnetPeru]

Pull Request Summary

The three board rows main is missing, and nothing else. Replaces #277, which is closed rather than merged: every code change on that branch has since landed from other sessions.

what was on #277	superseded by
capture script + extracted triage	#276
the two derived-artifact chain links	#287 — identical to the specification: same producer, checkArgs, the three consumes sources and both written artifacts, in the position after the ABAC link
SDK range fix + 1.2.2 release prep	#285
GT-624 deprecations + the publish-lag gate	#288

GT-633 — DONE

The content worth keeping is the failure mode, not the repair: a guard whose expected value was a copy of its actual value. iso-5055-mapping.test.mjs asserted the snapshot's six class counts against six numbers typed into the test — the same six literals the snapshot already contained — so it passed for as long as the file was unchanged, whatever Core actually pinned. And the drift did not stay put: build-iso-5055-mapping.mjs stamps nativeEvaluability onto every row of the ISO/IEC 5055 mapping from that file, laundering one stale class into an artifact five times the size of its input.

Recorded with how it actually landed, because three sessions converged on it: #276 and #287 on main, and a second, independent implementation on develop as #279 — an in-spec renderer driven by UPDATE_EVALUABILITY_SNAPSHOT=1 rather than a standalone script. Both recaptured the same numbers (native-handler 139 → 151, documentation-only 129 → 136, backlog 60 → 48, corpus 379 → 386), which is mutual corroboration of the measurement. But two generators for one artifact is this row's own defect one level up, and reconciling them is the open blocker on develop → main. That reconciliation is deliberately not attempted here: choosing which generator survives belongs to the sessions that wrote the two halves.

GT-634 — PENDING, and it stays that way

1.2.2 is on main and not published. A range in the repository is not a range on the registry; until npm serves it, the published latest of the CLI and the MCP still installs the 2026-07-18 SDK. The row closes when npm view @beyondnet/evolith-cli@latest dependencies shows a range that resolves to a version published on or after 2026-07-27.

GT-635 — DONE, closed by someone else within the hour

And closed the way the row asked: the budget was not raised to ratify the breach. f34a10f1 migrated the recorded closure commands onto the paths this repository actually has; 600dd7a9 then moved the budget 304 → 40 from the count that migration produced. The corpus went 309 → 40 dead over 1045 recorded commands — 269 repaired, not exempted, which subsumes the four the row was opened for. The record says plainly that the row's value was making a permanently red job visible, not owning the repair.

Verified

• 08-validate-tracking → 635 gaps (ES 635), 611/611 EN/ES catalog sections, 577 closure records
• 41-validate-evidence-commands --strict --max-dead 40 → 38 dead on a clean checkout, and the guard's own basis line separates generated state, so that number is not a property of my machine. The two new closure records add none.
• 01-validate-docs (1491 files), 04-check-bilingual-parity, 46-validate-derived-artifact-order → 5 links current and at a fixed point
• counters 593/632 → 595/635

Evolith Core Quality Gates

• Bilingual Parity: all three rows and all three catalog entries in EN and ES.
• Validation Scripts: 01-validate-docs.mjs green.
• Bilingual Validation: 04-check-bilingual-parity.mjs green.
• Agnosticism: documentation only.

Linked ADRs / Issues

• Link to ADR: n/a
• Link to Issue: GT-633, GT-634, GT-635; closes fix(standards): a guard whose expected value was a copy of its actual value (GT-633) #277 without merging it

Conventional Commits

• Commit follows Conventional Commits.

---

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[github-actions]

📊 Bilingual Coverage Impact

PR Changes

• Paired EN/ES files modified: 3
• New EN files needing ES translation: 0

Repository Coverage

Metric	Value
Total EN files	524
Total ES files	498
Paired files	0
Coverage	0%

✅ Good: All EN changes have ES counterparts.

---

Generated by GitHub Actions