Hide dispatch as a Skywalker background library

Skywalker already orchestrates. Keep the on-disk DAG protocol
behind an explicit use_skill load, not in the listing.

Author: TheGreatAxios

CHANGELOG.md

@@ -17,6 +17,8 @@ parallel copies under `docs/` or `scripts/notes/`. At cut time: rename
 
 - First-party skills are how-to playbooks (what to do, in what order, what done looks like),
   not director personas. Identity stays on director system prompts.
+- Dispatch is a background library for an existing `dispatch/` tree. Skywalker
+  orchestrates natively and no longer lists dispatch as an optional skill.
 
 ### Fixed
 

docs/ARCHITECTURE.md

@@ -403,7 +403,7 @@ Corbits Code **ships a bundled catalog** as the first-party data-only plugin `pl
 
 `discoverRepoPlugins` locates `plugins/` next to the source root, at `dist/plugins`, or at `dirname(execPath)/plugins`. It never scans the session cwd for the bundled catalog.
 
-Primary is Skywalker. Bundled skill bodies are **how-to playbooks** (steps, done-definition) — not director personas and not fleet routers. Identity and who-does-what live on director system prompts. Default slashes: `/implement`, `/plan`, `/refactor`, `/review`, `/pull-request-review`, `/create-issue`, `/scribe`, `/interview`, `/ast-grep`. `/review` is how to review a branch (base, scope, signal); `/pull-request-review` is worktree checkout then the review skill; `/scribe` is how to maintain PRODUCT / ARCHITECTURE / IMPLEMENTATION; `/implement` is the per-commit greybeard → implement → gate → critic loop; `/plan` authors an eng change plan and does not implement or file tickets; `/create-issue` remains the tracker command — Linear MCP when available, otherwise `ask_operator` for the platform and persists `Preferred issue tracker` in `.corbits/MEMORY.md`. Dispatch is `use_skill` only, not a default slash. Draper and emil are closed directors via `task(agent=…)`, not slashes. There is no catch-all worker. The operator types the slash; the primary follows the playbook.
+Primary is Skywalker. Bundled skill bodies are **how-to playbooks** (steps, done-definition) — not director personas and not fleet routers. Identity and who-does-what live on director system prompts. Default slashes: `/implement`, `/plan`, `/refactor`, `/review`, `/pull-request-review`, `/create-issue`, `/scribe`, `/interview`, `/ast-grep`. `/review` is how to review a branch (base, scope, signal); `/pull-request-review` is worktree checkout then the review skill; `/scribe` is how to maintain PRODUCT / ARCHITECTURE / IMPLEMENTATION; `/implement` is the per-commit greybeard → implement → gate → critic loop; `/plan` authors an eng change plan and does not implement or file tickets; `/create-issue` remains the tracker command — Linear MCP when available, otherwise `ask_operator` for the platform and persists `Preferred issue tracker` in `.corbits/MEMORY.md`. Dispatch is a background library (`disable-model-invocation`) for an existing `dispatch/` tree — Skywalker orchestrates natively without it. Draper and emil are closed directors via `task(agent=…)`, not slashes. There is no catch-all worker. The operator types the slash; the primary follows the playbook.
 
 #### Discovery and precedence
 

docs/PRODUCT.md

@@ -98,7 +98,7 @@ is the direct, explicit resume path.
 
 The TUI has an extensible slash-command framework. Built-ins include `/help` (shortcut + command overlay), `/model` (models-only picker for connected accounts; **Alt+A** adds a provider), `/settings`, `/permissions`, `/plugins`, `/clear`, `/new`, `/mcp`, and `/yolo` (persists as the user-global skip-permissions default; `--dangerously-skip-permissions` still forces this process; secret-guard and authz still apply; `/yolo [on|off|toggle]`, bare `/yolo` toggles), plus a `/<name>` command per available workflow. When a session starts with the persisted default already on, the TUI shows a startup notice ("Permission prompts are disabled by your saved default…") so the silent machine-wide default is never invisible; `corbits exec` prints the equivalent warning to stderr. Plugins can register additional commands.
 
-**Default skills** exist out of the gate as first-party slash **actions**, not director names: `/implement`, `/plan`, `/refactor`, `/review`, `/pull-request-review`, `/create-issue`, `/scribe`, `/interview`, `/ast-grep`. Each one is a how-to playbook — the slash sends the skill body to the primary, which follows the steps. Skills do not assign identity or route the fleet; that stays on director system prompts. `/review` is how to review a branch; `/scribe` is how to maintain PRODUCT / ARCHITECTURE / IMPLEMENTATION; `/implement` is the per-commit review/build/critique loop; `/plan` authors an eng change plan (files, AC, non-goals, risks, ordered steps) and does not implement. `/create-issue` remains the tracker command: Linear MCP when available; otherwise it `ask_operator`s for the platform (GitHub etc.) and persists `Preferred issue tracker` in `.corbits/MEMORY.md` (GitHub via `gh issue create`). Dispatch is not a default slash — it stays `use_skill` only, along with git-rebase, linear-issue-workflow, style, philosophy, typescript, and opsh (`user-invocable: false`). Draper and emil are not slashes; they remain closed directors via `task(agent=…)`. There is no catch-all worker. Slash names are also available to the model via `use_skill`. Disable the catalog in `/plugins` (`corbits-skills`) if you want them gone.
+**Default skills** exist out of the gate as first-party slash **actions**, not director names: `/implement`, `/plan`, `/refactor`, `/review`, `/pull-request-review`, `/create-issue`, `/scribe`, `/interview`, `/ast-grep`. Each one is a how-to playbook — the slash sends the skill body to the primary, which follows the steps. Skills do not assign identity or route the fleet; that stays on director system prompts. `/review` is how to review a branch; `/scribe` is how to maintain PRODUCT / ARCHITECTURE / IMPLEMENTATION; `/implement` is the per-commit review/build/critique loop; `/plan` authors an eng change plan (files, AC, non-goals, risks, ordered steps) and does not implement. `/create-issue` remains the tracker command: Linear MCP when available; otherwise it `ask_operator`s for the platform (GitHub etc.) and persists `Preferred issue tracker` in `.corbits/MEMORY.md` (GitHub via `gh issue create`). Dispatch is a background library for an existing `dispatch/` tree (hidden from slash and the use_skill listing). `git-rebase`, `linear-issue-workflow`, `style`, `philosophy`, `typescript`, and `opsh` stay `use_skill` only (`user-invocable: false`). Draper and emil are not slashes; they remain closed directors via `task(agent=…)`. There is no catch-all worker. Slash names are also available to the model via `use_skill`. Disable the catalog in `/plugins` (`corbits-skills`) if you want them gone.
 
 Providers are **models-first**: there is no standalone `/login` command. `/model` opens a **models-only list** (Recent, Favorites, then connected provider/model rows) — type-to-filter owns printable keys, so Connect is never a bare letter. **Alt+A** opens a dedicated add-provider selector over every first-class kind (OpenAI dual-path ChatGPT OAuth or API key, xAI, OpenCode Zen, Anthropic, Google, OpenCode Go, Z.AI Coding Plan, Custom), each annotated with its live account count and never filtered out for “already connected.” **Alt+F** toggles favorite on the highlighted model. **Alt+D** persists the highlighted pair as the default without switching the live session. Advanced provider drill-down (edit/delete/tiers) stays on the advanced surface, not a bare printable key while the model list is filtering. OAuth providers open their existing browser login with a named account step so multiple accounts per kind coexist (`codex/work`, …). API-key providers use the same named-instance step before the key (auth-only form: instance name + key + fixed catalog base URL), so personal and team keys land as distinct catalog rows (`openai/default`, `anthropic/work`, …); reusing a name re-keys that instance after confirm. Custom remains a free-form single endpoint (full manual form). Successful connect refreshes the catalog and reopens the model list focused on the new account’s default model. OpenCode Go routes each model by its protocol metadata (chat completions, OpenAI responses, or Anthropic messages) and can show subscription usage in the status bar when active (rolling 5h / weekly / monthly windows when the usage API responds; omitted on auth or network failure). When Go returns a quota or rate-limit error — including some HTTP 400 responses that carry limit payloads — Corbits classifies them so quota aborts cleanly and short provider rate limits remain retryable. On a free-tier or subscription quota hit, wait for the window to reset or use OpenCode Zen free models.
 

plugins/corbits-skills/skills/dispatch/SKILL.md

@@ -1,13 +1,16 @@
 ---
 name: dispatch
 user-invocable: false
+disable-model-invocation: true
 argument-hint: "[<name> | dispatch/<name>/ | dispatch/<name>/dispatch.yaml | <spec-file> ]"
-description: Multi-lane DAG orchestration via use_skill("dispatch"). Spawns explorer, intern, builder, counsel, and critic. Use for DAG product work; tiny edits outside the DAG may be DIY.
+description: On-disk DAG protocol (dispatch.yaml / plan.md / resume). Background library — load via use_skill("dispatch") when a dispatch/ tree already exists. Absent from slash and use_skill listing. Skywalker orchestrates natively without this skill.
 ---
 
 # Dispatch
 
-How to orchestrate parallel director runs across a dependency graph. Fan out work, fan in reports, critique, verify, re-dispatch fixes, and synthesize until done.
+On-disk DAG protocol for an existing `dispatch/` tree. Skywalker orchestrates natively with spawn_agent / wait_agents / manage_tasks — do not load this skill for ordinary multi-lane work.
+
+How to run a `dispatch.yaml` graph: fan out work, fan in reports, critique, verify, re-dispatch fixes, and synthesize until done. Fan out work, fan in reports, critique, verify, re-dispatch fixes, and synthesize until done.
 
 DAG product tasks go through builder workers. Do not write `dispatch.yaml` or `plan.md` on the parent (intern cannot write; builder writes manifests). Tiny / single-file / one-route product edits outside this DAG may be DIY with write_file/edit_file/delete_file.
 

src/agent/directors/identity.test.ts

@@ -80,7 +80,7 @@ describe("formatDirectorSystemPrompt", () => {
     expect(text).not.toContain("use_skill is not mounted on workers");
     expect(text).not.toMatch(/guidance is baked/i);
     expect(text).toContain("use_skill is primary-mounted");
-    expect(text).toContain("dispatch, style, philosophy, interview");
+    expect(text).toContain("style, philosophy, interview");
   });
 
   test("counsel does not bake interview ask_operator guidance (CL-6803)", () => {

src/agent/directors/skywalker/package.test.ts

@@ -56,12 +56,7 @@ describe("skywalkerPackage", () => {
   });
 
   test("optionalSkills order", () => {
-    expect(skywalkerPackage.optionalSkills).toEqual([
-      "dispatch",
-      "style",
-      "philosophy",
-      "interview",
-    ]);
+    expect(skywalkerPackage.optionalSkills).toEqual(["style", "philosophy", "interview"]);
   });
 
   test("primaryIntent and outOfLane", () => {

src/agent/directors/skywalker/package.ts

@@ -112,7 +112,7 @@ Docs/design (PRODUCT.md, ARCHITECTURE.md, docs/design/*, brand) still spawn shak
 1. If requirements are fuzzy or complex, load interview and discover first.
 2. Use explorer workers for scope when needed.
 3. Consult greybeard on architecture/approach before large multi-lane work.
-4. Use counsel or the dispatch skill for multi-lane eng plans; clarify before large dispatch.
+4. Use counsel for multi-lane eng plans; clarify before a large fan-out.
 5. Track progress with manage_tasks; synthesize results for the operator.
 
 ## If ORCHESTRATION → coordinate
@@ -129,9 +129,9 @@ Do not reclassify COMMUNICATION as ORCHESTRATION just to justify parallel spawn
 
 - Tiny/single-file/one-route product edits: write_file/edit_file/delete_file yourself. Substantial, multi-file, parallel, or specialist work: spawn (builder for code; shakespeare / bruckheimer / rand for docs/design unless a one-line fix).
 - Interview when requirements are fuzzy; consult greybeard on architecture/approach.
-- Use counsel or dispatch skill for multi-lane eng plans; clarify before large dispatch.
+- Use counsel for multi-lane eng plans; clarify before a large fan-out.
 - Path tools are the DIY surface; shell file-writes stay denied. Track fleet work with manage_tasks.
-- Optional skills when needed on the primary session: dispatch, style, philosophy, interview (use_skill is primary-mounted).
+- Optional skills when needed on the primary session: style, philosophy, interview (use_skill is primary-mounted). For an existing dispatch/ tree, load use_skill("dispatch").
 
 
 # Spawn graph
@@ -175,7 +175,7 @@ export const skywalkerPackage: DirectorPackage = {
   ],
   description: "Primary orchestration director — chains specialists into a workflow",
   systemPrompt: SKYWALKER_SYSTEM_PROMPT,
-  optionalSkills: ["dispatch", "style", "philosophy", "interview"],
+  optionalSkills: ["style", "philosophy", "interview"],
   tools: { allow: SKYWALKER_TOOLS },
   spawn: {
     maySpawn: true,

tests/unit/corbits-skills-catalog.test.ts

@@ -30,7 +30,6 @@ const SPAWN_RECIPE_SKILLS = ["implement", "dispatch"] as const;
 
 /** use_skill listing + resolve; not slash. No disable-model-invocation. */
 const USE_SKILL_ONLY = [
-  "dispatch",
   "git-rebase",
   "linear-issue-workflow",
   "style",
@@ -40,7 +39,7 @@ const USE_SKILL_ONLY = [
 ] as const;
 
 /** Background libs: absent from slash and use_skill listing; explicit resolve only. */
-const BACKGROUND_ONLY = ["git-worktrees"] as const;
+const BACKGROUND_ONLY = ["git-worktrees", "dispatch"] as const;
 
 const SLASH_SKILLS = [
   "implement",