wiggum-cli 0.16.0 → 0.17.0

package/dist/templates/prompts/PROMPT_review_merge.md.tmpl

@@ -1,5 +1,5 @@
 ## Context
-Study @.ralph/AGENTS.md for commands and patterns.
+If @.ralph/guides/AGENTS.md exists, study it for commands and patterns.
 Study @.ralph/specs/$FEATURE.md for feature specification.
 Study @.ralph/specs/$FEATURE-implementation-plan.md for completed tasks.
 
@@ -9,6 +9,7 @@ Capture any review feedback patterns for future iterations.
 
 ## Task
 All implementation and E2E tasks are complete. Create PR, review, and merge.
+Complete ALL steps in a single pass — do not end the session between steps.
 
 ### Step 1: Verify Ready State
 1. Check all tasks are complete in implementation plan (no `- [ ]` items)
@@ -52,12 +53,14 @@ cd {{appDir}} && gh pr create --base main --head feat/$FEATURE \
 [Read from implementation plan - list completed phases]
 
 ## Testing
-- [x] Unit/integration tests: 97 passing
-- [x] E2E tests: All scenarios passed via Playwright MCP
+- [x] Unit/integration tests: passing
+- [x] E2E tests: All scenarios passed
 - [x] Build succeeds
 
 ## E2E Test Results
-[Copy from implementation plan Phase 9]
+[Copy from implementation plan E2E section]
+
+Closes #[Read the source issue number from the spec file metadata or context section]
 
 Generated with Claude Code
 EOF
@@ -88,17 +91,27 @@ Review the git diff against main and check:
 
 Run: git diff main
 
-Respond with:
-- APPROVED if everything looks good
-- Or list specific issues with file:line references that need to be fixed
-
-IMPORTANT: After posting any PR review comment, you MUST print your final verdict as the LAST line of your output. Print exactly one of:
-  VERDICT: APPROVED
-  VERDICT: NOT APPROVED
-This line is parsed by the automation — do not omit it."
+Then:
+1. Post your complete review as a comment on the PR using:
+   gh pr comment --body '<your review in markdown>'
+   Format the comment with: a summary, specific issues with file:line refs (if any), and the verdict.
+2. Print your final verdict as the LAST line of stdout. Print exactly one of:
+   VERDICT: APPROVED
+   VERDICT: NOT APPROVED
+   This line is parsed by the automation — do not omit it."
 fi
 ```
 
+After the review completes, check its output:
+- If it contains "VERDICT: APPROVED", echo that line so the automation detects it:
+  ```bash
+  echo "VERDICT: APPROVED"
+  ```
+- If issues were found, echo:
+  ```bash
+  echo "VERDICT: NOT APPROVED"
+  ```
+
 **Handle review feedback:**
 - If Claude outputs "VERDICT: APPROVED" -> Proceed to Step 5 (rebase and merge)
 - If Claude lists issues:
@@ -119,7 +132,10 @@ If rebase has conflicts:
 1. Resolve conflicts in affected files
 2. `git add .` the resolved files
 3. `git rebase --continue`
-4. Re-run tests: `{{testCommand}} && {{buildCommand}}`
+
+After rebase (whether or not there were conflicts), ALWAYS re-run tests and build:
+cd {{appDir}} && {{testCommand}} && {{buildCommand}}
+If any tests fail after rebase, fix them before proceeding. Do NOT merge with failing tests.
 
 Push rebased branch:
 ```bash
@@ -127,7 +143,9 @@ cd {{appDir}} && git push --force-with-lease origin feat/$FEATURE
 ```
 
 ### Step 6: Merge PR
-When Claude review is approved and branch is rebased:
+**Pre-merge gate:** Confirm ALL tests pass. Run `cd {{appDir}} && {{testCommand}}` one final time. If ANY test fails, STOP — do not merge. Fix the failures first, then re-run.
+
+When Claude review is approved, all tests pass, and branch is rebased:
 ```bash
 cd {{appDir}} && gh pr merge --squash --delete-branch
 ```
@@ -145,8 +163,15 @@ cd {{appDir}} && gh pr merge --squash --delete-branch
 
 Note: Spec status updates are handled in the Spec Verification phase before PR creation.
 
+## IMPORTANT: Review scope
+If you discover that no implementation code exists (empty diff, no source files changed),
+do NOT implement the feature yourself. Instead, report "VERDICT: NOT APPROVED —
+no implementation found" so the harness can trigger a new implementation iteration.
+
 ## Rules
+- **NEVER merge if any tests are failing.** If tests fail after rebase, fix them first. If unfixable, output "VERDICT: NOT APPROVED — test failures" and stop.
 - Do NOT merge without Claude Code approval
+- Do NOT implement missing features — only review and fix minor issues
 - Address ALL review comments before merging
 - Use squash merge to keep history clean
 - If gh CLI fails, check authentication: `gh auth status`

package/dist/templates/prompts/PROMPT_verify.md.tmpl

@@ -7,6 +7,7 @@ Read @.ralph/LEARNINGS.md for verification patterns from previous features.
 
 ## Task
 Verify that the implementation meets the spec requirements. Update spec files accordingly.
+Complete ALL steps in a single pass — do not end the session between steps.
 
 ### Step 1: Review Requirements
 Read @.ralph/specs/$FEATURE.md and for each requirement under "## Requirements":
@@ -29,8 +30,10 @@ Update `**Last Updated:**` to today's date.
 
 ### Step 4: Update README.md
 Update @.ralph/specs/README.md Active Specs table:
-- Change status from "Planned" to "Completed" (or "Partial")
-- Update Last Updated date
+- Add or update ONLY the row for $FEATURE — do NOT remove or modify other rows
+- Change this feature's status from "Planned" to "Completed" (or "Partial")
+- Update this feature's Last Updated date
+- IMPORTANT: Preserve ALL existing rows in the table — previous features must remain intact
 
 ### Step 5: Document Gaps (if any)
 If any requirements were not fully met, add a section to the spec: