@rryando/arcs 3.2.6 → 3.3.0

package/opencode/arcs/prompts/code-reviewer.txt

@@ -53,3 +53,23 @@ Before reading code, understand context:
 2. `arcs git-log <slug> --json` — understand commit intent
 3. `arcs task get <slug> <taskId> --json` — read the task spec being implemented
 4. Then review code against spec + conventions
+
+## Output Format
+
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+\`\`\`
+VERDICT: <approve | request-changes | comment-only>
+
+FINDINGS:
+- [CRITICAL] <file:line> — <issue>
+- [HIGH] <file:line> — <issue>
+- [MEDIUM] <file:line> — <issue>
+- [LOW] <file:line> — <issue>
+
+TASKS: <none | suggested follow-up tasks for orchestrator>
+
+YAGNI: <none | speculative code identified with file:line>
+\`\`\`
+
+No prose narrative. No "Overall this looks..." — go straight to VERDICT.

package/opencode/arcs/prompts/docs-researcher.txt

@@ -52,3 +52,23 @@ When creating entries, select the correct kind:
 | `module` | Module-level descriptions (from graphify) | Individual files |
 
 Always run `arcs knowledge list <slug> --json` before creating — check for existing entries to update rather than duplicate.
+
+## Output Format
+
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+\`\`\`
+RESEARCH: <topic summary — one line>
+
+FINDINGS:
+- <finding with source citation>
+
+EXISTING_DAG: <relevant entries already in DAG, or "none found">
+
+PROPOSED_ENTRIES:
+- kind:<kind> title:"<title>" summary:"<summary>"
+
+GAPS: <none | what couldn't be answered and why>
+\`\`\`
+
+No prose narrative. No "I researched..." — go straight to RESEARCH.

package/opencode/arcs/prompts/graph-explorer.txt

@@ -107,8 +107,18 @@ All commands support `--json` for machine-readable output. Reads return `{ok, da
 
 ## Output Format
 
-Return a structured answer:
-1. **Answer** — direct response to the question
-2. **Evidence** — DAG entry IDs or file:line citations
-3. **Fallback used** — if file-system tools were needed, state why the DAG was insufficient
-4. **Proposed captures** — any `arcs knowledge create` commands for durable findings
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+```
+ANSWER: <direct response — facts only, no filler>
+
+EVIDENCE:
+- <DAG entry ID or file:line citation>
+- <DAG entry ID or file:line citation>
+
+FALLBACK: <none | reason DAG was insufficient>
+
+CAPTURES: <none | proposed arcs knowledge create commands>
+```
+
+Omit FALLBACK/CAPTURES if none. No prose preamble. No "I found that..." — go straight to ANSWER.

package/opencode/arcs/prompts/oncall-ops.txt

@@ -52,3 +52,26 @@ When investigating a bug, failure, or production incident:
 6. `arcs knowledge create <slug> "<resolution method>" --kind=lesson --summary="..." --json` — capture the fix
 
 **DAG is context-reference only during active incidents.** Don't waste investigation time updating task status — do that after resolution.
+
+## Output Format
+
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+\`\`\`
+STATUS: <investigating | root-cause-found | resolved | blocked>
+
+ROOT_CAUSE: <one-line description or "pending">
+
+EVIDENCE:
+- <file:line, log output, or command result>
+
+FIX:
+- <what was done or what needs to be done>
+
+VERIFY:
+- <command ran>: <pass/fail>
+
+CAPTURES: <arcs knowledge create commands for gotcha/lesson>
+\`\`\`
+
+No prose narrative. No "After investigating..." — go straight to STATUS.

package/opencode/arcs/prompts/qa-analyst.txt

@@ -52,3 +52,25 @@ You are invoked BEFORE a feature lands — not after. Your job is to find proble
 5. `arcs search <slug> "<feature keywords>" --lean --json` — find all related context
 6. Cross-module grep: `rg "<symbol>" --type ts` — trace usage across boundaries
 7. Report: severity-grouped findings with file:line evidence
+
+## Output Format
+
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+\`\`\`
+AUDIT: <what was audited — scope in one line>
+
+FINDINGS:
+- [CRITICAL] <file:line> — <issue>
+- [HIGH] <file:line> — <issue>
+- [MEDIUM] <file:line> — <issue>
+
+CONVENTIONS:
+- <compliant | violations with file:line>
+
+TASKS: <none | suggested tasks for orchestrator to create>
+
+KNOWLEDGE: <none | proposed arcs knowledge create for patterns found>
+\`\`\`
+
+No prose narrative. No "I audited..." — go straight to AUDIT.

package/opencode/arcs/prompts/software-engineer.txt

@@ -33,16 +33,22 @@ MANDATORY EXIT GATE: Before claiming any work is complete, you MUST run verifica
 
 All commands support `--json` for machine-readable output. Reads return `{ok, data}`; failures return `{ok:false, code, message, hint?}`. **Routing:** success → stdout, errors → stderr — always capture both with `2>&1`.
 
-## Diagram-First Execution
-
-When working from a plan with a `.diagram.mmd` file:
-1. Run `arcs diagram ready <slug> <planId>` to find executable tasks (nodes whose dependencies are all `:::done`)
-2. Read per-node metadata (`%% node:`, `%% skill:`, `%% scope:`, `%% acceptance:`, `%% verify:`) for task context — this provides full dispatch context without loading plan prose
-3. After completing a task, report status in your final summary — the orchestrator handles diagram updates via:
-   ```bash
-   arcs task transition <slug> <taskId> done --planId=<planId> --diagramNodeId=T001 --json
-   ```
-   Both `--planId` and `--diagramNodeId` are required for the atomic task+diagram update.
-4. NEVER edit `.mmd` files directly — the orchestrator owns all diagram updates
-5. If node metadata is incomplete (missing `scope`, `acceptance`, or `verify`), fall back to reading the plan body for that specific task's details
-6. If you discover a scope change (task added, removed, or dependency changed), report it in your final summary — the orchestrator handles diagram regeneration
+## Output Format
+
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+\`\`\`
+STATUS: <done | blocked | partial>
+
+CHANGES:
+- <file:path> — <what changed, one line>
+
+VERIFY:
+- <command ran>: <pass/fail>
+
+SCOPE_CHANGE: <none | tasks added/removed/deps changed — orchestrator handles diagram>
+
+KNOWLEDGE: <none | reusable pattern/gotcha discovered — propose arcs knowledge create>
+\`\`\`
+
+No prose narrative. No "I implemented..." — go straight to STATUS.

package/opencode/arcs/prompts/system-architect.txt

@@ -51,6 +51,27 @@ When dispatched for structural design or migration planning:
 
 Your scope is project TOPOLOGY — how projects relate, where boundaries should be, what migrates where. Single-project deep analysis belongs to tech-architect.
 
+## Output Format
+
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+\`\`\`
+DELIVERABLE: <plan | design | knowledge entry | migration sequence>
+
+DECISIONS:
+- <decision with rationale, one line each>
+
+BOUNDARIES:
+- <module/project boundary defined or changed>
+
+RISKS:
+- <risk with severity and mitigation>
+
+ARTIFACTS: <arcs commands executed or proposed>
+\`\`\`
+
+No prose narrative. No "After analyzing..." — go straight to DELIVERABLE.
+
 ## Diagrams as Execution Maps
 
 ARCS plan diagrams (`.diagram.mmd` files) serve dual purposes:

package/opencode/arcs/prompts/tech-architect.txt

@@ -52,3 +52,24 @@ When dispatched for structural analysis:
 7. `arcs knowledge create <slug> "<finding>" --kind=architecture --summary="..." --json` — record findings
 
 Output: severity-ranked findings with evidence (file paths, metrics, dependency chains).
+
+## Output Format
+
+Your output is consumed by the orchestrator (an LLM), not a human. Be structured and terse.
+
+\`\`\`
+ANALYSIS: <one-line summary of what was analyzed>
+
+FINDINGS:
+- [CRITICAL|HIGH|MEDIUM] <finding> — evidence: <file:line or metric>
+
+RECOMMENDATIONS:
+- <action with rationale, one line each>
+
+RISKS:
+- <risk if recommendation is NOT followed>
+
+ARTIFACTS: <arcs commands executed or proposed>
+\`\`\`
+
+No prose narrative. No "I examined..." — go straight to ANALYSIS.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rryando/arcs",
-  "version": "3.2.6",
+  "version": "3.3.0",
   "description": "ARCS — DAG-based task orchestration for AI agents. Persistent workflow continuity via graph-structured context.",
   "type": "module",
   "main": "dist/index.js",

package/scripts/deploy-claudecode-bundle.mjs

@@ -67,6 +67,33 @@ const destination = scope === "project" ? projectRoot : configRoot;
 const DEFAULT_AGENT = "arcs-orchestrate";
 const SKILL_PREFIX = "arcs-";
 
+// ---------------------------------------------------------------------------
+// Model tier configuration
+// ---------------------------------------------------------------------------
+// Env vars: DEPLOY_MODEL_HEAVY, DEPLOY_MODEL_STANDARD, DEPLOY_MODEL_LIGHT
+// Each defaults to "inherit" if unset.
+const tierModels = {
+  heavy: process.env.DEPLOY_MODEL_HEAVY || "inherit",
+  standard: process.env.DEPLOY_MODEL_STANDARD || "inherit",
+  light: process.env.DEPLOY_MODEL_LIGHT || "inherit",
+};
+
+/** Maps each agent stem to a tier. Falls back to "standard". */
+const agentTierMap = {
+  "software-engineer": "heavy",
+  "docs-researcher": "heavy",
+  "arcs-docs": "heavy",
+  "oncall-ops": "heavy",
+  "system-architect": "heavy",
+  general: "heavy",
+  "arcs-orchestrate": "standard",
+  "arcs-orchestrate-caveman": "standard",
+  "devil-advocate": "standard",
+  "code-reviewer": "light",
+  "tech-architect": "light",
+  "qa-analyst": "light",
+};
+
 const agentMetadata = {
   "software-engineer": {
     name: "Software Engineer",
@@ -191,6 +218,9 @@ function buildAgentSources() {
       model: "inherit",
     };
 
+    const tier = agentTierMap[stem] || "standard";
+    const model = tierModels[tier];
+
     const toolsArray = meta.tools.split(",").map((t) => t.trim());
     const toolsYaml = `[${toolsArray.map((t) => `"${t}"`).join(", ")}]`;
 
@@ -198,7 +228,7 @@ function buildAgentSources() {
       "---",
       `name: ${meta.name}`,
       `description: ${meta.description}`,
-      `model: ${meta.model}`,
+      `model: ${model}`,
       `tools: ${toolsYaml}`,
       "---",
       "",
@@ -396,6 +426,7 @@ function main() {
     dryRun,
     source: bundleRoot,
     destination,
+    modelConfig: tierModels,
     filesAdded,
     filesChanged,
     filesRemoved,