@rudderhq/agent-runtime-codex-local 0.2.10-canary.14 → 0.2.10-canary.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rudderhq/agent-runtime-codex-local",
-  "version": "0.2.10-canary.14",
+  "version": "0.2.10-canary.16",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/Undertone0809/rudder",
   "bugs": {
@@ -68,7 +68,7 @@
     "probe:quota": "pnpm exec tsx src/cli/quota-probe.ts --json"
   },
   "dependencies": {
-    "@rudderhq/agent-runtime-utils": "0.2.10-canary.14",
+    "@rudderhq/agent-runtime-utils": "0.2.10-canary.16",
     "picocolors": "^1.1.1"
   },
   "devDependencies": {

package/skills/rudder/SKILL.md

@@ -62,6 +62,14 @@ Important files and conventions:
 - 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.
+- When the operator asks you to create or maintain project records, use the
+  stable CLI instead of ad hoc API calls:
+
+```bash
+rudder project list --org-id "$RUDDER_ORG_ID" --json
+rudder project create --org-id "$RUDDER_ORG_ID" --name "<name>" --json
+rudder project update "<project-id-or-shortname>" --org-id "$RUDDER_ORG_ID" --status in_progress --json
+```
 
 ## Heartbeat Procedure
 

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

@@ -136,6 +136,8 @@ When updating an existing document, send the latest `baseRevisionId` or the API
 - `GET /api/orgs/:orgId/dashboard`
 - `GET /api/orgs/:orgId/projects`
 - `POST /api/orgs/:orgId/projects`
+- `GET /api/projects/:projectIdOrShortname?orgId=:orgId`
+- `PATCH /api/projects/:projectIdOrShortname?orgId=:orgId`
 - `GET /api/orgs/:orgId/goals`
 - `POST /api/orgs/:orgId/goals`
 - `GET /api/orgs/:orgId/activity`
@@ -172,6 +174,13 @@ Loading policy:
 - If you need org-wide background that was not attached to the current project,
   query the org catalog explicitly.
 
+Project mutation policy:
+
+- Agent keys may create and update projects inside their own organization. They
+  cannot access or mutate projects in another organization.
+- Project create/update requests write activity log entries with the agent
+  actor and run id when the CLI attaches one.
+
 ## Approval Workflows
 
 - `GET /api/approvals/:approvalId`

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

@@ -41,6 +41,10 @@ Direct API fallback is allowed for heartbeat close-out only when a required CLI
 | `rudder issue documents list <issue>` | List issue documents. | no | no | no | no |
 | `rudder issue documents get <issue> <key>` | Read one issue document by key. | no | no | no | no |
 | `rudder issue documents revisions <issue> <key>` | List revisions for an issue document. | no | no | no | no |
+| `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 |
+| `rudder project update <project-id-or-shortname> [--org-id <id>]` | Update mutable project fields such as name, description, status, goals, lead agent, target date, color, or archivedAt. | yes | no | no | attached when available |
 | `rudder library file list [directory]` | List path-based Library files and folders. | no | required | no | no |
 | `rudder library file get <path>` | Read one path-based Library file. | no | required | no | no |
 | `rudder library file put <path> --body-file <path>` | Create or update one path-based Library file. | yes | required | no | attached when available |