@rudderhq/agent-runtime-gemini-local 0.3.4-canary.31 → 0.3.4-canary.32

package/package.json

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

package/skills/rudder/SKILL.md

@@ -290,10 +290,12 @@ If asked to make or revise durable project work files, use the Library as a loca
 
 When you need to cite a Library file in a chat reply, issue comment, review, blocker, or done comment, use the `markdownLink` returned by `rudder library file ref "$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>" --json`. Do not hand-write `library-entry://...` URLs.
 
-Strong Library links look like normal Markdown, but the target is a stable Library entry id:
+Strong Library links look like normal Markdown, but the target contains only
+the stable Library entry id. Title and path are display or lookup details
+returned by Rudder, not URL metadata agents should encode:
 
 ```md
-[Project work file](library-entry://<entry-id>?t=Project+work+file&p=projects%2Fproject-name%2FRUD-123.md)
+[Project work file](library-entry://<entry-id>)
 ```
 
 Typical flow:
@@ -307,7 +309,7 @@ rudder issue comment "<issue-id-or-identifier>" --body-file "<path>" --json
 The `ref`, `put`, and `get` JSON responses include:
 
 - `libraryEntryId`: stable Library file identity
-- `mentionHref`: the raw `library-entry://...` target
+- `mentionHref`: the raw `library-entry://<entry-id>` target
 - `markdownLink`: the Markdown link to paste into the comment body
 
 For close-out comments, copy `markdownLink` from the JSON response into your temporary Markdown comment file and post that link as the Rudder-visible handoff checkpoint. Direct filesystem writes are not complete handoff evidence until the file is cited with the returned `markdownLink`. The `ref` argument is a Library-relative path such as `$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>`, not the absolute `$RUDDER_PROJECT_LIBRARY_ROOT/...` filesystem path. If `$RUDDER_PROJECT_LIBRARY_ROOT` is unset or inaccessible, use `rudder library file get/put "$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>"` as the remote or restricted runtime fallback. Use older `library-file://...` links only when you are preserving or reading legacy content that has no `libraryEntryId`.

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

@@ -111,7 +111,6 @@ Use the incremental `after` form when you already know the thread.
 ### Status and ownership mutations
 
 - `PATCH /api/issues/:issueId`
-- `POST /api/issues/:issueId/release`
 - `POST /api/issues/:issueId/approvals`
 
 `PATCH` accepts `comment` alongside mutable issue fields such as `status`, `priority`, `assigneeAgentId`, `assigneeUserId`, `reviewerAgentId`, `reviewerUserId`, `projectId`, `goalId`, and `parentId`.
@@ -195,8 +194,8 @@ Workspace file detail responses include renderable reference fields:
 {
   "filePath": "projects/rudder/RUD-123.md",
   "libraryEntryId": "entry-uuid",
-  "mentionHref": "library-entry://entry-uuid?t=RUD-123.md&p=projects%2Frudder%2FRUD-123.md",
-  "markdownLink": "[RUD-123.md](library-entry://entry-uuid?t=RUD-123.md&p=projects%2Frudder%2FRUD-123.md)"
+  "mentionHref": "library-entry://entry-uuid",
+  "markdownLink": "[RUD-123.md](library-entry://entry-uuid)"
 }
 ```
 

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

@@ -38,7 +38,6 @@ Direct API fallback is allowed for heartbeat close-out only when a required CLI
 | `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 |
 | `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 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 |
@@ -121,7 +120,7 @@ printf '%s\n' "$result" | jq -r .markdownLink
 The relevant JSON fields are:
 
 - `libraryEntryId`: stable identity for the Library file.
-- `mentionHref`: raw `library-entry://<id>?t=<title>&p=<path>` target.
+- `mentionHref`: raw `library-entry://<id>` target.
 - `markdownLink`: complete Markdown link that the renderer turns into a Library
   chip and that continues resolving after Rudder-managed rename or move.