summaryrefslogtreecommitdiffhomepage
path: root/.dispatch
diff options
context:
space:
mode:
Diffstat (limited to '.dispatch')
-rw-r--r--.dispatch/extension-agent.md2
-rw-r--r--.dispatch/package-agent.md6
2 files changed, 1 insertions, 7 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.