revert: undo parallel owner-agent brief refactor (dd249ed, bf0c4d1)

Superseded by the package/extension owner-agent briefs iterated with the user.
Reverts only the 3 markdown files (.dispatch/extension-agent.md, .dispatch/package-agent.md,
ORCHESTRATOR.md); no code was involved.

1 files changed, 36 insertions, 40 deletions

diff --git a/ORCHESTRATOR.md b/ORCHESTRATOR.md
index 7ddeba9..ae0e66f 100644
--- a/ORCHESTRATOR.md
+++ b/ORCHESTRATOR.md
@@ -73,34 +73,17 @@ building.
 
 **Canonical invocation** (inline the prompt — do NOT use `-f`, see gotcha;
 ALWAYS redirect output to a file — do NOT let it stream to your terminal):
-
-The prompt is assembled from **standardized briefs** (`.dispatch/`) + the **TASK block** you
-write. The briefs define who the agent is, guardrails, ownership, visibility, coupling,
-engineering standard, verification, and report format — you never restate those. You only write
-the TASK (the job + contracts + test cases).
-
-**Loading model:**
-- **Package summon:** `package-agent.md` + scoped `rules/*` + TASK
-- **Extension summon:** `package-agent.md` + `extension-agent.md` + scoped `rules/*` + TASK
-
 ```bash
 cd /home/tradam/projects/dispatch/arch-rewrite && \
 opencode run --dir /home/tradam/projects/dispatch/arch-rewrite \
   -m opencode-go/mimo-v2.5-pro \
-  "$(cat \
-    .dispatch/package-agent.md \
-    .dispatch/extension-agent.md \
-    .dispatch/rules/<scoped-rules...>.md \
-  )
-
-## TASK
-<your task block here — see §3 for what goes in it>" \
+  "$(cat prompts/<unit>.md)
+
+---
+Follow the above exactly. You own ONLY <files>. When done, write reports/<unit>.md." \
   > reports/<unit>.run.log 2>&1
 ```
 
-For a **non-extension** package, omit `extension-agent.md`. The agent never reads files —
-everything it needs is inlined above.
-
 **MANDATORY — capture output to a file, never display it.** The agent's streamed
 output is enormous and will overwhelm and CRASH this harness if it lands in your
 terminal. ALWAYS redirect the summon's stdout+stderr to a log file (e.g.
@@ -127,30 +110,43 @@ log into context as a hard failure.
 
 ---
 
-## 3. The TASK block (the only thing the orchestrator writes per summon)
-
-The prompt is assembled from standardized briefs + rules (§2). You then **append a TASK
-message** telling the agent what to build. Keep it scoped (P6): don't restate what the briefs
-already say; do state the project-specific, non-inferable rules. The agent gets the WHAT — it
-decides the HOW and the files.
-
-**The TASK names:**
-- The package (`packages/<name>/`) and whether it's an extension.
-- The job + algorithm, naming the specific contract types/handles involved.
-- The specific contract file(s) to read (e.g. `packages/kernel/src/contracts/<x>.ts`) plus any
-  sibling public surfaces.
-- The required test cases (named).
-- Verification instructions (always the isolated-scoped commands; the orchestrator runs the
-  full-graph verify itself).
-
-**`.dispatch/rules/` scoping map** — cat in ONLY the rows matching the unit
-(per §0 "scoped rules beat general rules"); do NOT dump every rule on every agent:
+## 3. Prompt recipe (what every `prompts/<unit>.md` must contain)
+
+Write self-contained prompts. Structure:
+1. **Role:** "You are the owner-agent for <unit>."
+2. **Read first (ordered):** `AGENTS.md`, the **scoped `.dispatch/rules/`** for this
+   unit's layer (the scoping map is below the recipe), `GLOSSARY.md`, the relevant
+   `notes/restructure-plan.md` §-sections, and **the exact contract files under
+   `packages/kernel/src/contracts/` it builds against**.
+3. **Ownership (strict):** the EXACT files it may create/edit, and an explicit
+   "do not touch anything else; if you need a change elsewhere, write a change-
+   request in your report — do NOT edit it."
+   - **Visibility (state it in EVERY prompt):** "Read ONLY the surfaces
+     (contracts/hooks/manifests/public signatures) of OTHER units; do NOT read
+     their implementation files. You MAY read the implementation files of YOUR
+     assigned unit only." (Mirrors §6 — keeps the agent's context clean too.)
+4. **The job + algorithm:** precise, with the contract types named.
+5. **Engineering constraints:** pure-core/inject-effects (P2), no ambient state
+   (P3), no internal mocks (the test rule), strict-mode TS, typed handles for any
+   cross-extension coupling (no string keys).
+6. **Tests REQUIRED:** name the cases. Pure units → fake inputs, ZERO internal
+   mocks. Shell units → a few integration tests, no sibling mocks.
+7. **Verify before finishing:** `bun run typecheck`, `bun run test`,
+   `bun run check` — all clean.
+8. **Report:** "write `reports/<unit>.md` with: files created, public surface,
+   full command output, decisions, and explicit change-requests for other units."
+
+Keep the prompt scoped (P6): don't restate what a frontier model knows; do state
+the project-specific, non-inferable rules.
+
+**`.dispatch/rules/` scoping map** — include ONLY the rows matching the unit (per §0
+"scoped rules beat general rules"); do NOT dump every rule on every agent:
 - **Every agent:** `one-owner.md`, `isolation-over-dry.md`.
 - **Kernel unit:** `kernel-purity.md` + `pure-core.md` + `no-internal-mocks.md`.
 - **Pure-core unit:** `pure-core.md` + `no-internal-mocks.md`.
 - **Any extension coupling via hooks/services:** `typed-handles.md`.
 - **Any extension that emits logs/spans (≈ all of them):** `extension-logging.md`
-  *(pending — authored with the observability substrate; see
+  *(pending — authored with the observability substrate, see
   `notes/observability-design.md` §9; keystone: each extension self-redacts its OWN
   secrets in its OWN code — NO shared redaction helper).*