@rudderhq/agent-runtime-opencode-local 0.4.2 → 0.4.3-canary.0

package/package.json

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

package/skills/rudder/SKILL.md

@@ -163,7 +163,7 @@ Important files and conventions:
 - If you encounter older `library-file://...` or `library-doc://...` links, treat them as legacy Rudder Library references. Prefer project Library resources going forward.
 - If you need broader org-wide resources, query the org resource catalog or inspect Library files explicitly instead of assuming they are already in the prompt.
 - Use Workspaces for disk-backed shared files and skill packages.
-- In local trusted runs, durable generated project work files belong under `$RUDDER_PROJECT_LIBRARY_ROOT`. Use `$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>` only when asking Rudder for a renderable reference. Use `/tmp` only for transient scratch files and temporary verification files.
+- In local trusted runs with project context, durable generated project work files belong under `$RUDDER_PROJECT_LIBRARY_ROOT`. Use `$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>` only when asking Rudder for a renderable reference. When there is no project context, write durable generated chat/work artifacts under the organization Library artifacts fallback `$RUDDER_ORG_WORKSPACE_ROOT/artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>` and cite the product locator `library:artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`. Do not choose an existing project, such as Getting Started, just to obtain a project Library path. Use `/tmp` only for transient scratch files and temporary verification files.
 - If a `resources.md` file exists, treat it like a normal workspace file rather than a reserved Rudder surface.
 - Agent-specific files live under `workspaces/agents/<workspace-key>/...`.
 - New projects do not create or configure their own workspace roots.
@@ -220,7 +220,9 @@ Do not fall back to raw `curl` for this workflow in local adapters or packaged d
 
 If asked to make or revise durable project work files, use the Library as a local file workspace. In local trusted runs with project context, write files directly under `$RUDDER_PROJECT_LIBRARY_ROOT` with normal filesystem tools. `library:projects/<project-key>/...` is the Rudder product locator for those files, not the Markdown link syntax and not a reason to route ordinary local edits through the CLI.
 
-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.
+If there is no project context, write durable generated chat/work artifacts under the organization Library artifacts fallback instead: `$RUDDER_ORG_WORKSPACE_ROOT/artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`, with product locator `library:artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`. Use the current date and a concise slug of the current chat/thread title for `<conversation-title>`. Do not choose an existing project, such as Getting Started, just to obtain a project Library path.
+
+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` with project context, or `rudder library file ref "artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>" --json` without project context. Do not hand-write `library-entry://...` URLs.
 
 Strong Library links look like normal Markdown. The stable Library entry id is
 the identity; Rudder may add a `p` query parameter as a synchronous path hint so
@@ -247,7 +249,7 @@ The `ref`, `put`, and `get` JSON responses include:
   Rudder-generated `?p=<url-encoded-path-hint>`
 - `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`.
+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>` or `artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`, not an absolute filesystem path. If `$RUDDER_PROJECT_LIBRARY_ROOT` is unset or inaccessible but `$RUDDER_PROJECT_LIBRARY_PATH` exists, use `rudder library file get/put "$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>"` as the remote or restricted runtime fallback. If there is no project context, use the organization artifacts fallback path instead. Use older `library-file://...` links only when you are preserving or reading legacy content that has no `libraryEntryId`.
 
 Planning rules:
 

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

@@ -182,9 +182,13 @@ Project mutation policy:
 ### Library Workspace Files
 
 Local trusted agents should use normal filesystem tools under
-`$RUDDER_PROJECT_LIBRARY_ROOT` for durable project files. API fallback for
-Library files is for debugging, compatibility, remote runtimes, or restricted
-runtimes that cannot access the local Library filesystem.
+`$RUDDER_PROJECT_LIBRARY_ROOT` for durable project files when the run has project
+context. When there is no project context, durable generated chat/work artifacts
+belong under the organization Library artifacts fallback:
+`$RUDDER_ORG_WORKSPACE_ROOT/artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`
+with product locator `library:artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`.
+API fallback for Library files is for debugging, compatibility, remote runtimes,
+or restricted runtimes that cannot access the local Library filesystem.
 
 - `GET /api/orgs/:orgId/workspace/files?path=:directory`
 - `GET /api/orgs/:orgId/workspace/file?path=:file`
@@ -204,15 +208,19 @@ Workspace file detail responses include renderable reference fields:
 ```
 
 Agents should paste `markdownLink` into issue comments and close-out notes. In
-normal local runs, obtain that field with
+normal local project-context runs, obtain that field with
 `rudder library file ref "$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>" --json`
-after writing the file directly. The `ref` path is Library-relative, not the
-absolute `$RUDDER_PROJECT_LIBRARY_ROOT/...` filesystem path. Posting that
-returned link is the Rudder-visible handoff checkpoint for direct filesystem
-writes. If `$RUDDER_PROJECT_LIBRARY_ROOT` is unset or inaccessible, use
+after writing the file directly. With no project context, obtain it with
+`rudder library file ref "artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>" --json`.
+The `ref` path is Library-relative, not an absolute filesystem path such as
+`$RUDDER_PROJECT_LIBRARY_ROOT/...` or `$RUDDER_ORG_WORKSPACE_ROOT/...`. Posting
+that returned link is the Rudder-visible handoff checkpoint for direct filesystem
+writes. If `$RUDDER_PROJECT_LIBRARY_ROOT` is unset or inaccessible but
+`$RUDDER_PROJECT_LIBRARY_PATH` exists, use
 `rudder library file get/put "$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>"` as
-the remote or restricted runtime fallback. `library-file://...` is legacy weak
-path syntax and should not be used for new durable Library references when
+the remote or restricted runtime fallback. If there is no project context, use
+the organization artifacts fallback path instead. `library-file://...` is legacy
+weak path syntax and should not be used for new durable Library references when
 `libraryEntryId` is available.
 
 The `libraryEntryId` remains the strong identity. The optional `p` query value

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

@@ -123,7 +123,12 @@ If `RUDDER_WAKE_REASON=issue_passive_followup`, the run is issue follow-up for t
 
 Agents should not hand-write `library-entry://...` URLs. Local trusted agents
 should create and update durable project files directly under
-`$RUDDER_PROJECT_LIBRARY_ROOT` with normal filesystem tools. After creating,
+`$RUDDER_PROJECT_LIBRARY_ROOT` with normal filesystem tools when the run has
+project context. When there is no project context, write durable generated
+chat/work artifacts under
+`$RUDDER_ORG_WORKSPACE_ROOT/artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`
+and reference the Library-relative product path
+`artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>`. After creating,
 updating, or reading a durable Library file, use `rudder library file ref` to
 get the CLI-returned `markdownLink` for issue comments, review comments,
 blocker notes, done comments, and chat replies.
@@ -132,6 +137,11 @@ blocker notes, done comments, and chat replies.
 printf '%s\n' "<markdown body>" > "$RUDDER_PROJECT_LIBRARY_ROOT/<issue>.md"
 result="$(rudder library file ref "$RUDDER_PROJECT_LIBRARY_PATH/<issue>.md" --json)"
 printf '%s\n' "$result" | jq -r .markdownLink
+
+mkdir -p "$RUDDER_ORG_WORKSPACE_ROOT/artifacts/YYYY-MM-DD/<conversation-title>"
+printf '%s\n' "<markdown body>" > "$RUDDER_ORG_WORKSPACE_ROOT/artifacts/YYYY-MM-DD/<conversation-title>/<artifact>.md"
+result="$(rudder library file ref "artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>" --json)"
+printf '%s\n' "$result" | jq -r .markdownLink
 ```
 
 The relevant JSON fields are:
@@ -148,13 +158,17 @@ Use `rudder library file get/put` only when local filesystem access to the
 Library is unavailable, such as remote or restricted runtimes. `rudder library
 file link <path> --json` remains as a compatibility alias for `ref`. The
 `ref` path is Library-relative, for example
-`$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>`; do not pass the absolute
-`$RUDDER_PROJECT_LIBRARY_ROOT/...` filesystem path. Posting the returned
-`markdownLink` is the Rudder-visible handoff checkpoint for direct filesystem
-writes. If `$RUDDER_PROJECT_LIBRARY_ROOT` is unset or inaccessible, use
+`$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>` with project context or
+`artifacts/YYYY-MM-DD/<conversation-title>/<relative-file>` without project
+context; do not pass absolute filesystem paths such as
+`$RUDDER_PROJECT_LIBRARY_ROOT/...` or `$RUDDER_ORG_WORKSPACE_ROOT/...`. Posting
+the returned `markdownLink` is the Rudder-visible handoff checkpoint for direct
+filesystem writes. If `$RUDDER_PROJECT_LIBRARY_ROOT` is unset or inaccessible
+but `$RUDDER_PROJECT_LIBRARY_PATH` exists, use
 `rudder library file get/put "$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>"` as
-the remote or restricted runtime fallback. Treat `library-file://...` as legacy
-weak path syntax and use it only when preserving old content that has no
+the remote or restricted runtime fallback. If there is no project context, use
+the organization artifacts fallback path instead. Treat `library-file://...` as
+legacy weak path syntax and use it only when preserving old content that has no
 `libraryEntryId`.
 
 ## Git Identity Policy