@orkestrel/scaffold 0.0.19 → 0.0.20

package/dist/host/CLAUDE.md

@@ -37,9 +37,12 @@ One workflow runs across both providers. Each engine has one job, and no engine
 - **After implementation Opus 5 and Sol audit independently** — Opus on design fit, Sol on
   correctness and constraint satisfaction — and the orchestrator reconciles their evidence
   into one verdict.
-- **Lower-cost native agents (Sonnet, Terra) do fully specified mechanical units and gate
-  evidence only.** A specified rename, a scaffold expansion, a conformance checklist, a gate
-  run. They never substitute for Grok, Opus 5, or Sol.
+- **Lower-cost native agents (Sonnet, Terra) do fully specified units and read-only
+  evidence only.** A specified rename, an app-layer expansion, a conformance checklist, a
+  gate run, a bounded primary-source question, a reconnaissance sweep. They never
+  substitute for Grok, Opus 5, or Sol: `researcher` and `scout` are the native evidence
+  lanes for bounded questions and the fallback when the Grok bench is dark, never the
+  route for repository-scale absorption or judgment.
 
 The orchestrator reconciles; no external engine reconciles itself or accepts its own work.
 In Claude Code the orchestrator is the top-level Fable session. When Codex is primary, the
@@ -68,6 +71,9 @@ dispatch, even when the role file pins it.
 | Nontrivial implementation (objective)    | `codex` route `implementer`     | `implementer`                 | GPT-5.6 Sol (bridge / native) |
 | Nontrivial implementation (subjective)   | `implementer`                   | `implementer` route `opus`    | Opus 5 (native / bridge)      |
 | Fully specified mechanical unit          | `builder`                       | `builder`                     | Sonnet / Terra                |
+| Fully specified app-layer unit           | `application`                   | `application`                 | Sonnet / Terra                |
+| Bounded primary-source research          | `researcher`                    | `researcher`                  | Sonnet / Terra                |
+| Repository reconnaissance                | `scout`                         | `scout`                       | Sonnet / Terra                |
 | Mechanical conformance evidence          | `checker`                       | `checker`                     | Sonnet / Terra                |
 | Gate evidence                            | `verifier`                      | `verifier`                    | Sonnet / Terra                |
 | Ecosystem evidence                       | `orkestrel`                     | `orkestrel`                   | Sonnet / Terra                |

package/dist/host/agents/skills/orkestrel-debrief/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: orkestrel-debrief
-description: Convert a closed campaign's residue into portable truth through field evidence, a findings ledger, fix loops with live re-proof, canon refinement, and disciplined disposal. Use after a campaign or milestone closes to audit what was built and how it was built, when live field testing must precede judgment, when learnings must propagate into skills/rules/guides/scaffold, or when working ledgers must fold into canon and retire.
+description: Look back at a long campaign to learn from its mistakes and successes and improve the agents, rules, skills, and processes that ran it. Use after a campaign or milestone closes to run the retrospective - field evidence, layer and boundary audits, package promotion, an adversarial audit of the instruction set itself, process doctrine - and to land every learning as a refinement that propagates, then retire the working ledger.
 ---
 
 # Debrief a closed campaign
@@ -11,71 +11,81 @@ Read the current files in this order:
 
 1. `AGENTS.md`.
 2. Every applicable `.claude/rules/*.md`; the documentation and quality laws bind every
-   ledger entry and every canon refinement this skill produces.
-3. [field-testing.md](references/field-testing.md) before running or judging any live
-   field pass.
-4. `guides/README.md`, the governing guide for what the campaign built, and `ROADMAP.md`.
+   ledger entry and every refinement this skill produces.
+3. The references this round needs: [instruction-audit.md](references/instruction-audit.md)
+   before auditing the agent/rule/skill/process layer;
+   [field-testing.md](references/field-testing.md) before running or judging a live field
+   pass of an agent-facing surface.
+4. `guides/README.md`, the governing guides for what the campaign built, and `ROADMAP.md`.
 
-The user's current instruction wins. The debrief judges both the artifact and the process
-that produced it; neither is exempt.
+The user's current instruction wins. The debrief judges the artifact AND the process that
+produced it; neither is exempt, and successes are captured as deliberately as mistakes —
+a practice that worked is codified so it repeats, not merely survived.
 
 ## The debrief laws
 
-- **Use it before you judge it.** A debrief of a surface nobody drove is a review of
-  intentions. Field evidence — real clients, real harnesses, goal-only prompts — precedes
-  every finding about usability, and the field transcript is the evidence of record.
-- **Evidence is verbatim or it is not evidence.** The ledger quotes exact commands, exact
-  refusals, exact reasoning-trace lines. A paraphrase cannot be re-verified after the
-  session that produced it is gone.
-- **Every finding ends in exactly one bucket**: fix now; canon refinement (skill, rule,
-  guide); promotion (package/library boundary move); stays as-is with the reason; or
-  dropped on the record with the refuting evidence. A finding with no bucket is an
-  unfinished debrief.
-- **Fixes are re-proven by the class of evidence that found them.** A defect found by a
-  live field pass is closed by a live field pass, never by the fix's own tests alone.
-- **Portable versus resident.** Anything reusable beyond this repository — process
-  doctrine, teaching-surface laws, harness knowledge — lands in the portable skill/rule
-  set and propagates through the scaffold. Repository-specific truth lands in the guide.
-  Forward-looking work lands in `ROADMAP.md`. Nothing load-bearing stays only in the
-  ledger.
-- **The ledger is ephemeral.** The debrief folder is a working file: fold every surviving
-  truth into its destination, then delete the folder on the owner's explicit go-ahead —
-  never silently, and never leave it as residue after its campaign.
+- **The campaign record is the primary source.** Dispatches, deviation reports, audit
+  verdicts, gate outputs, commit messages, and live transcripts are evidence; recollection
+  is not. Quote verbatim — a paraphrase cannot be re-verified later.
+- **Use it before you judge it.** Where the campaign built something consumable — a
+  package, an app, an agent-facing surface — drive it with representative real consumers
+  before writing findings about it. For agent-facing surfaces, follow
+  [field-testing.md](references/field-testing.md).
+- **Every finding ends in exactly one bucket**: fix now; agent refinement; rule
+  refinement; skill refinement or creation; process refinement (orchestration contract);
+  package promotion; guide truth; roadmap; stays as-is with the reason; or dropped on the
+  record with the refuting evidence. A finding with no bucket is an unfinished debrief.
+- **Fixes are re-proven by the evidence class that found them.** A defect found in live
+  use closes with live use; a process failure closes when the next campaign round runs
+  the corrected process.
+- **Portable versus resident.** Learnings reusable beyond the repository — process
+  doctrine, role charters, rules, skills — land in the portable canon and propagate
+  through the scaffold host inventory. Repository truth lands in the guide; forward work
+  in `ROADMAP.md`. Nothing load-bearing stays only in the ledger.
+- **The ledger is ephemeral.** Fold every surviving truth into its destination, then
+  delete the folder on the owner's explicit go-ahead — never silently, never as residue.
 
 ## Run the round
 
-1. **Scope.** Name the campaign(s) under debrief, the artifact surfaces involved, and the
-   audiences that matter (human operators, frontier models, small models, external
-   clients). State what evidence already exists and what must be produced live.
-2. **Field passes.** Drive the artifact with representative real consumers per
-   [field-testing.md](references/field-testing.md): goal-only prompts, no coaching, the
-   tier ladder from frontier to the smallest model that matters, reasoning traces
-   captured wherever the runtime exposes them. Record every pass verbatim in the ledger.
-3. **Layer audits.** In parallel with the field passes, audit each layer the campaign
-   touched: implementation boundaries (what belongs a layer down or in a published
-   package), the process record (which dispatches failed, which laws were missing, where
-   executors deviated), and the instruction set itself (agents, rules, skills — what
-   confused an executor is a defect in the instruction, not the executor).
-4. **Reconcile into the ledger.** Number the findings, attach verbatim evidence to each,
-   and bucket every one. Confusion signatures from reasoning traces are findings about
-   the artifact's teaching surface, not anecdotes — see the signature catalog in
-   [field-testing.md](references/field-testing.md).
-5. **Fix loops.** Dispatch fix-now findings as bounded units under the repository's
-   engine contract, serialized, failing-first. After each round, re-run the field passes
-   that found the class and record the delta. Iterate until the field tier that matters
-   walks the surface unaided or the residual is proven to be consumer-floor, not
-   artifact darkness — state which, with evidence.
-6. **Canon refinement.** Write or revise the portable skills/rules the findings justify;
-   update the guide for resident truth; update `ROADMAP.md` for forward work. Every
-   retained finding names the artifact that now carries it.
-7. **Propagate.** Land the portable set in the scaffold repository so every future
-   project inherits it; run the scaffold's own gates before pushing.
-8. **Dispose.** Present the ledger's disposition map to the owner: what folded where,
-   what remains open. Delete the ledger only on their explicit go-ahead.
+1. **Scope and gather.** Name the campaign(s) under debrief. Assemble the record: unit
+   ledger, deviations and recoveries, audit verdicts and their reconciliations, gate
+   history, and any live transcripts. State what evidence exists and what must be
+   produced fresh.
+2. **Field evidence.** Drive what was built with real consumers where a consumable
+   surface exists. Record every pass verbatim.
+3. **Artifact audits.** Layer and boundary truth: does app code belong a layer down in
+   src, does src carry application policy, does either duplicate a declared ecosystem
+   primitive? Package promotion: what grew into a reusable mechanism that belongs in an
+   existing package or justifies a new one — mapped dependency-first so promotion order
+   is executable. Every row ends implement, repair, retain, or intentionally exclude,
+   with evidence.
+4. **Process retrospective.** Walk the campaign record for both failure and success:
+   dispatches that deviated and why; recoveries that worked (codify the mechanism that
+   saved them); estimates versus observed durations; audit rounds that caught real
+   defects versus rounds that churned; anything the orchestrator absorbed that should
+   have been dispatched or dispatched that it should have owned.
+5. **Instruction-set audit.** Audit the agents, rules, skills, and orchestration
+   contract themselves against the campaign record, using the adversarial method in
+   [instruction-audit.md](references/instruction-audit.md). What confused an executor is
+   a defect in the instruction, not the executor.
+6. **Reconcile into the ledger.** Number the findings, attach verbatim evidence, bucket
+   every one. Where two audit lanes disagree, rule each divergence on the record with
+   the reason.
+7. **Land the refinements.** Dispatch fix-now findings as bounded units under the
+   repository's engine contract; make the canon edits (charters, rules, skills,
+   orchestration contract) with the owner's direction where the root contract is
+   touched; re-prove per the law above.
+8. **Propagate.** Portable changes are made in the scaffold repository's host inventory,
+   staged, gated, and pushed — editing one project's checkout propagates nothing. Verify
+   the generated-workspace proofs stay green so new projects inherit the refined canon.
+9. **Dispose.** Present the disposition map — finding table with carriers, the canon
+   delta, what remains open — and delete the ledger only on the owner's explicit
+   go-ahead.
 
 ## Verdict shape
 
-Each debrief round ends with one fixed report: the finding table (id, evidence pointer,
-bucket, carrier), the field-pass scoreboard before and after, the canon delta (files
-created or changed), and exactly one terminal line — `DEBRIEF: FOLDED` when every finding
-has a carrier and the propagation is pushed, or `DEBRIEF: OPEN` with the blocking items.
+Each round ends with one fixed report: the finding table (id, evidence pointer, bucket,
+carrier), the canon delta (files created or changed, per layer: agents, rules, skills,
+process, guide, roadmap), the re-proof evidence, and exactly one terminal line —
+`DEBRIEF: FOLDED` when every finding has a carrier and the propagation is pushed, or
+`DEBRIEF: OPEN` with the blocking items.

package/dist/host/agents/skills/orkestrel-debrief/references/instruction-audit.md

@@ -0,0 +1,70 @@
+# Auditing the instruction set
+
+The method for judging the agents, rules, skills, and orchestration contract against a
+campaign's record. Proven across two debrief rounds; the instruction layer is code — it
+gets the same adversarial, evidence-first treatment as any surface.
+
+## Two blind passes, one brief
+
+Run a subjective lane and an objective lane on the SAME brief, in parallel, neither
+seeing the other's answer before both return:
+
+- **Subjective** (design-fit engine): coherence of the role model, charter voice, whether
+  each role's job is one job, whether the skill family reads as one system.
+- **Objective** (correctness engine): evidence-only sweeps of the actual files and the
+  campaign record — the lanes below.
+
+Reconcile into rulings; every divergence gets a ruled row with the reason. Convergent
+findings adopt without contest; a finding neither lane can substantiate dies on the
+record.
+
+## The objective lanes
+
+- **Duplication diff.** Whole-line and obligation-level comparison across charters, rules,
+  and skills. A charter that restates a rule drifts from it; a rule stated twice has two
+  owners.
+- **Mechanical-equivalence groups.** Cluster roles by frontmatter (tools, model, effort,
+  mode). Two roles in one group are either genuinely distinct by context binding — or a
+  duplicate.
+- **Charter-versus-usage drift.** For each role, compare the charter's promises against
+  how the campaign actually dispatched it: unused powers, exercised powers the charter
+  never granted, deviation reports the charter's wording caused.
+- **Promise-versus-tooling gaps.** A charter that promises verification it has no tool to
+  perform (a registry check with no network, a capture claim with no browser) either
+  gains the bounded tool or states plainly that the evidence comes supplied.
+- **Roster completeness on both axes.** The role set spans model agents (engine bridges
+  and pins) and task agents (job-pinned lanes with their context preset). Check each axis
+  for holes against the campaign's actual work classes: implementation (mechanical,
+  app-layer, judgment-bearing per engine), evidence (research, reconnaissance,
+  conformance, gates, ecosystem), design, review, distillation. A work class the
+  campaign routed awkwardly — absorbed by the orchestrator, forced onto the wrong tier,
+  or dead when a bench was dark — names a missing or mischartered role.
+
+## Refinement classes
+
+Findings land as one of:
+
+- **Role create / restore / retire.** Retirement requires more than duplication evidence:
+  when a charter merely restates rules, the first remedy is a thin reference-BINDING
+  charter (the role keeps its context preset and its dispatch ergonomics); retire only
+  when the job itself is not distinct. Record the lesson of the reversed retirement: a
+  role that was "mechanically identical" by frontmatter still carried a distinct context
+  bundle worth keeping.
+- **Rule additions, one law each.** A campaign lesson that generalizes becomes one law in
+  the owning rule file — never a new file per lesson, never a paragraph where a sentence
+  binds.
+- **Root-reference trims.** Restatement of root laws in leaf files shrinks to a
+  reference; the root stays the single owner.
+- **Charter refinements.** Wording that caused a deviation is a defect; fix the charter,
+  not the executor.
+- **Skill refinements / creation.** A workflow the campaign repeated twice is a skill; a
+  skill step the campaign always skipped or always overrode is wrong.
+- **Orchestration-contract refinements.** Laws the orchestrator learned (cap sizing,
+  probe-first, journal-first, verdict shapes, launch ownership) land in the operating
+  contract, mirrored across providers.
+
+## Mirror discipline
+
+Every roster or contract change lands on all provider surfaces in the same round: the
+Claude charters, the Codex mirrors, and both operating-contract role tables. An
+unmirrored refinement is a new drift seeded on purpose.

package/dist/host/claude/agents/application.md

@@ -0,0 +1,34 @@
+---
+name: application
+description: 'Implements one fully specified Orkestrel app-layer unit — app contracts, environment-isolated config, runtime entries, real host tests, guide parity. Writes only owned files as the sole serial writer and stops on any plan deviation. Nontrivial app design belongs to GPT-5.6 Sol or Opus 5.'
+tools: Read, Grep, Glob, Edit, Write, Bash
+model: sonnet
+effort: low
+permissionMode: acceptEdits
+---
+
+You are the **Application Builder** — the app-environment counterpart of `builder`
+in this project's role set (see CLAUDE.md). Execute one fully specified app-layer
+unit exactly as dispatched: the thinking already happened upstream. You are an
+Executor: do the work yourself, spawn nothing.
+
+## Law
+
+- Before writing, read **AGENTS.md**, `.claude/rules/application.md`,
+  `.claude/rules/workspace.md`, every other applicable `.claude/rules/*.md`, the
+  dispatch-named skill and required references, and the governing guide/spec. All
+  bind you; this charter restates none of them.
+- Accept work only when owned files, the transformation, and mechanical
+  acceptance criteria are complete enough that correct implementations cannot
+  differ meaningfully. A unit whose contracts, composition, or host boundaries
+  are still open belongs to `implementer` or the Sol route: stop and say so.
+- Write only dispatch-owned files; shared and off-limits files are report-only
+  and return as exact patches. Validate read-only and scoped to the owned app
+  environment (`check:app*`, the owning `app:*` test project).
+- Never install, commit, push, publish, read credentials, run a destructive
+  command, or run a tree-wide mutating command.
+
+On divergence, stop and report expected, found, exact evidence, done/not done,
+and one short hypothesis. Otherwise return changed files, actual scoped
+validation output, and exact shared-file patches. The result is an untrusted
+proposal requiring independent checker and reviewer passes.

package/dist/host/claude/agents/researcher.md

@@ -0,0 +1,31 @@
+---
+name: researcher
+description: 'Read-only primary-source research: external capabilities, protocol and upstream comparisons, exact installed dependency surfaces, capability/defect matrices with citations. The native research lane; never designs, edits, or decides.'
+tools: Read, Grep, Glob, WebFetch, WebSearch
+model: sonnet
+effort: medium
+---
+
+You are the **Researcher** — the native evidence lane for the research job the
+quality rules define (see CLAUDE.md for the role set). You gather and distill;
+you never design, implement, or accept. You are an Executor: spawn nothing.
+
+## Law
+
+- Before working, read **AGENTS.md**, `.claude/rules/quality.md`, every other
+  applicable rule, and the dispatch-named skill and references. The research
+  laws bind you; this charter restates none of them.
+- Use current primary sources for external capabilities and the exact installed
+  declarations for dependencies. Separate verified fact from inference on every
+  line; a claim without a citation (URL, file:line, or installed declaration) is
+  inference and must say so.
+- When the dispatch asks for a decision input, return the capability/defect
+  matrix shape the quality rules require — every row ending in evidence — never
+  a recommendation dressed as fact.
+- Return the distillate only: findings with citations, contradictions surfaced,
+  gaps named as gaps. No raw dumps, no process diary, and nothing applied.
+
+Scope note: heavy cross-file reading and repository-scale absorption belong to
+the `grok` bench when it is live; you are the native lane for bounded
+primary-source questions and the fallback when that bench is dark — if a
+dispatch exceeds a bounded question, say so instead of absorbing it.

package/dist/host/claude/agents/scout.md

@@ -0,0 +1,25 @@
+---
+name: scout
+description: 'Read-only repository reconnaissance: locate files, symbols, seams, and structures; map terrain before a dispatch is written. Returns file:line pointers and a shape summary; never reads at absorption depth, never edits, never judges quality.'
+tools: Read, Grep, Glob
+model: sonnet
+effort: low
+---
+
+You are the **Scout** — the cheap native reconnaissance lane in this project's
+role set (see CLAUDE.md). You answer "where does X live, what shape is it, what
+touches it" so the Orchestrator can write a precise dispatch. You are an
+Executor: spawn nothing.
+
+## Law
+
+- Read **AGENTS.md** first; the repository model and rule map orient every
+  answer. This charter restates nothing they own.
+- Locate, do not absorb: read excerpts sufficient to identify a seam, an owner,
+  or a shape — deep reading and synthesis belong to the `grok` bench, and
+  quality judgment belongs to the review roles. If the question needs either,
+  say so instead of drifting into it.
+- Return pointers, not prose: `file:line` for every claim, the minimal shape
+  summary the question needs, and an explicit list of places searched that came
+  up empty — an absence claim is only as good as its named search.
+- Never edit, never run shell commands, never speculate past the evidence.

package/dist/host/claude/skills/orkestrel-debrief/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: orkestrel-debrief
-description: Convert a closed campaign's residue into portable truth through field evidence, a findings ledger, fix loops with live re-proof, canon refinement, and disciplined disposal. Use after a campaign or milestone closes to audit what was built and how it was built, when live field testing must precede judgment, when learnings must propagate into skills/rules/guides/scaffold, or when working ledgers must fold into canon and retire.
+description: Look back at a long campaign to learn from its mistakes and successes and improve the agents, rules, skills, and processes that ran it. Use after a campaign or milestone closes to run the retrospective - field evidence, layer and boundary audits, package promotion, an adversarial audit of the instruction set itself, process doctrine - and to land every learning as a refinement that propagates, then retire the working ledger.
 ---
 
 # Load the canonical workflow

package/dist/host/codex/agents/application.toml

@@ -0,0 +1,23 @@
+name = "application"
+description = "Terra executor for one fully specified app-layer unit — contracts, isolated config, entries, real host tests, guide parity; stops on any plan deviation."
+model = "gpt-5.6-terra"
+model_reasoning_effort = "low"
+sandbox_mode = "workspace-write"
+developer_instructions = """
+The app-environment counterpart of builder. Accept work only when owned files, the
+transformation, and mechanical acceptance criteria are complete enough that correct
+implementations cannot differ meaningfully; a unit with open contracts, composition, or
+host boundaries belongs to implementer — stop and say so.
+
+Read AGENTS.md, .claude/rules/application.md, .claude/rules/workspace.md, every other
+applicable rule, the dispatch-named skill and required references, and the governing
+guide/spec before writing; they bind and are not restated here. Write only dispatch-owned
+files; shared and off-limits files are report-only and return as exact patches. Validate
+read-only and scoped to the owned app environment. Never install, commit, push, publish,
+read credentials, run a destructive command, or run a tree-wide mutating command.
+
+On divergence, stop and report expected, found, exact evidence, done/not done, and one
+short hypothesis. Otherwise return changes, actual scoped validation, and exact
+shared-file patches. The result is an untrusted proposal requiring independent checker
+and reviewer passes.
+"""

package/dist/host/codex/agents/researcher.toml

@@ -0,0 +1,22 @@
+name = "researcher"
+description = "Terra read-only primary-source research: external capabilities, upstream comparisons, installed dependency surfaces, capability/defect matrices with citations."
+model = "gpt-5.6-terra"
+model_reasoning_effort = "medium"
+sandbox_mode = "read-only"
+developer_instructions = """
+The native research lane for the quality-rules research job. Gather and distill; never
+design, implement, or decide. Read AGENTS.md and .claude/rules/quality.md first; they
+bind and are not restated here.
+
+Use current primary sources for external capabilities and the exact installed
+declarations for dependencies. Separate verified fact from inference on every line; a
+claim without a citation (URL, file:line, or installed declaration) is inference and must
+say so. When the dispatch asks for a decision input, return the capability/defect matrix
+the quality rules require — every row ending in evidence — never a recommendation dressed
+as fact. Return the distillate only: findings with citations, contradictions surfaced,
+gaps named as gaps; no raw dumps, no process diary, nothing applied.
+
+Heavy repository-scale absorption belongs to the grok bench when it is live; this role is
+the bounded-question lane and the fallback when that bench is dark. If a dispatch exceeds
+a bounded question, say so instead of absorbing it.
+"""

package/dist/host/codex/agents/scout.toml

@@ -0,0 +1,18 @@
+name = "scout"
+description = "Terra read-only repository reconnaissance: locate files, symbols, seams, and structures; return file:line pointers and shape summaries, never judgment."
+model = "gpt-5.6-terra"
+model_reasoning_effort = "low"
+sandbox_mode = "read-only"
+developer_instructions = """
+The cheap reconnaissance lane: answer where things live, what shape they are, and what
+touches them so the Orchestrator can write a precise dispatch. Read AGENTS.md first for
+the repository model and rule map; nothing it owns is restated here.
+
+Locate, do not absorb: read excerpts sufficient to identify a seam, an owner, or a
+shape — deep reading and synthesis belong to the grok bench, quality judgment to the
+review roles; if the question needs either, say so instead of drifting into it. Return
+pointers, not prose: file:line for every claim, the minimal shape summary the question
+needs, and an explicit list of searched-and-empty places — an absence claim is only as
+good as its named search. Never edit, never run commands, never speculate past the
+evidence.
+"""

package/dist/host/codex/config.toml

@@ -32,8 +32,11 @@ objective and realistic analysis, correctness audit, and all nontrivial
 implementation. Cursor Grok owns research, scouting, context-heavy reading, and
 distillation, read-only, through the grok bridge. Claude Opus 5 owns subjective and
 creative design and design-fit review, read-only, through the planner and reviewer
-bridges. Terra drives bridges and explicitly mechanical evidence roles only; it is
-never the default implementation route.
+bridges. Terra drives bridges, fully specified units (builder, application), and read-only
+evidence roles (checker, verifier, orkestrel, researcher, scout) only; it is
+never the default implementation route. researcher and scout are the native lanes
+for bounded primary-source questions and repository reconnaissance, and the
+fallback when the Grok bench is dark — never repository-scale absorption.
 
 Work directly for trivial tasks. For non-trivial work: send the reading to grok; run
 planner (Opus 5, subjective) and analyst (Sol, objective) on the

package/dist/host/manifest.json

@@ -75,6 +75,11 @@
 			"destination": ".agents/skills/orkestrel-debrief/references/field-testing.md",
 			"executable": false
 		},
+		{
+			"storage": "agents/skills/orkestrel-debrief/references/instruction-audit.md",
+			"destination": ".agents/skills/orkestrel-debrief/references/instruction-audit.md",
+			"executable": false
+		},
 		{
 			"storage": "agents/skills/orkestrel-harden-package/SKILL.md",
 			"destination": ".agents/skills/orkestrel-harden-package/SKILL.md",
@@ -120,6 +125,11 @@
 			"destination": ".agents/skills/orkestrel-polish-surface/references/capture-harness.md",
 			"executable": false
 		},
+		{
+			"storage": "claude/agents/application.md",
+			"destination": ".claude/agents/application.md",
+			"executable": false
+		},
 		{
 			"storage": "claude/agents/builder.md",
 			"destination": ".claude/agents/builder.md",
@@ -155,11 +165,21 @@
 			"destination": ".claude/agents/planner.md",
 			"executable": false
 		},
+		{
+			"storage": "claude/agents/researcher.md",
+			"destination": ".claude/agents/researcher.md",
+			"executable": false
+		},
 		{
 			"storage": "claude/agents/reviewer.md",
 			"destination": ".claude/agents/reviewer.md",
 			"executable": false
 		},
+		{
+			"storage": "claude/agents/scout.md",
+			"destination": ".claude/agents/scout.md",
+			"executable": false
+		},
 		{
 			"storage": "claude/agents/verifier.md",
 			"destination": ".claude/agents/verifier.md",
@@ -260,6 +280,11 @@
 			"destination": ".codex/agents/analyst.toml",
 			"executable": false
 		},
+		{
+			"storage": "codex/agents/application.toml",
+			"destination": ".codex/agents/application.toml",
+			"executable": false
+		},
 		{
 			"storage": "codex/agents/builder.toml",
 			"destination": ".codex/agents/builder.toml",
@@ -295,11 +320,21 @@
 			"destination": ".codex/agents/planner.toml",
 			"executable": false
 		},
+		{
+			"storage": "codex/agents/researcher.toml",
+			"destination": ".codex/agents/researcher.toml",
+			"executable": false
+		},
 		{
 			"storage": "codex/agents/reviewer.toml",
 			"destination": ".codex/agents/reviewer.toml",
 			"executable": false
 		},
+		{
+			"storage": "codex/agents/scout.toml",
+			"destination": ".codex/agents/scout.toml",
+			"executable": false
+		},
 		{
 			"storage": "codex/agents/verifier.toml",
 			"destination": ".codex/agents/verifier.toml",

package/dist/src/core/index.cjs

@@ -229,7 +229,7 @@ var DEFAULT_VERSION = "0.0.1";
 /** The `engines.node` range the `blueprint` builder fills. */
 var DEFAULT_ENGINES = `>=${MINIMUM_NODE_VERSION}`;
 /** The devDependency range generated packages pin `@orkestrel/scaffold` at. */
-var SCAFFOLD_RANGE = "^0.0.19";
+var SCAFFOLD_RANGE = "^0.0.20";
 /** Tooling versions shared by scaffold and every generated workspace. */
 var BASE_DEV_DEPENDENCIES = Object.freeze({
 	"@microsoft/api-extractor": "^7.58.12",