@rudderhq/server 0.2.10-canary.30 → 0.2.10-canary.31

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rudderhq/server",
3
- "version": "0.2.10-canary.30",
3
+ "version": "0.2.10-canary.31",
4
4
  "license": "SEE LICENSE IN LICENSE",
5
5
  "homepage": "https://github.com/Undertone0809/rudder",
6
6
  "bugs": {
@@ -53,18 +53,18 @@
53
53
  "@langfuse/otel": "^5.1.0",
54
54
  "@langfuse/tracing": "^5.1.0",
55
55
  "@opentelemetry/sdk-trace-node": "^2.1.0",
56
- "@rudderhq/agent-runtime-claude-local": "0.2.10-canary.30",
57
- "@rudderhq/agent-runtime-codex-local": "0.2.10-canary.30",
58
- "@rudderhq/agent-runtime-cursor-local": "0.2.10-canary.30",
59
- "@rudderhq/agent-runtime-gemini-local": "0.2.10-canary.30",
60
- "@rudderhq/agent-runtime-openclaw-gateway": "0.2.10-canary.30",
61
- "@rudderhq/agent-runtime-opencode-local": "0.2.10-canary.30",
62
- "@rudderhq/agent-runtime-pi-local": "0.2.10-canary.30",
63
- "@rudderhq/agent-runtime-utils": "0.2.10-canary.30",
64
- "@rudderhq/db": "0.2.10-canary.30",
65
- "@rudderhq/plugin-sdk": "0.2.10-canary.30",
66
- "@rudderhq/run-intelligence-core": "0.2.10-canary.30",
67
- "@rudderhq/shared": "0.2.10-canary.30",
56
+ "@rudderhq/agent-runtime-claude-local": "0.2.10-canary.31",
57
+ "@rudderhq/agent-runtime-codex-local": "0.2.10-canary.31",
58
+ "@rudderhq/agent-runtime-cursor-local": "0.2.10-canary.31",
59
+ "@rudderhq/agent-runtime-gemini-local": "0.2.10-canary.31",
60
+ "@rudderhq/agent-runtime-openclaw-gateway": "0.2.10-canary.31",
61
+ "@rudderhq/agent-runtime-opencode-local": "0.2.10-canary.31",
62
+ "@rudderhq/agent-runtime-pi-local": "0.2.10-canary.31",
63
+ "@rudderhq/agent-runtime-utils": "0.2.10-canary.31",
64
+ "@rudderhq/db": "0.2.10-canary.31",
65
+ "@rudderhq/plugin-sdk": "0.2.10-canary.31",
66
+ "@rudderhq/run-intelligence-core": "0.2.10-canary.31",
67
+ "@rudderhq/shared": "0.2.10-canary.31",
68
68
  "ajv": "^8.18.0",
69
69
  "ajv-formats": "^3.0.1",
70
70
  "better-auth": "1.4.18",
@@ -298,6 +298,7 @@ Planning rules:
298
298
 
299
299
  - do not mark the issue done when the request was only to create or revise a plan
300
300
  - reassign back to the requester if that is the expected workflow
301
+ - 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
301
302
  - when you reference the plan in comments, link to the Library file with `library-file://file?p=<url-encoded-relative-path>`
302
303
  - `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.
303
304
 
@@ -101,7 +101,7 @@ Notes:
101
101
  - Rudder now uses one fixed org workspace root at `~/.rudder/instances/<instance>/organizations/<org-id>/workspaces`.
102
102
  - `scan-projects` should be treated as a compatibility command that scans the shared org workspace plus any legacy project workspace records that still exist.
103
103
  - The org `Resources` catalog is the canonical place to register shared repos, docs, URLs, and connector objects for agents.
104
- - Workspaces remains the disk-backed shared file surface; durable project work belongs under `library:projects/<project-name>/`.
104
+ - Workspaces remains the disk-backed shared file surface; durable project work belongs under `library:projects/<project-name>/`. When a run creates or updates a durable Library file, its final chat reply or issue comment should include a user-visible Markdown link to that file.
105
105
 
106
106
  ## Inspect Imported Skills
107
107
 
@@ -298,6 +298,7 @@ Planning rules:
298
298
 
299
299
  - do not mark the issue done when the request was only to create or revise a plan
300
300
  - reassign back to the requester if that is the expected workflow
301
+ - 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
301
302
  - when you reference the plan in comments, link to the Library file with `library-file://file?p=<url-encoded-relative-path>`
302
303
  - `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.
303
304
 
@@ -101,7 +101,7 @@ Notes:
101
101
  - Rudder now uses one fixed org workspace root at `~/.rudder/instances/<instance>/organizations/<org-id>/workspaces`.
102
102
  - `scan-projects` should be treated as a compatibility command that scans the shared org workspace plus any legacy project workspace records that still exist.
103
103
  - The org `Resources` catalog is the canonical place to register shared repos, docs, URLs, and connector objects for agents.
104
- - Workspaces remains the disk-backed shared file surface; durable project work belongs under `library:projects/<project-name>/`.
104
+ - Workspaces remains the disk-backed shared file surface; durable project work belongs under `library:projects/<project-name>/`. When a run creates or updates a durable Library file, its final chat reply or issue comment should include a user-visible Markdown link to that file.
105
105
 
106
106
  ## Inspect Imported Skills
107
107