@rudderhq/agent-runtime-gemini-local 0.3.4-canary.21 → 0.3.4-canary.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rudderhq/agent-runtime-gemini-local",
-  "version": "0.3.4-canary.21",
+  "version": "0.3.4-canary.22",
   "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.3.4-canary.21",
+    "@rudderhq/agent-runtime-utils": "0.3.4-canary.22",
     "picocolors": "^1.1.1"
   },
   "devDependencies": {

package/skills/rudder/SKILL.md

@@ -318,7 +318,7 @@ Planning rules:
 - reassign back to the requester if that is the expected workflow
 - when you create or update a durable Library file, always include a user-visible Markdown link to that file in your final chat reply or issue comment
 - when you reference the plan in comments, use the `markdownLink` returned by `rudder library file ref ... --json`
-- `rudder issue documents ...` is a legacy compatibility surface for older DB-backed issue documents. Read it when a prompt explicitly points to an existing legacy issue document; do not use it for new durable files.
+- `rudder issue documents ...` has been retired. Use Project Library files for durable plans/specs and cite them from issue text or comments.
 
 ## Critical Rules
 
@@ -365,7 +365,6 @@ Use concise markdown with:
 - issues: `/<prefix>/issues/<issue-identifier>`
 - issue comments: `/<prefix>/issues/<issue-identifier>#comment-<comment-id>`
 - Library files: `/<prefix>/library?path=<url-encoded-relative-path>`
-- legacy issue documents: `/<prefix>/issues/<issue-identifier>#document-<document-key>`
 - agents: `/<prefix>/agents/<agent-url-key>`
 - projects: `/<prefix>/projects/<project-url-key>`
 - approvals: `/<prefix>/messenger/approvals/<approval-id>`

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

@@ -108,15 +108,6 @@ requests.
 
 Use the incremental `after` form when you already know the thread.
 
-### Documents
-
-- `GET /api/issues/:issueId/documents`
-- `GET /api/issues/:issueId/documents/:key`
-- `PUT /api/issues/:issueId/documents/:key`
-- `GET /api/issues/:issueId/documents/:key/revisions`
-
-When updating an existing document, send the latest `baseRevisionId` or the API will reject concurrent overwrites.
-
 ### Status and ownership mutations
 
 - `PATCH /api/issues/:issueId`

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

@@ -39,9 +39,6 @@ Direct API fallback is allowed for heartbeat close-out only when a required CLI
 | `rudder issue done <issue> --comment-file <path> [--image <path>]` | Mark an issue done with a required completion comment, optionally uploading images. | yes | no | no | attached when available |
 | `rudder issue block <issue> --comment-file <path> [--image <path>]` | Mark an issue blocked with a required blocker comment, optionally uploading images. | 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 |
-| `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 revisions <issue> <key>` | List revisions for an issue document. | no | no | no | no |
 | `rudder project list --org-id <id>` | List projects in an organization. | no | required | no | no |
 | `rudder project get <project-id-or-shortname> [--org-id <id>]` | Read one project by ID or shortname. | no | no | no | no |
 | `rudder project create --org-id <id> --name <name>` | Create a project in the organization. | yes | required | no | attached when available |
@@ -166,7 +163,6 @@ Do not rely on a free-form reject or accept comment as the review outcome. The s
 - `rudder agent config list --org-id <id>` — List redacted agent configuration snapshots for an organization.
 - `rudder agent config get <agent-id-or-shortname>` — Read one redacted agent configuration snapshot by id or shortname.
 - `rudder agent icons` — List legacy named agent icons for compatibility/debugging; normal create and hire payloads should omit icon.
-- `rudder issue documents put <issue> <key> --body-file <path>` — Legacy create or update of a DB-backed issue document; prefer local project Library files under `$RUDDER_PROJECT_LIBRARY_ROOT` for durable project files.
 - `rudder issue create --org-id <id> ... [--label-id <id> ...] [--label <name> ...]` — Create a new issue or subtask with the generic issue surface; agent-created issues default to the creating agent when no assignee is supplied.
 - `rudder issue labels list --org-id <id>` — List organization issue labels available for issue creation.
 - `rudder approval create --org-id <id> --type <type> --payload <json>` — Create a new approval request.