@rudderhq/agent-runtime-codex-local 0.2.0-canary.11 → 0.2.0-canary.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rudderhq/agent-runtime-codex-local",
-  "version": "0.2.0-canary.11",
+  "version": "0.2.0-canary.13",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/Undertone0809/rudder",
   "bugs": {
@@ -52,7 +52,7 @@
     "probe:quota": "pnpm exec tsx src/cli/quota-probe.ts --json"
   },
   "dependencies": {
-    "@rudderhq/agent-runtime-utils": "0.2.0-canary.11",
+    "@rudderhq/agent-runtime-utils": "0.2.0-canary.13",
     "picocolors": "^1.1.1"
   },
   "devDependencies": {

package/skills/rudder/SKILL.md

@@ -88,9 +88,17 @@ For each linked issue:
 rudder agent inbox --json
 ```
 
-Work `in_progress` first, then `todo`. Skip `blocked` unless you can actually unblock it.
+Inbox rows include a `relationship` field:
 
-If `RUDDER_TASK_ID` is set and the task is assigned to you, prioritize it first.
+- `assignee`: execution work you own
+- `reviewer`: review work where the issue is in `in_review`
+
+Prioritize active close-out work first: reviewer rows with `status:
+"in_review"`, then assignee `in_progress`, then assignee `todo`. Skip
+`blocked` unless you can actually unblock it.
+
+If `RUDDER_TASK_ID` is set and the task is assigned to you or names you as
+reviewer, prioritize it first.
 
 **Step 4 — Mention-triggered wakes.** If `RUDDER_WAKE_COMMENT_ID` is set, read the relevant issue context before doing anything else on that task:
 
@@ -135,6 +143,35 @@ rudder issue comments list "<issue-id-or-identifier>" --after "<last-comment-id>
 
 Before exiting an active `todo` or `in_progress` issue run, leave exactly one clear close-out signal. Use a progress comment if work remains, `issue done` if complete, `issue block` if blocked, or an explicit handoff comment when ownership changes. Rudder may wake you again with `RUDDER_WAKE_REASON=issue_passive_followup` when a successful run exits without that signal.
 
+Before exiting a reviewer run or an inbox row with `relationship: "reviewer"`,
+leave exactly one structured reviewer decision. Do not rely on free-form
+comments such as "reject" or "accepted" as the durable outcome:
+
+- approve:
+
+```bash
+rudder issue review "<issue-id-or-identifier>" --decision approve --comment "<markdown>" --json
+```
+
+- request changes and return the issue to the assignee:
+
+```bash
+rudder issue review "<issue-id-or-identifier>" --decision request_changes --comment "<markdown>" --json
+```
+
+- keep the issue in review because specific evidence or follow-up is still
+  missing:
+
+```bash
+rudder issue review "<issue-id-or-identifier>" --decision needs_followup --comment "<markdown>" --json
+```
+
+- block the issue:
+
+```bash
+rudder issue review "<issue-id-or-identifier>" --decision blocked --comment "<markdown>" --json
+```
+
 - progress-only update:
 
 ```bash
@@ -213,6 +250,11 @@ Planning rules:
 - Self-assign only on explicit @-mention handoff.
 - Always communicate before exit on active work, except blocked issues with no new context.
 - Treat `issue_passive_followup` as close-out governance, not a fresh assignment: inspect current state, then comment, finish, block, or hand off explicitly.
+- Treat `issue_review_closeout_missing` as review close-out governance: inspect
+  current state, then record one structured review decision.
+- A reviewer does not take over implementation unless explicitly asked.
+- A reviewer request for changes must use `rudder issue review --decision
+  request_changes`, not only a reject comment.
 - If blocked, explicitly set the issue to `blocked` with a blocker comment before exit.
 - Never cancel cross-team tasks. Reassign upward with explanation.
 - Use `chainOfCommand` for escalation.

package/skills/rudder/references/cli-reference.md

@@ -14,7 +14,7 @@ Stable CLI contract for agents using the bundled `rudder` skill. Prefer these co
 | Command | Description | Mutating | Org | Agent | Run ID |
 | --- | --- | --- | --- | --- | --- |
 | `rudder agent me` | Show the authenticated agent identity, budget, and chain of command. | no | no | no | no |
-| `rudder agent inbox` | List the compact assigned-work inbox for the authenticated agent. | no | no | no | no |
+| `rudder agent inbox` | List the compact assignee and reviewer work inbox for the authenticated agent. | no | no | no | no |
 | `rudder agent capabilities` | List the stable Rudder agent command contract. | no | no | no | no |
 | `rudder agent skills sync <agent-id>` | Sync the desired enabled skill set for an agent. | yes | no | no | attached when available |
 | `rudder issue get <issue>` | Read a full issue by UUID or identifier. | no | no | no | no |
@@ -24,6 +24,7 @@ Stable CLI contract for agents using the bundled `rudder` skill. Prefer these co
 | `rudder issue comments list <issue>` | List issue comments, optionally only newer comments after a cursor. | no | no | no | no |
 | `rudder issue comments get <issue> <comment-id>` | Read one issue comment by id. | no | no | no | no |
 | `rudder issue update <issue> ...` | Apply generic issue updates when workflow commands are not enough. | yes | no | no | attached when available |
+| `rudder issue review <issue> --decision <decision> --comment <text>` | Record a structured reviewer decision with a required comment. | yes | no | no | attached when available |
 | `rudder issue done <issue> --comment <text>` | Mark an issue done with a required completion comment. | yes | no | no | attached when available |
 | `rudder issue block <issue> --comment <text>` | Mark an issue blocked with a required blocker comment. | yes | no | no | attached when available |
 | `rudder issue release <issue>` | Release an issue back to todo and clear ownership. | yes | no | no | attached when available |
@@ -52,6 +53,17 @@ Before a successful `todo` or `in_progress` issue run exits, leave one close-out
 
 If `RUDDER_WAKE_REASON=issue_passive_followup`, the run is close-out governance for the same issue. Inspect current issue state first, then leave a progress comment, completion, blocker, or explicit handoff.
 
+## Reviewer Close-Out Signals
+
+When the inbox row or wake context says `relationship: "reviewer"`, `role: "reviewer"`, or `wakeSource: "review"`, finish the review with one structured reviewer decision:
+
+- approve: `rudder issue review <issue> --decision approve --comment <text>`
+- request changes: `rudder issue review <issue> --decision request_changes --comment <text>`
+- needs follow-up: `rudder issue review <issue> --decision needs_followup --comment <text>`
+- blocked: `rudder issue review <issue> --decision blocked --comment <text>`
+
+Do not rely on a free-form reject or accept comment as the review outcome. The structured decision is the durable close-out signal.
+
 ## Compatibility Commands
 
 - `rudder agent list --org-id <id>` — List agents for an organization.