@rudderhq/agent-runtime-codex-local 0.2.0-canary.27 → 0.2.0-canary.28

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.2.0-canary.27",
3
+ "version": "0.2.0-canary.28",
4
4
  "license": "SEE LICENSE IN LICENSE",
5
5
  "homepage": "https://github.com/Undertone0809/rudder",
6
6
  "bugs": {
@@ -52,7 +52,7 @@
52
52
  "probe:quota": "pnpm exec tsx src/cli/quota-probe.ts --json"
53
53
  },
54
54
  "dependencies": {
55
- "@rudderhq/agent-runtime-utils": "0.2.0-canary.27",
55
+ "@rudderhq/agent-runtime-utils": "0.2.0-canary.28",
56
56
  "picocolors": "^1.1.1"
57
57
  },
58
58
  "devDependencies": {
@@ -199,6 +199,8 @@ rudder issue block "<issue-id-or-identifier>" --comment "<markdown>" [--image "<
199
199
 
200
200
  Add `--image "<path>"` one or more times when the close-out/progress comment should include local screenshots or images. Supported local image types are PNG, JPEG, WebP, and GIF; the CLI uploads them as issue attachments and appends Markdown image links.
201
201
 
202
+ If your comment mentions a screenshot path or uses a screenshot as validation evidence, attach that file with `--image "<path>"`. Do not leave only a local `/tmp/...` or workspace image path in the comment, because board users may not be able to inspect it from Rudder.
203
+
202
204
  ```bash
203
205
  rudder issue update "<issue-id-or-identifier>" ... --json
204
206
  ```
@@ -27,6 +27,7 @@ Stable CLI contract for agents using the bundled `rudder` skill. Prefer these co
27
27
  | `rudder issue comments get <issue> <comment-id>` | Read one issue comment by id. | no | no | no | no |
28
28
  | `rudder issue update <issue> ... [--image <path>]` | Apply generic issue updates when workflow commands are not enough, optionally uploading images for the update comment. | yes | no | no | attached when available |
29
29
  | `rudder issue review <issue> --decision <decision> --comment <text>` | Record a structured reviewer decision with a required comment. | yes | no | no | attached when available |
30
+ | `rudder issue commit <issue> --sha <sha> --message <subject>` | Report a code commit created during issue work as structured issue activity. | yes | no | no | attached when available |
30
31
  | `rudder issue done <issue> --comment <text> [--image <path>]` | Mark an issue done with a required completion comment, optionally uploading images. | yes | no | no | attached when available |
31
32
  | `rudder issue block <issue> --comment <text> [--image <path>]` | Mark an issue blocked with a required blocker comment, optionally uploading images. | yes | no | no | attached when available |
32
33
  | `rudder issue release <issue>` | Release an issue back to todo and clear ownership. | yes | no | no | attached when available |
@@ -57,6 +58,8 @@ If an issue has a reviewer, moving it to `blocked` is also a reviewer handoff: t
57
58
 
58
59
  `--image` may be repeated. The CLI uploads each local PNG/JPEG/WebP/GIF as an issue attachment and appends Markdown image links to the comment text before sending it.
59
60
 
61
+ If your issue comment cites a screenshot path or visual validation artifact, attach that file with `--image <path>` instead of leaving only the local path in the text.
62
+
60
63
  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.
61
64
 
62
65
  ## Git Identity Policy