waypoint-codex 0.10.3 → 0.10.4

package/README.md

@@ -161,7 +161,7 @@ The intended workflow is closeout-based: run `code-reviewer` before considering
 
 For planning work, run `plan-reviewer` before presenting a non-trivial implementation plan to the user and iterate until it has no meaningful review findings left.
 
-When the user approves a reviewed plan or explicitly says to proceed, the intended Waypoint behavior is autonomous execution: keep going through implementation, verification, review, and repo-memory updates unless a real blocker or materially risky unresolved decision requires a pause. If reviewers, subagents, CI, or other external work are still running, Waypoint should wait as long as necessary rather than interrupting them for speed.
+When the user approves a reviewed plan or explicitly says to proceed, the intended Waypoint behavior is autonomous execution: keep going through implementation, verification, review, and repo-memory updates unless a real blocker or materially risky unresolved decision requires a pause. If reviewers, subagents, CI, or other external work are still running, Waypoint should wait as long as necessary rather than interrupting them for speed. For PR work, placeholder automated-review states like CodeRabbit's "review in progress" do not count as a completed review.
 
 When browser-based reproduction or verification is part of the work, Waypoint should also send screenshots of the relevant UI states so the user can see the evidence directly.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "waypoint-codex",
-  "version": "0.10.3",
+  "version": "0.10.4",
   "description": "Codex-native repository operating system: scaffolding, docs routing, repo-local skills, doctor, and sync.",
   "license": "MIT",
   "type": "module",

package/templates/.agents/skills/pr-review/SKILL.md

@@ -12,6 +12,9 @@ Use this skill to drive the PR through review instead of treating review as a on
 - Check the PR's current review and CI status.
 - If CI is red or pending, inspect the failed check logs before triaging review comments so you do not chase comment fixes while a separate blocker is breaking the branch.
 - If automated review is still running, wait for it to finish instead of racing it.
+- Treat placeholder messages such as CodeRabbit's "review in progress" as unfinished state, not as a meaningful review result.
+- If an automated reviewer like CodeRabbit is still pending, in progress, or has not reached a green/completed check state yet, keep waiting before you conclude there are no findings.
+- Once the automated reviewer check turns green/completed, reread the review comments and threads because the real findings may only appear after the placeholder state clears.
 - If comments are still arriving, do not prematurely declare the loop complete.
 - For stacked or non-`main` PRs, explicitly compare the PR head against its base branch and make sure later fixes on the base branch have actually been merged or rebased forward. Do not assume a sibling/base PR fix is already present in the dependent PR.
 - Keep waiting as long as required. Do not interrupt or abandon the review loop just because CI, reviewers, or automated checks are taking a long time.
@@ -42,10 +45,12 @@ Do not leave comments unanswered.
 - push follow-up commit(s)
 - after pushing, return to the PR and wait for the next round of CI, automated review, and human review comments before deciding whether the loop is complete
 - if CI or review is still in flight, keep waiting instead of assuming your last push ended the process
+- before declaring the PR clear or ready, make sure the required Waypoint reviewer agents for this slice have actually run and that their real findings, if any, were handled
 
 Stay in the loop until no new meaningful issues remain.
 Never cut the loop short by forcing a partial return from still-running review or verification systems.
 The loop is not complete while any meaningful review thread still lacks an inline response.
+The loop is also not complete if required Waypoint reviewer-agent passes for the current slice have not been run yet.
 
 ## Step 5: Close With A Crisp State Summary
 

package/templates/.waypoint/agent-operating-manual.md

@@ -132,6 +132,7 @@ Use reviewer agents before considering the work complete, not just as a reflex a
 6. Do not call the work finished before you read the required reviewer results.
 7. Wait for reviewer outputs even if that requires repeated or long waits. Do not interrupt them just because they are still running.
 8. Fix real findings, rerun the relevant verification, update workspace/docs if needed, and make a follow-up commit when fixes change the repo.
+9. Do not call a PR clear, ready, or done until the required reviewer-agent passes for the current slice have actually run.
 
 ## Quality bar