René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"chore(#5056): gate evidence is typed and the exit code follows the verdict — Phase 8","articleBody":"### Pre-submission checklist\n\n- [x] This does not change user-facing behavior (commands, output, file formats, config)\n- [x] I have searched existing issues — this has not already been filed\n\n> Scope note on the first checkbox: gate payloads stay byte-identical. The one class of behavior change is stated in ADR-5057 §4 and #4686: a gate verb's exit status is now a function of its verdict, so a failing verdict no longer exits 0. It ships with a `Fixed` changeset.\n\n### What is the maintenance task?\n\nPhase 8 of epic #5056 (ADR-5057 §4, third and fourth bullets): gate evidence is a typed result read through the document seams, and a gate verb's exit code is derived from its `GateVerdict` through the process exit contract (`src/cli-exit.cts`, ADR-3889). Depends on Phase 6 (merged in #5144).\n\n### Type of maintenance\n\nRefactoring / code quality\n\n### Current state\n\n- `Evidence\u003cT> = found | none | unreadable` does not exist. Gate return paths cannot tell \"nothing there\" from \"could not read\", so an unreadable input can produce a passing verdict.\n- Gates parse structured plan and document content with per-gate regexes instead of the Frontmatter Module, `markdown-sectionizer`, `markdown-table` and `PlanningDoc`.\n- `emitGateResult` in `src/check-command-router.cts` prints a verdict's payload and never sets an exit status; `phase uat-passed` and `verify artifacts` exit 0 while their JSON reports failure (#4686).\n\n### Proposed work\n\n- Census per-gate regex parsers of structured content, gate return paths that cannot distinguish `none` from `unreadable`, and gate verbs whose exit code is chosen per verb; publish the counts in the PR and drive them to zero.\n- Add `Evidence\u003cT> = { kind: 'found', value: T } | { kind: 'none' } | { kind: 'unreadable', reason, span? }`; a gate cannot produce a passing verdict from `unreadable`.\n- Read structured content through the document seams; delete the per-gate regexes.\n- Derive every gate verb's exit status from its `GateVerdict` through `cli-exit`; no verb chooses its own.\n- Failing-first regression cases for #4562, #4541, #4259, #4686, #4031, #4176.\n\n### Done when\n\n- [ ] Census published in the PR and driven to zero\n- [ ] `Evidence\u003cT>` exists and does not admit a passing verdict on `unreadable` (type or property test, with a positive control)\n- [ ] Gates read structured content only through the document seams; per-gate regex parsers deleted\n- [ ] Gate verbs obtain their exit code only through `cli-exit`; a shell caller of `phase uat-passed --require-verification` and `verify.artifacts` gets a non-zero status whenever the verdict fails\n- [ ] A drift guard fails on a gate verb choosing its own exit code, with a positive control\n- [ ] Tests pass under `gsd-test`\n\n### Area affected\n\nMultiple areas\n\n### Additional context\n\nEpic: #5056. Design lock: ADR-5057 §4 and Phase 8. Evidence (`Refs`, all closed): #4562, #4541, #4259, #4686, #4031, #4176.\n","author":{"url":"https://github.com/trek-e","@type":"Person","name":"trek-e"},"datePublished":"2026-10-01T20:39:35Z","url":"https://github.com/open-gsd/gsd-core/issues/5170"}