@rudderhq/agent-runtime-gemini-local 0.2.0-canary.26 → 0.2.0-canary.28

package/package.json

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

package/skills/rudder/SKILL.md

@@ -175,6 +175,8 @@ rudder issue review "<issue-id-or-identifier>" --decision needs_followup --comme
 rudder issue review "<issue-id-or-identifier>" --decision blocked --comment "<markdown>" --json
 ```
 
+Use `blocked` to confirm a human/external blocker. The comment must name the next human action; Rudder records a human handoff and removes the issue from repeated reviewer pickup until the board changes the issue.
+
 - progress-only update:
 
 ```bash
@@ -197,6 +199,8 @@ rudder issue block "<issue-id-or-identifier>" --comment "<markdown>" [--image "<
 
 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.
 
+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.
+
 ```bash
 rudder issue update "<issue-id-or-identifier>" ... --json
 ```
@@ -207,6 +211,8 @@ rudder issue update "<issue-id-or-identifier>" ... --json
 rudder issue create --org-id "$RUDDER_ORG_ID" ... --json
 ```
 
+When you create an issue as an authenticated agent without an assignee, Rudder assigns it to you by default. Pass an explicit assignee only when the new issue should belong to someone else.
+
 Always set `parentId`. Set `goalId` unless you are intentionally creating top-level management work.
 
 ## Organization Skills Workflow
@@ -223,9 +229,18 @@ rudder skill import --org-id "$RUDDER_ORG_ID" --source "<source>" --json
 rudder skill list --org-id "$RUDDER_ORG_ID" --json
 rudder skill get "<skill-id>" --org-id "$RUDDER_ORG_ID" --json
 rudder skill file "<skill-id>" --org-id "$RUDDER_ORG_ID" --path SKILL.md --json
+rudder agent skills enable "<agent-id>" "<selection-ref>" --json
 rudder agent skills sync "<agent-id>" --desired-skills "<csv>" --json
 ```
 
+Use `skills enable` when adding one or more skills because it preserves the
+agent's existing enabled selections. Use `skills sync` only when you intend to
+replace the full optional enabled-skill set.
+
+After creating or copying a skill under `AGENT_HOME/skills/<slug>/`, check the
+agent's Skills snapshot. If the skill is installed but not enabled, say:
+installed but not enabled; future runs will not load it until enabled.
+
 Do not fall back to raw `curl` for this workflow in local adapters or packaged desktop.
 
 ## Planning And Issue Documents

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

@@ -16,6 +16,7 @@ Stable CLI contract for agents using the bundled `rudder` skill. Prefer these co
 | `rudder agent me` | Show the authenticated agent identity, budget, and chain of command. | no | no | no | no |
 | `rudder agent inbox` | List the compact assignee and reviewer work inbox for the authenticated agent. | no | no | no | no |
 | `rudder agent capabilities` | List the stable Rudder agent command contract. | no | no | no | no |
+| `rudder agent skills enable <agent-id> <selection-ref...>` | Add skill selections to an agent without replacing existing enabled skills. | yes | no | no | attached when available |
 | `rudder agent skills sync <agent-id>` | Sync the desired enabled skill set for an agent. | yes | no | no | attached when available |
 | `rudder issue get <issue>` | Read a full issue by UUID or identifier. | no | no | no | no |
 | `rudder issue search <query> [--org-id <id>]` | Search issues with the server-side issue index across title, identifier, description, and comments. | no | required | no | no |
@@ -26,6 +27,7 @@ Stable CLI contract for agents using the bundled `rudder` skill. Prefer these co
 | `rudder issue comments get <issue> <comment-id>` | Read one issue comment by id. | no | no | no | no |
 | `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 |
 | `rudder issue review <issue> --decision <decision> --comment <text>` | Record a structured reviewer decision with a required comment. | yes | no | no | attached when available |
+| `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 <text> [--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 <text> [--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 |
@@ -56,6 +58,8 @@ If an issue has a reviewer, moving it to `blocked` is also a reviewer handoff: t
 
 `--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.
 
+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.
+
 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.
 
 ## Git Identity Policy
@@ -69,9 +73,9 @@ When the inbox row or wake context says `relationship: "reviewer"`, `role: "revi
 - approve: `rudder issue review <issue> --decision approve --comment <text>`
 - request changes: `rudder issue review <issue> --decision request_changes --comment <text>`
 - needs follow-up: `rudder issue review <issue> --decision needs_followup --comment <text>`
-- blocked or blocker confirmed: `rudder issue review <issue> --decision blocked --comment <text>`
+- blocked or blocker confirmed: `rudder issue review <issue> --decision blocked --comment <text>`; use this only for a confirmed human/external blocker and name the next human action.
 
-Do not rely on a free-form reject or accept comment as the review outcome. The structured decision is the durable close-out signal.
+Do not rely on a free-form reject or accept comment as the review outcome. The structured decision is the durable close-out signal. A blocked reviewer decision records a human handoff and removes the issue from repeated reviewer pickup until the board changes the issue.
 
 ## Compatibility Commands
 
@@ -83,6 +87,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 allowed agent icon names for create and hire payloads.
-- `rudder issue create --org-id <id> ...` — Create a new issue or subtask with the generic issue surface.
+- `rudder issue create --org-id <id> ...` — 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 approval create --org-id <id> --type <type> --payload <json>` — Create a new approval request.
 - `rudder approval resubmit <approval-id> [--payload <json>]` — Resubmit a revision-requested approval, optionally with updated payload.

package/skills/rudder/references/organization-skills.md

@@ -8,7 +8,7 @@ This workflow is now **CLI-first** for the bundled `rudder` skill.
 
 1. import or scan the skill into the organization library
 2. inspect the imported skill if needed
-3. sync the desired enabled skills onto the target agent
+3. enable the desired skills on the target agent
 
 ## Core CLI Surface
 
@@ -19,6 +19,7 @@ rudder skill file "<skill-id>" --org-id "$RUDDER_ORG_ID" --path SKILL.md --json
 rudder skill import --org-id "$RUDDER_ORG_ID" --source "<source>" --json
 rudder skill scan-local --org-id "$RUDDER_ORG_ID" --roots "<csv>" --json
 rudder skill scan-projects --org-id "$RUDDER_ORG_ID" --project-ids "<csv>" --workspace-ids "<csv>" --json
+rudder agent skills enable "<agent-id>" "<selection-ref>" --json
 rudder agent skills sync "<agent-id>" --desired-skills "<csv>" --json
 ```
 
@@ -124,26 +125,30 @@ rudder skill file "<skill-id>" --org-id "$RUDDER_ORG_ID" --path references/notes
 - exact slug when it is unique in the organization
 
 ```bash
-rudder agent skills sync \
+rudder agent skills enable \
   "<agent-id>" \
-  --desired-skills "vercel-labs/agent-browser/agent-browser" \
+  "vercel-labs/agent-browser/agent-browser" \
   --json
 ```
 
 For multiple skills:
 
 ```bash
-rudder agent skills sync \
+rudder agent skills enable \
   "<agent-id>" \
-  --desired-skills "agent-browser,design-md" \
+  "agent-browser" "design-md" \
   --json
 ```
 
+`rudder agent skills enable` is additive and preserves existing enabled
+selections. Use `rudder agent skills sync --desired-skills` only when replacing
+the full optional enabled-skill set intentionally.
+
 ## Permission Model
 
 - organization skill reads: any same-organization actor
 - organization skill mutations: board, CEO, or an agent with effective `agents:create`
-- agent skill sync: same permission model as updating that agent
+- agent skill enable/sync: same permission model as updating that agent
 
 ## Notes
 
@@ -151,5 +156,5 @@ rudder agent skills sync \
 - New organizations also seed optional community preset skills into the organization library. They stay organization-managed and default-off for agents.
 - If a skill reference is missing or ambiguous, Rudder returns `422`.
 - Prefer linking back to the relevant issue, approval, and agent when commenting about skill changes.
-- This document only covers library import/inspect/sync.
+- This document only covers library import/inspect/enable/sync.
 - Hire and create flows now live on the CLI-first `rudder-create-agent` path.

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

@@ -129,6 +129,7 @@ Post-hire adjustments use the normal agent and skill surfaces:
 
 ```sh
 rudder agent get "<agent-id-or-shortname>" --org-id "$RUDDER_ORG_ID" --json
+rudder agent skills enable "<agent-id>" "<selection-ref>" --json
 rudder agent skills sync "<agent-id>" --desired-skills "<csv>" --json
 rudder agent local-cli "<agent-id-or-shortname>" --org-id "$RUDDER_ORG_ID" --json
 ```