Revert "Tell Skywalker when native fleet beats the dispatch protocol"

This reverts commit 909206b.

Author: TheGreatAxios

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

@@ -180,15 +180,6 @@ describe("skywalkerPackage", () => {
     expect(p).toContain("Do not always explorer→implement→critic");
   });
 
-  test("systemPrompt defaults to native fleet and loads dispatch only for an existing tree", () => {
-    const p = skywalkerPackage.systemPrompt;
-    expect(p).toContain("Native fleet vs dispatch/ protocol");
-    expect(p).toContain("Size is not a reason to load dispatch");
-    expect(p).toContain('use_skill("dispatch")');
-    expect(p).toContain("never because the work is large");
-    expect(p).not.toContain("Use counsel or the dispatch skill");
-  });
-
   test("systemPrompt re-dispatches builder on blocking critic", () => {
     const p = skywalkerPackage.systemPrompt;
     expect(p).toContain("blocking");

src/agent/directors/skywalker/package.ts

@@ -119,10 +119,6 @@ Docs/design (PRODUCT.md, ARCHITECTURE.md, docs/design/*, brand) still spawn shak
 
 Track with manage_tasks. Parallelize independent lanes via spawn_agent + wait_agents. After each spawn wave, update the operator before blocking. Escalate blockers with ask_operator. This is your core role.
 
-Native fleet vs dispatch/ protocol — default native:
-- **Native (A):** spawn_agent + wait_agents + manage_tasks. Use this for every new multi-lane job, including large ones. Counsel plans; you fan out. Size is not a reason to load dispatch.
-- **dispatch/ protocol (B):** load use_skill("dispatch") only when (1) a dispatch/<name>/ tree or dispatch.yaml already exists and the job is to run/resume it, or (2) the operator named dispatch / a dispatch.yaml / a spec-as-dispatch-input. Do not create a dispatch/ tree to justify loading the skill.
-
 ## If COMMUNICATION → answer directly
 
 Clear and short. No dispatch for pure questions, digs, "why", screenshots of the UI, or architecture explainers.
@@ -135,8 +131,7 @@ Do not reclassify COMMUNICATION as ORCHESTRATION just to justify parallel spawn
 - Interview when requirements are fuzzy; consult greybeard on architecture/approach.
 - 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: style, philosophy, interview (use_skill is primary-mounted).
-- Load use_skill("dispatch") only for an existing dispatch/ tree or an operator-named dispatch run — never because the work is large.
+- 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