fix(harness): make authoritative F150-F152 verification commands runnable and evidence-backed
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 969
Description
Post-merge forensic from PR #961 exact head 1115421a85e19420a1fdc6a03c3fc6797dd994de. All six authoritative F150-F152 verification commands in feature_list exit 1 with No test files found because the committed tests use different paths; evidence fields remain empty. The PR nevertheless merged and closed three issues. Required fix: preserve the intended behavior contract while aligning committed test paths and authoritative verification commands, add non-empty exact-SHA evidence, and mechanically prevent passing or merge when declared verification files do not exist. One issue, one PR. Related governance incident: #956. Coordination state: recorded but not dispatched because it is not in the current pnpm harness readiness queue.
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the feature_list entries and the authoritative F150-F152 verification commands, then compare them with the committed test paths from PR #961 at exact SHA 1115421a85e19420a1fdc6a03c3fc6797dd994de. Run the declared commands first and trace the pnpm harness checks. Done means every declared file exists, commands pass, and non-empty exact-SHA evidence prevents an invalid merge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100