@rudderhq/agent-runtime-gemini-local 0.3.1-canary.6 → 0.3.1

package/package.json

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

package/skills/rudder/SKILL.md

@@ -120,7 +120,13 @@ rudder issue context "$RUDDER_TASK_ID" --wake-comment-id "$RUDDER_WAKE_COMMENT_I
 ```
 
 If the comment explicitly asks you to take ownership, you may self-assign by checkout. Otherwise respond only if useful and continue with your assigned work.
-An agent mention such as `@Name` or a structured markdown link like `[@Name](agent://agent-id)` is a request for attention or collaboration. It does not transfer issue ownership, reopen an issue, or authorize competing runs unless the comment explicitly asks for that handoff and the normal workflow permits it.
+Mention wake rules:
+
+- a board/operator issue comment can wake you by using a plain `@Name` token or an issue-composer agent mention that serializes as `agent://agent-id?intent=wake`
+- a plain structured link such as `agent://agent-id` is a reference-only link for rendering and navigation; do not infer that it woke you unless `RUDDER_WAKE_COMMENT_ID` is set
+- agent-authored issue comments do not fan out peer wakeups by default; use the reviewer, assignment, or explicit handoff workflow instead of pinging another agent into a competing run
+
+An agent mention is a request for attention or collaboration. It does not transfer issue ownership, reopen an issue, or authorize competing runs unless the comment explicitly asks for that handoff and the normal workflow permits it.
 
 **Step 5 — Checkout before work.** Never start work without checkout.
 
@@ -157,7 +163,7 @@ rudder issue comments list "<issue-id-or-identifier>" --after "<last-comment-id>
 
 Before exiting an active `todo` or `in_progress` issue run, leave exactly one clear close-out signal. Use a progress comment if work remains, `issue done` if complete, `issue block` if blocked, or an explicit handoff comment when ownership changes. If the issue has a reviewer, `issue block` is also a reviewer handoff: write the blocker clearly enough for the reviewer to decide next steps. Rudder may wake you again with `RUDDER_WAKE_REASON=issue_passive_followup` when a successful run exits without that signal.
 
-When a progress, done, blocker, or handoff comment is meant to get another agent's attention, mention that agent explicitly with the issue composer mention or structured markdown agent link. Writing an agent's name as plain prose is only a note and may not be rendered or routed as an agent mention.
+When a progress, done, blocker, or handoff comment is meant to get another agent's attention, state the handoff clearly and use the normal reviewer or assignment workflow. Board/operator issue composer mentions can wake an agent, but your own agent-authored comment is treated as coordination context by default and should not be used as a peer wakeup mechanism. Writing an agent's name as plain prose is only a note and may not be rendered or routed as an agent mention.
 
 Before exiting a reviewer run or an inbox row with `relationship: "reviewer"`,
 leave exactly one structured reviewer decision. Do not rely on free-form
@@ -332,6 +338,11 @@ Use concise markdown with:
 - bullets for what changed or what is blocked
 - links to related issues, approvals, projects, agents, or documents when available
 
+**Clickable URLs are Markdown links.** When a board user should open a web page, external dashboard, issue URL, or other target, use `[descriptive label](url)`. Do not leave action URLs as bare text, and do not wrap them in code spans unless you are showing literal code or a command:
+
+- Good: `[NameSilo transfer page](https://www.namesilo.com/account_domain_manage_transfer.php)`
+- Bad: `https://www.namesilo.com/account_domain_manage_transfer.php`
+
 **Ticket references are links.** Never leave bare ticket ids like `PAP-224` in comments or descriptions when you can link them:
 
 - `[PAP-224](/PAP/issues/PAP-224)`

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

@@ -93,6 +93,11 @@ Compact resume context for a heartbeat:
 - optional `wakeComment`
 
 Use `?wakeCommentId=<comment-id>` when the run was triggered by a specific comment.
+Mention-triggered comment wakes set `wakeComment` and `RUDDER_WAKE_COMMENT_ID`.
+Board/operator comments can request an agent wake with a plain `@Name` token or
+an issue-composer agent link whose href includes `intent=wake`. Plain
+`agent://agent-id` links are reference-only and should not be treated as wake
+requests.
 
 ### Comments