Files

Tom Boucher ba96c70b14 feat(#1602 ): deterministic coverage-metadata UAT routing for verify-work

Add an optional structured `coverage:` block to SUMMARY.md frontmatter and a
deterministic classifier that `verify-work` consumes to route deliverables to
auto-pass vs human-UAT — replacing the rejected #1598/#1599 post-hoc heuristic.

- New `src/coverage.cts` (→ bin/lib/coverage.cjs) parses the nested coverage
  block (extractFrontmatter can't — its `-` items are scalars-only; this is a
  focused parser, sibling of parseMustHavesBlock), validates each entry, and
  classifies into auto_passed vs present. Frozen MODE/PRESENT_REASON/ERROR_CODE
  typed-IR surface. Exposed via `uat classify-coverage --summary <f>`.
- Auto-pass is the narrow proven case only: strict-boolean human_judgment:false
  AND non-empty all-`pass` verification AND zero validation errors. Everything
  else — judgment, empty/failing verification, malformed entry — routes to the
  human (fail-safe). A malformed block falls back to legacy prose extraction and
  surfaces an error; an absent block is byte-identical to pre-#1602.
- execute-plan create_summary populates the block (fail-safe default
  human_judgment:true); verify-work extract_tests consumes it; create_uat_file
  marks auto-passed entries `source: automated`.
- Templates (summary + 3 variants), CONTEXT.md predicate + glossary, INVENTORY,
  eslint/gitignore registration, and Diataxis docs (COMMANDS reference +
  USER-GUIDE explanation) updated.
- Behavioral tests via the CLI (no source-grep); parser-robustness regressions
  for the null-entry/comment-header/mis-indent cases found in adversarial review.

Closes #1602

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

2026-06-22 23:43:22 -04:00

1.4 KiB

Raw Blame History

phase, plan, subsystem, tags, provides, affects, tech-stack, key-files, key-decisions, duration, completed, status

phase

plan

subsystem

Phase [X]: [Name] Summary

[Substantive one-liner describing outcome]

Performance

Duration: [time]
Tasks: [count completed]
Files modified: [count]

Accomplishments

[Key outcome 1]
[Key outcome 2]

Task Commits

Task 1: [task name] - hash
Task 2: [task name] - hash
Task 3: [task name] - hash

Files Created/Modified

path/to/file.ts - What it does
path/to/another.ts - What it does

Decisions & Deviations

[Key decisions or "None - followed plan as specified"] [Minor deviations if any, or "None"]

Next Phase Readiness

[What's ready for next phase]

1.4 KiB Raw Blame History