@rudderhq/agent-runtime-codex-local 0.3.6-canary.22 → 0.3.6-canary.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rudderhq/agent-runtime-codex-local",
3
- "version": "0.3.6-canary.22",
3
+ "version": "0.3.6-canary.24",
4
4
  "license": "SEE LICENSE IN LICENSE",
5
5
  "homepage": "https://github.com/Undertone0809/rudder",
6
6
  "bugs": {
@@ -68,7 +68,7 @@
68
68
  "probe:quota": "pnpm exec tsx src/cli/quota-probe.ts --json"
69
69
  },
70
70
  "dependencies": {
71
- "@rudderhq/agent-runtime-utils": "0.3.6-canary.22",
71
+ "@rudderhq/agent-runtime-utils": "0.3.6-canary.24",
72
72
  "picocolors": "^1.1.1"
73
73
  },
74
74
  "devDependencies": {
@@ -106,7 +106,7 @@ ownership. Questions should get answers, corrections should get acknowledgment
106
106
  or explanation, and narrow requests should not become permission to finish the
107
107
  whole issue.
108
108
 
109
- If an issue has a reviewer, moving it to `blocked` is also a reviewer handoff: the reviewer should confirm the blocker, request changes, approve, or keep explicit follow-up open with `rudder issue review`.
109
+ If an issue has a reviewer, moving it to `blocked` also routes reviewer work: the reviewer should confirm the blocker, request changes, approve, or keep explicit follow-up open with `rudder issue review`.
110
110
 
111
111
  Issue comment and close-out commands accept comment bodies only from files or stdin. For any multiline Markdown, command names, code spans, code blocks, test summaries, or screenshot evidence, write the comment to a temporary Markdown file and pass `--body-file <path>` or `--comment-file <path>`, or pass `-` to read the body from stdin.
112
112
 
@@ -169,7 +169,7 @@ When the inbox row or wake context says `relationship: "reviewer"`, `role: "revi
169
169
  - needs follow-up: `rudder issue review <issue> --decision needs_followup --comment-file <path>`
170
170
  - blocked or blocker confirmed: `rudder issue review <issue> --decision blocked --comment-file <path>`; use this only for a confirmed human/external blocker and name the next human action.
171
171
 
172
- Do not rely on a free-form reject or accept comment as the review outcome. The structured decision is the durable close-out signal. A blocked reviewer decision records a human handoff and removes the issue from repeated reviewer pickup until the board changes the issue.
172
+ Do not rely on a free-form reject or accept comment as the review outcome. The structured decision is the durable close-out signal. If a blocked reviewer decision needs human input, name the next human action in the review comment; Rudder records only the reviewer decision and removes the issue from repeated reviewer pickup until the board changes the issue.
173
173
 
174
174
  ## Compatibility Commands
175
175