fix(opencode): enforce disciplined RGR guardrails #212
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Slipstream/auto_review!212
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "bdd-tdd-guardrails"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Tightens opencode's BDD/TDD guardrails so behavior work proceeds through one focused RED, reviewed RED approval, one implementation edit, focused rerun, GREEN review, and committed checkpoints. Adds mechanical RGR plugin gates for multi-failure RED rejection, clean worktree starts, reviewed RED state, single-edit tokens, apply_patch path extraction, and broad implementer-prompt blocking, with release-tooling contract coverage.
Type of change
Verification
Pre-merge checklist
Related
No issue linked.
This PR introduces stricter guardrails for the RGR cycle, enforcing single-failure RED tests and requiring RED approval before production edits. The changes appear well-structured and should enhance discipline in the development process.
Walkthrough
rgr_approve_redin the workflow, ensuring RED approval before production edits.assertCleanWorktreeandvalidateRgrRedEvidencefunctions.validateRgrRedEvidencefunction.