@rudderhq/agent-runtime-codex-local 0.6.1 → 0.6.2-canary.0

package/package.json

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

package/skills/rudder-docs/evals/trigger-evals.json

@@ -28,7 +28,7 @@
     "should_trigger": true
   },
   {
-    "query": "Before hiring a Founding Engineer in Rudder, compare the installed Codex runtime configuration with existing agents and explain the correct role, title, reportsTo, SOUL.md, desiredSkills, and sourceIssueId fields.",
+    "query": "Before hiring a Founding Engineer in Rudder, compare the installed Codex runtime configuration with existing agents and explain the correct role, title, SOUL.md, desiredSkills, and sourceIssueId fields.",
     "should_trigger": true
   },
   {

package/skills/rudder-docs/references/agent-creation.md

@@ -71,8 +71,6 @@ defines its organizational responsibility and runnable configuration:
   `designer`, `pm`, `qa`, `devops`, `researcher`, or `general`.
 - `title` carries the specific job title. For example, use role `engineer` and
   title `Founding Engineer`, never a new `founding_engineer` role.
-- `reportsTo` identifies an in-organization manager and must preserve the
-  intended reporting line.
 - `capabilities` states the work this Agent owns and the boundaries it should
   not silently cross.
 - `agentRuntimeType`, `agentRuntimeConfig`, and `runtimeConfig` must follow the
@@ -147,7 +145,7 @@ written. Success requires the canonical hire operation to return:
 - `agent.id` for the created or pending Agent; and
 - `approval.id` when approval is required.
 
-Report the organization, Agent identity, role/title, reporting line, runtime,
+Report the organization, Agent identity, role/title, runtime,
 source issue, and direct versus approval branch without exposing secrets.
 If execution was not explicitly requested, report only the verified proposed
 configuration and the current command or capability that would govern it.

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

@@ -32,7 +32,7 @@ Internal/debug reference for the Rudder API.
 
 ### `GET /api/agents/me`
 
-Returns the authenticated agent plus `chainOfCommand` and access state.
+Returns the authenticated agent plus access state.
 
 Representative shape:
 
@@ -45,19 +45,11 @@ Representative shape:
   "title": "Senior Backend Engineer",
   "status": "running",
   "budgetMonthlyCents": 5000,
-  "spentMonthlyCents": 1200,
-  "chainOfCommand": [
-    {
-      "id": "mgr-1",
-      "name": "EngineeringLead",
-      "role": "manager",
-      "title": "VP Engineering"
-    }
-  ]
+  "spentMonthlyCents": 1200
 }
 ```
 
-Use `chainOfCommand` for escalation and the budget fields for spend awareness.
+Use explicit assignee/reviewer ownership and organization permissions for escalation, and the budget fields for spend awareness.
 
 ### `GET /api/agents/me/inbox-lite`
 
@@ -147,7 +139,6 @@ Use the incremental `after` form when you already know the thread.
 - `POST /api/orgs/:orgId/issues`
 - `GET /api/orgs/:orgId/agents`
 - `POST /api/orgs/:orgId/agent-hires`
-- `GET /api/orgs/:orgId/org`
 - `GET /api/orgs/:orgId/dashboard`
 - `GET /api/orgs/:orgId/projects`
 - `POST /api/orgs/:orgId/projects`

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

@@ -45,7 +45,7 @@ operating-practices guide for operating behavior:
 
 | MCP Tool | CLI Fallback | Description | Mutating | Org | Agent | Run ID |
 | --- | --- | --- | --- | --- | --- | --- |
-| `rudder_agent_me` | `rudder agent me` | Show the authenticated agent identity, budget, and chain of command. | no | no | no | no |
+| `rudder_agent_me` | `rudder agent me` | Show the authenticated agent identity and budget. | no | no | no | no |
 | `rudder_agent_inbox` | `rudder agent inbox` | List the compact assignee and reviewer work inbox for the authenticated agent. | no | no | no | no |
 | `rudder_agent_capabilities` | `rudder agent capabilities` | List the stable Rudder agent command contract. | no | no | no | no |
 | `rudder_agent_update` | `rudder agent update [agent-id] [--title <title>] [--description <text>]` | Update an agent's identity fields; defaults to the authenticated agent. | yes | no | no | attached when available |

package/skills/rudder-docs/references/operating-practices.md

@@ -122,8 +122,8 @@ report the status and required follow-up rather than bypassing it.
   creating top-level management work. When the organization has a mature label
   taxonomy, choose at least one suitable label after inspecting the available
   labels.
-- Never cancel cross-team work. Reassign upward with an explanation, and use
-  `chainOfCommand` for escalation.
+- Never cancel cross-team work. Reassign to an explicit owner or operator with
+  an explanation.
 - Above 80% spend, focus on critical work only and avoid expanding scope.
 - Use [Agent creation](agent-creation.md) for the canonical governed hiring
   workflow rather than assembling a raw Rudder API payload.