fix: remove placeholder from skill files — orchestrator appends TASK as a separate message

3 files changed, 14 insertions, 30 deletions

diff --git a/.dispatch/extension-agent.md b/.dispatch/extension-agent.md
index 3c80b12..ec7c7cb 100644
--- a/.dispatch/extension-agent.md
+++ b/.dispatch/extension-agent.md
@@ -1,7 +1,7 @@
 # Extension Owner-Agent — Extension Rules (additive)
 
 > The package-agent brief (stated immediately above) applies fully. This file adds only the
-> rules unique to extensions. Your **TASK** follows this section.
+> rules unique to extensions.
 
 ## You're building an extension
 An extension is a package that plugs into the kernel host via a **manifest** + an
diff --git a/.dispatch/package-agent.md b/.dispatch/package-agent.md
index 31bfa55..7df6d91 100644
--- a/.dispatch/package-agent.md
+++ b/.dispatch/package-agent.md
@@ -69,9 +69,3 @@ The orchestrator runs the authoritative full-graph `typecheck`/`test`/`check` it
 3. New test names + the isolated-verify output above.
 4. **Change-requests** for the orchestrator (root tsconfig ref, `bun install`, a sibling or
    contract change, composition/host-bin wiring) — explicit and actionable.
-
----
-
-> Your specific **TASK** (package name, job, contracts to read, test cases) is appended below by
-> the orchestrator. If you are building an **extension**, the extension-only rules
-> (`.dispatch/extension-agent.md`) are appended first.
diff --git a/ORCHESTRATOR.md b/ORCHESTRATOR.md
index a379320..7ddeba9 100644
--- a/ORCHESTRATOR.md
+++ b/ORCHESTRATOR.md
@@ -129,29 +129,19 @@ 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 write **only the TASK**.
-It goes at the very end, after the briefs and rules are cat'd in.
-
-```markdown
-## TASK
-You are the owner-agent for `packages/<name>/`.
-
-**Read first:** `packages/kernel/src/contracts/<x>.ts` (the types you build
-against), plus `packages/<sibling>/src/index.ts` if you consume a sibling's
-public surface.
-
-**The job:** <precise description of what to build, naming the contract
-types/handles involved>.
-
-**Tests REQUIRED:** <named cases — fakes only for pure, integration for shell>.
-
-**Verify your package in isolation** (do NOT run the whole-graph build):
-`bunx tsc -b packages/<name>/tsconfig.json`, scoped vitest/biome — all clean.
-```
-
-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 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: