@rryando/arcs 3.2.3 → 3.2.5

package/opencode/arcs/prompts/arcs-orchestrate-caveman.txt

@@ -138,12 +138,23 @@ Discovery: `arcs --commands --json` (cache once per session). Batch op names are
 | Validate | `arcs validate <slug> --json` |
 | Task transition | `arcs task transition <slug> <taskId> <status> --planId=<id> --diagramNodeId=<node> --json` |
 | Batch writes | `arcs batch --file=ops.json --json` |
+| Update doc (inline) | `arcs project update-doc <slug> <doc> --content="..." --json` |
 | Create task | `arcs task create <slug> <title> --priority=medium --planId=<id> --dependsOn=id1,id2 --json` |
 | Create knowledge | `arcs knowledge create <slug> <title> --kind=<kind> --summary="..." --body="..." --source-files="src/foo.ts:anchor" --json` |
 | Create plan | `arcs plan create <slug> <title> --summary="..." --status=planned --json` |
 | Update plan meta | `arcs plan update-meta <slug> <planId> [--status=proposed\|planned\|in_progress\|done\|archived] --json` |
 | Role-targeted context | `arcs context <slug> --audience=<role> --lean --json` |
 
+**Batch op format** (flat structure — fields at top level, NOT nested under `params`):
+```json
+{"op":"task-create",     "slug":"<slug>","title":"...","priority":"medium","planId":"..."}
+{"op":"task-transition", "slug":"<slug>","taskId":"...","status":"done"}
+{"op":"knowledge-create","slug":"<slug>","title":"...","kind":"lesson","summary":"...","body":"..."}
+{"op":"doc-update",      "slug":"<slug>","doc":"overview","content":"..."}
+{"op":"plan-create",     "slug":"<slug>","title":"...","summary":"...","status":"planned"}
+```
+Valid ops: `task-create`, `task-transition`, `task-update`, `task-delete`, `knowledge-create`, `knowledge-update-meta`, `knowledge-update-body`, `knowledge-delete`, `plan-create`, `plan-update-meta`, `plan-delete`, `doc-update`
+
 ## Master Routing
 
 ```mermaid

package/opencode/arcs/prompts/arcs-orchestrate.txt

@@ -46,12 +46,23 @@ Discovery: `arcs --commands --json` (cache once per session). Batch op names are
 | Validate | `arcs validate <slug> --json` |
 | Task transition | `arcs task transition <slug> <taskId> <status> --planId=<id> --diagramNodeId=<node> --json` |
 | Batch writes | `arcs batch --file=ops.json --json` |
+| Update doc (inline) | `arcs project update-doc <slug> <doc> --content="..." --json` |
 | Create task | `arcs task create <slug> <title> --priority=medium --planId=<id> --dependsOn=id1,id2 --json` |
 | Create knowledge | `arcs knowledge create <slug> <title> --kind=<kind> --summary="..." --body="..." --source-files="src/foo.ts:anchor" --json` |
 | Create plan | `arcs plan create <slug> <title> --summary="..." --status=planned --json` |
 | Update plan meta | `arcs plan update-meta <slug> <planId> [--status=proposed\|planned\|in_progress\|done\|archived] --json` |
 | Role-targeted context | `arcs context <slug> --audience=<role> --lean --json` |
 
+**Batch op format** (flat structure — fields at top level, NOT nested under `params`):
+```json
+{"op":"task-create",     "slug":"<slug>","title":"...","priority":"medium","planId":"..."}
+{"op":"task-transition", "slug":"<slug>","taskId":"...","status":"done"}
+{"op":"knowledge-create","slug":"<slug>","title":"...","kind":"lesson","summary":"...","body":"..."}
+{"op":"doc-update",      "slug":"<slug>","doc":"overview","content":"..."}
+{"op":"plan-create",     "slug":"<slug>","title":"...","summary":"...","status":"planned"}
+```
+Valid ops: `task-create`, `task-transition`, `task-update`, `task-delete`, `knowledge-create`, `knowledge-update-meta`, `knowledge-update-body`, `knowledge-delete`, `plan-create`, `plan-update-meta`, `plan-delete`, `doc-update`
+
 ## Master Routing
 
 ```mermaid

package/opencode/arcs/skills/writing-plans/SKILL.md

@@ -163,7 +163,7 @@ arcs plan create <slug> --title="YYYY-MM-DD <feature> Implementation Plan" --sum
 
 ## Execution Handoff
 
-> "Plan complete and saved to arcs project plan `<planId>` in project `<slug>`. Ready to execute?"
+> "Plan complete and saved via `arcs plan get <slug> <planId>` in project `<slug>`. Ready to execute?"
 
 - **Subagents available** → REQUIRED: use `arcs:subagent-driven-development`
 - **No subagents** → use `arcs:executing-plans`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rryando/arcs",
-  "version": "3.2.3",
+  "version": "3.2.5",
   "description": "ARCS — DAG-based task orchestration for AI agents. Persistent workflow continuity via graph-structured context.",
   "type": "module",
   "main": "dist/index.js",
@@ -56,6 +56,7 @@
     "@types/node": "^22.15.3",
     "typescript": "^5.8.3",
     "vite": "^6.4.1",
-    "vitest": "^3.2.4"
+    "vitest": "^3.2.4",
+    "@types/bun": "latest"
   }
 }

package/skills/orchestrate.md

@@ -80,7 +80,7 @@ Discovery: `arcs --commands --json`
 
 ## Loop Tools
 
-- `arcs loop start <slug> --prompt="..." --max-iterations=50 --json` — self-referential dev loop
+- `arcs loop start <slug> --prompt="..." --session="<session-id>" --max-iterations=50 --json` — self-referential dev loop (--session is required; use a unique stable ID per agent session, e.g. a UUID or timestamp string)
 - `arcs loop cancel <slug> --json` — cancel active loop
 - `arcs loop status <slug> --json` — inspect loop state