@rudderhq/agent-runtime-cursor-local 0.2.9-canary.6 → 0.2.9-canary.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rudderhq/agent-runtime-cursor-local",
-  "version": "0.2.9-canary.6",
+  "version": "0.2.9-canary.8",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/Undertone0809/rudder",
   "bugs": {
@@ -67,7 +67,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@rudderhq/agent-runtime-utils": "0.2.9-canary.6",
+    "@rudderhq/agent-runtime-utils": "0.2.9-canary.8",
     "picocolors": "^1.1.1"
   },
   "devDependencies": {

package/skills/rudder/SKILL.md

@@ -199,12 +199,11 @@ rudder issue block "<issue-id-or-identifier>" --comment-file "<path>" [--image "
 
 - generic patch when workflow commands are not enough:
 
-Use file or stdin input for issue comments. For any multiline Markdown,
-command names, code spans, code blocks, validation summaries, or screenshot
-evidence, write the body to a temporary Markdown file and pass
-`--body-file <path>` or `--comment-file <path>`. Pass `-` to read from stdin.
-Do not place shell-sensitive Markdown containing backticks or `$()` directly
-inside a shell argument.
+Issue comment and close-out commands accept comment bodies only from files or
+stdin. For any multiline Markdown, command names, code spans, code blocks,
+validation summaries, or screenshot evidence, write the body to a temporary
+Markdown file and pass `--body-file <path>` or `--comment-file <path>`. Pass
+`-` to read from stdin.
 
 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.
 
@@ -275,7 +274,7 @@ Typical flow:
 ```bash
 rudder issue documents get "<issue-id-or-identifier>" plan --json
 rudder issue documents revisions "<issue-id-or-identifier>" plan --json
-rudder issue documents put "<issue-id-or-identifier>" plan --title "Plan" --format markdown --body "<markdown>" --json
+rudder issue documents put "<issue-id-or-identifier>" plan --title "Plan" --format markdown --body-file "<path>" --json
 rudder issue comment "<issue-id-or-identifier>" --body-file "<path>" --json
 ```
 

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

@@ -40,11 +40,11 @@ Direct API fallback is allowed for heartbeat close-out only when a required CLI
 | `rudder issue release <issue>` | Release an issue back to todo and clear ownership. | yes | no | no | attached when available |
 | `rudder issue documents list <issue>` | List issue documents. | no | no | no | no |
 | `rudder issue documents get <issue> <key>` | Read one issue document by key. | no | no | no | no |
-| `rudder issue documents put <issue> <key> --body <text>` | Create or update an issue document. | yes | no | no | attached when available |
+| `rudder issue documents put <issue> <key> --body-file <path>` | Create or update an issue document. | yes | no | no | attached when available |
 | `rudder issue documents revisions <issue> <key>` | List revisions for an issue document. | no | no | no | no |
 | `rudder approval get <approval-id>` | Read one approval request. | no | no | no | no |
 | `rudder approval issues <approval-id>` | List the issues linked to an approval. | no | no | no | no |
-| `rudder approval comment <approval-id> --body <text>` | Add a comment to an approval. | yes | no | no | attached when available |
+| `rudder approval comment <approval-id> --body-file <path>` | Add a comment to an approval. | yes | no | no | attached when available |
 | `rudder skill list --org-id <id>` | List organization-visible skills. | no | required | no | no |
 | `rudder skill get <skill-id> --org-id <id>` | Read one organization skill detail. | no | required | no | no |
 | `rudder skill file <skill-id> --org-id <id> [--path SKILL.md]` | Read one file from an organization skill package. | no | required | no | no |
@@ -63,7 +63,7 @@ Before a successful `todo` or `in_progress` issue run exits, leave one close-out
 
 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`.
 
-Use file or stdin comment input 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. Do not place shell-sensitive Markdown containing backticks or `$()` directly inside a shell argument.
+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.
 
 `--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.
 

package/skills/rudder-create-agent/SKILL.md

@@ -136,13 +136,16 @@ If the hire response includes `approval`, monitor and discuss on the approval th
 
 ```sh
 rudder approval get "<approval-id>" --json
-rudder approval comment "<approval-id>" --body "## CTO hire request submitted
+cat > /tmp/rudder-approval-comment.md <<'EOF'
+## CTO hire request submitted
 
 - Approval: [<approval-id>](/<prefix>/messenger/approvals/<approval-id>)
 - Pending agent: [<agent-ref>](/<prefix>/agents/<agent-url-key-or-id>)
 - Source issue: [<issue-ref>](/<prefix>/issues/<issue-identifier-or-id>)
 
-Updated prompt and adapter config per board feedback." --json
+Updated prompt and adapter config per board feedback.
+EOF
+rudder approval comment "<approval-id>" --body-file /tmp/rudder-approval-comment.md --json
 rudder approval resubmit "<approval-id>" --payload '{"title":"Revised title","agentRuntimeConfig":{"cwd":"/abs/path/to/repo","model":"o4-mini"}}' --json
 rudder approval issues "<approval-id>" --json
 ```

package/skills/rudder-create-agent/references/api-reference.md

@@ -16,7 +16,7 @@ Internal/debug reference for the bundled `rudder-create-agent` skill.
 | `rudder agent config get <agentId>` | `GET /api/agents/:agentId/configuration` |
 | `rudder agent hire --org-id <orgId> --payload <json>` | `POST /api/orgs/:orgId/agent-hires` |
 | `rudder approval get <approvalId>` | `GET /api/approvals/:approvalId` |
-| `rudder approval comment <approvalId> --body <text>` | `POST /api/approvals/:approvalId/comments` |
+| `rudder approval comment <approvalId> --body-file <path>` | `POST /api/approvals/:approvalId/comments` |
 | `rudder approval resubmit <approvalId> [--payload <json>]` | `POST /api/approvals/:approvalId/resubmit` |
 | `rudder approval issues <approvalId>` | `GET /api/approvals/:approvalId/issues` |
 

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

@@ -83,7 +83,7 @@ Do not use `rudder approval create --type hire_agent` as a replacement for `agen
 
 ```sh
 rudder approval get "<approval-id>" --json
-rudder approval comment "<approval-id>" --body "<markdown>" --json
+rudder approval comment "<approval-id>" --body-file "<path>" --json
 rudder approval resubmit "<approval-id>" --payload '{"...":"..."}' --json
 rudder approval issues "<approval-id>" --json
 ```