github-router 0.3.324 → 0.3.326

package/dist/{attribution-settings-sTUXqFzx.js → attribution-settings-17Ug_BaA.js}

@@ -1,6 +1,6 @@
 import { Ln as BALANCED_PROFILE_NATIVE_AGENT_NAMES, Nn as oneMContextDisabled, Pn as withOneMSuffix, Rn as BALANCED_PROFILE_NATIVE_EFFORTS, Un as CHEAPEST_PROFILE_NATIVE_AGENT_NAMES, Wn as CHEAPEST_PROFILE_NATIVE_EFFORTS, Xn as CHEAP_PROFILE_NATIVE_EFFORTS, Yn as CHEAP_PROFILE_NATIVE_AGENT_NAMES, a as buildAgentPrompt, fn as CONDENSED_OPERATING_SEQUENCE, l as maxPersonasFor, n as MCP_GROUPS, pn as DEFINITION_OF_GREATNESS, t as GROUP_META, u as personasFor } from "./peer-mcp-personas-DcAErb_d.js";
 import { a as isUnderClaudeConfigMirror, f as writeRuntimeFileSecure, t as PATHS } from "./paths-BnZwolac.js";
-import { C as CHEAP_REVIEWER_ALIAS_ID, S as CHEAP_PLAN_ALIAS_ID, _ as CHEAPEST_GENERAL_PURPOSE_ALIAS_ID, b as CHEAP_EXPLORE_ALIAS_ID, f as BALANCED_EXPLORE_ALIAS_ID, g as CHEAPEST_EXPLORE_ALIAS_ID, h as BALANCED_REVIEWER_ALIAS_ID, m as BALANCED_PLAN_ALIAS_ID, p as BALANCED_GENERAL_PURPOSE_ALIAS_ID, v as CHEAPEST_PLAN_ALIAS_ID, w as LUNA_SCOUT_ALIAS_ID, x as CHEAP_GENERAL_PURPOSE_ALIAS_ID, y as CHEAPEST_REVIEWER_ALIAS_ID } from "./server-setup-CZ3tEsgq.js";
+import { C as CHEAP_REVIEWER_ALIAS_ID, S as CHEAP_PLAN_ALIAS_ID, _ as CHEAPEST_GENERAL_PURPOSE_ALIAS_ID, b as CHEAP_EXPLORE_ALIAS_ID, f as BALANCED_EXPLORE_ALIAS_ID, g as CHEAPEST_EXPLORE_ALIAS_ID, h as BALANCED_REVIEWER_ALIAS_ID, m as BALANCED_PLAN_ALIAS_ID, p as BALANCED_GENERAL_PURPOSE_ALIAS_ID, v as CHEAPEST_PLAN_ALIAS_ID, w as LUNA_SCOUT_ALIAS_ID, x as CHEAP_GENERAL_PURPOSE_ALIAS_ID, y as CHEAPEST_REVIEWER_ALIAS_ID } from "./server-setup-BfTjAZS2.js";
 import { c as FAST_PROFILE_MODELS, d as FAST_PROFILE_NATIVE_MODELS, l as FAST_PROFILE_NATIVE_AGENT_NAMES, u as FAST_PROFILE_NATIVE_EFFORTS } from "./fast-profile-contract-DmsyQQrw.js";
 import { C as MAX_PARALLELISM_RULE, S as MAX_COORDINATOR_PROMPT, T as maxNativePrompt, a as MAX_PROFILE_NATIVE_AGENT_NAMES, i as MAX_PROFILE_MODELS, o as MAX_PROFILE_NATIVE_EFFORTS, s as MAX_PROFILE_NATIVE_MODELS, w as maxNativeDescription, x as MAX_COORDINATOR_DESCRIPTION } from "./max-profile-contract-Bl7I_EOC.js";
 import "./self-invocation-opSXHEs0.js";
@@ -2074,23 +2074,33 @@ const GATHER_CONTEXT_SKILL = {
 	name: "gh-gather-context",
 	md: `---
 name: gh-gather-context
-description: Bounded context gathering for non-trivial asks: decomposes the ask, runs lexical code searches to identify relevant files, dispatches bounded parallel explore workers to gather evidence, stitches results into a freshness-stamped context brief plus a compact version. Use when grounded context is needed before planning or changing code.
+description: Gather grounded codebase context before planning. Use when unfamiliar code must be understood, files located, or claims verified against source. Returns a freshness-stamped brief with file:line citations. Not for trivial reads or already-known code.
 user-invocable: true
+requires: []
+produces: [context.md, context.compact.md, .complete]
+consumes: []
+excludes: [trivial tasks, already-known code, implementation]
 ---
 
 # gh-gather-context: bounded context gathering
 
 Use this skill when a non-trivial ask needs grounded context before planning.
-All reasoning runs at the 200K default window: the lead and every explore
-worker use the Luna model at high effort with bare slugs (no 1M accounting).
-Output is a durable full brief plus a compact downstream version.
+All reasoning runs at the 200K default window: the lead and every Explore
+subagent use the Luna model at high effort with bare slugs (no 1M accounting).
+Output is a durable full brief plus a compact downstream version. This skill
+dispatches ONLY native subagents present on the profile roster (Explore) via
+the Agent tool, never worker-* MCP dispatchers. No reviewer dispatch in this
+stage: Explore evidence plus targeted follow-up reads is the verification path.
 
 ## Hard bounds
 
 - Maximum rounds: 3.
-- Maximum parallel explore workers per round: 6.
+- Maximum parallel Explore subagents per round: 6.
 - Maximum lexical searches per round: 10.
 - Maximum follow-up reads per round: 5.
+- Advisory budget: keep each Explore dispatch under ~3 minutes of wall-clock;
+  the Task tool has no maxWallClockMs parameter, so count your own dispatches
+  and stop at saturation rather than running to a clock.
 - Terminate at the first of saturation or a cap.
 - On cap-hit, return with open unknowns flagged as residual. Do not loop forever.
 
@@ -2100,7 +2110,6 @@ Use these exact tags on every finding and claim:
 
 - verified-executable: reproduced the symptom, ran the failing test, or ran a check that directly proves the claim. This is the only deterministic confidence tag.
 - verified-source: read the actual source, config, logs, docs, or primary artifact and cited the relevant locations. This is model-mediated and can still be wrong.
-- cross-lab-agreed: a different-lab reviewer independently agreed with the claim. This reduces correlated blind spots but is advisory.
 - unverified: plausible but not confirmed; treat as residual risk.
 
 ## Procedure
@@ -2119,16 +2128,16 @@ Use these exact tags on every finding and claim:
    - Use git log and git blame when authorship, regression timing, or intent matters.
    - Use mcp__search__web for upstream APIs, package behavior, protocol docs, or public issues.
 
-4. Decompose into bounded explore workers.
+4. Decompose into bounded Explore subagents.
    - Cluster search results into at most 6 coherent investigation areas.
    - For each area, write a narrow brief: the specific question, the expected artifact, and the files to focus on.
-   - Dispatch ALL explore workers in a single turn via the Agent tool (subagent_type worker-explore). Each runs read-only at the 200K default window and returns a summary with an evidence table and file:line citations. Pass maxWallClockMs 180000 on every worker call so a hung worker is reaped after 3 minutes instead of blocking its slot.
-   - Keep worker results summarized; do not paste every detail into the main context.
+   - Dispatch ALL Explore subagents in a single turn via the Agent tool (subagent_type Explore). Each runs read-only at the 200K default window and returns a summary with an evidence table and file:line citations. Advisory: keep each dispatch under ~3 minutes; the Task tool enforces no wall-clock, so terminate at saturation.
+   - Keep Explore results summarized; do not paste every detail into the main context.
 
 5. Stitch and verify.
-   - Collect all explore results and deduplicate file references.
-   - Run at most 5 targeted follow-up reads for gaps, in parallel.
-   - Dispatch the worker-review subagent (via the Agent tool, maxWallClockMs 300000) to confirm source-reading for load-bearing claims.
+   - Collect all Explore results and deduplicate file references.
+   - Run at most 5 targeted follow-up reads for gaps, in parallel, using Read, Grep, and Glob directly; dispatch one more narrow Explore round only for gaps direct reads cannot close.
+   - Do NOT dispatch a reviewer in this stage. Verification here is Explore evidence plus your own follow-up reads: re-open the primary source for every load-bearing claim and confirm the citation is real before tagging it verified-source.
    - Form a root-cause hypothesis or integration map, and state what would falsify it.
 
 6. Run a completeness pass.
@@ -2137,29 +2146,46 @@ Use these exact tags on every finding and claim:
    - Ask: have we checked primary sources for every load-bearing claim?
    - If no material unknowns remain and the root cause is at least verified-source, stop for saturation.
 
-7. Persist two outputs under .github-router/context/<slug>/.
-   - context.md: full brief with the ask decomposition, searches run, worker reports, evidence table, hypothesis, freshness metadata (HEAD commit, working-tree diff hash, timestamp, repo path), residuals, and full citations.
+7. Persist outputs under .github-router/context/<slug>/ and close the stage.
+   - context.md: full brief with the ask decomposition, searches run, Explore reports, evidence table, hypothesis, freshness metadata (HEAD commit, working-tree diff hash, timestamp, repo path), residuals, and full citations.
    - context.compact.md: downstream consumable with a one-paragraph ask summary, key files with one-line purposes, critical constraints (APIs, types, patterns, forbidden changes), integration seams, and residual risks.
+   - .complete: stage-completion marker written ONLY after every dispatched Explore subagent has returned or been recorded as superseded, and both briefs are on disk. No downstream stage (/gh-plan, /gh-implement, /gh-swe-pipeline stage 2+) may start until this marker exists.
    - Downstream phases read by pointer and check freshness instead of re-injecting the whole brief.
 
+## Waterfall rule
+
+This stage owns all Explore dispatches until it completes. Do NOT return while
+any Explore subagent is still running unless you explicitly record it as
+superseded (saturation reached or its area covered) with the reason. Native
+subagents cannot be killed mid-run: record superseded areas and let them
+finish, but do not wait on or use their output. If the brief already saturates
+the ask, record remaining dispatches as superseded first (no further
+follow-ups), then write the marker. A plan built on shifting evidence wastes
+more than an idle subagent costs.
+
 ## Return format
 
-Return a compact brief, not the whole dump:
+Return a compact brief, not the whole dump. Output cost dominates: Luna output
+tokens cost 6x input, so return only file:line citations with one-line
+summaries, never full file contents or pasted source blocks.
 
 - Context files: paths to context.md and context.compact.md.
 - Freshness: HEAD commit, diff hash, timestamp.
 - Termination: saturated or cap-hit; if cap-hit, name the cap.
 - Summary: 3-8 bullets with confidence tags.
-- Evidence table: claim, tag, primary source or command, reviewer status.
+- Evidence table: claim, tag, primary source or command, verification status.
 - Residual unknowns: explicit list, or none.
 - Downstream guidance: recommended next action and what must be rechecked if the tree changes.
 
 ## Non-goals
 
-- Do not present verified-source or cross-lab-agreed as deterministic.
+- Do not present verified-source as deterministic.
 - Do not hide open unknowns because the answer looks useful.
 - Do not keep searching after the cap.
 - Do not paste the entire persisted brief into later turns unless the user asks.
+- Do not dispatch a reviewer from this stage; Explore evidence plus targeted follow-up reads is the verification path.
+- Do not return full file contents in briefs, summaries, or evidence tables; cite file:line plus one line of purpose.
+- Do not finish without the .complete marker: a marker-less brief is not a completed stage.
 `
 };
 //#endregion
@@ -2168,51 +2194,85 @@ const IMPLEMENT_SKILL = {
 	name: "gh-implement",
 	md: `---
 name: gh-implement
-description: Parallel implementation of an approved plan using bounded Luna workers with isolated worktrees: each worker implements its task, self-tests, self-reviews, and returns a patch; the lead aggregates into a unified diff, runs staged review, and returns the final diff with a report. Use when a user-approved plan is ready for execution.
+description: Execute an approved plan with parallel subagents and self-validation. Use when a user-approved plan.md is ready for execution. Reviewer only on low-confidence or risky changes. Not for unapproved plans or exploration.
 user-invocable: true
+requires: [approved plan.md with .complete marker]
+produces: [unified diff, implementation-report.md]
+consumes: [plan.md]
+excludes: [unapproved plans, exploration, trivial changes]
 ---
 
 # gh-implement: bounded parallel implementation with staged review
 
 Use this skill only after /gh-plan produced a user-approved plan.md. All
-implementation runs at the 200K default window: the lead and every task worker
-use the Luna model at max effort with bare slugs (no 1M accounting). Review is
-staged: a Luna max pass first, then a Sol medium pass only for major issues.
+implementation runs at the 200K default window with bare slugs (no 1M
+accounting): the lead dispatches native subagents present on the profile
+roster. If an implementer subagent exists (max profile), use it first for
+implementation tasks, then General-Purpose for handoffs; otherwise use
+General-Purpose for all tasks. Review is conditional, never staged by default:
+each task subagent self-tests, self-reviews, and reports an explicit confidence
+verdict; the lead dispatches a reviewer only on low-confidence validation or
+complex and risky changes, then a General-Purpose fix pass only for major
+reviewer findings. This skill dispatches ONLY native subagents via the Agent
+tool, never worker-* MCP dispatchers.
 
 ## Hard bounds
 
-- Maximum concurrent implement workers: 8.
+- Maximum concurrent implementation subagents: 8 (advisory; the Task tool
+  enforces no concurrency cap, so count your own dispatches).
 - Maximum retries per task: 2.
 - Maximum review-fix cycles: 2.
-- Worktrees are auto-removed on success and retained on failure for debugging.
+- Advisory budget: keep each task under ~10 minutes; the Task tool enforces
+  no wall-clock, so terminate at acceptance, not at a clock.
+- Worktrees are opt-in, not default: pass worktree:true to
+  General-Purpose when parallel tasks require isolation or git-history
+  protection. In-place tasks must be sequentialized to avoid collisions;
+  parallel in-place edits to the same files will conflict.
+
+## Stage gate 0 (do this BEFORE any implementation)
+
+1. Verify the plan stage is finished: .github-router/plans/<slug>/plan.md AND
+   its .complete marker both exist, with an explicit user-approval record. If
+   any is missing, STOP: do not implement an unapproved plan. Finish or
+   re-invoke planning first.
+2. Check freshness: if HEAD or the working-tree diff hash moved since the
+   plan was approved, re-verify stale load-bearing assumptions before
+   dispatching subagents.
+3. Close the previous stage: send no further follow-ups to any lingering Plan
+   dispatches (Explore follow-ups) and record them as superseded with the
+   reason. Native subagents cannot be killed mid-run: let them finish but do
+   not wait on or use their output. Implementing while planning still runs
+   builds on a moving target and wastes both stages. Only advance once every
+   Plan dispatch has returned or is recorded as superseded.
 
 ## Procedure
 
 1. Parse the approved plan.
    - Read plan.md fully.
    - Group tasks by parallelGroup; order groups by dependency.
-   - For each group, prepare an isolated git worktree per task plus a narrow task brief (task spec, relevant context excerpt, acceptance criteria, verification commands).
+   - For each group, prepare a narrow task brief (task spec, relevant context excerpt, acceptance criteria, verification commands). Write every brief as plain directives, never reflective first-person prose: Gemini-run subagents may suppress tool calls when the prompt contains reflective text. If parallel tasks in the group require isolation, prepare one git worktree per task and pass worktree:true; otherwise tasks run in-place and must be sequentialized within shared files.
 
-2. Dispatch bounded implement workers, one parallel batch per group.
-   - Dispatch ALL tasks in the group in a single turn via the Agent tool (subagent_type worker-implement, with worktree isolation, maxWallClockMs 600000 per task so a hung worker is reaped after 10 minutes instead of blocking its slot).
-   - Each worker runs at the 200K default window and must self-contain its work:
+2. Dispatch bounded implementation subagents, one parallel batch per group.
+   - Dispatch ALL tasks in the group in a single turn via the Agent tool. Use subagent_type implementer first where the profile provides one (max), otherwise subagent_type General-Purpose for every task. Advisory: keep each task under ~10 minutes; the Task tool enforces no wall-clock.
+    - Each subagent runs at the 200K default window and must self-contain its work:
      a. Implement the change.
      b. Run the task verification commands (tests, typecheck, lint).
      c. Self-review against the acceptance criteria.
      d. Fix any self-found issues (at most 2 internal fix cycles).
-     e. Return the patch plus test results and self-review notes.
+     e. Return the patch plus test results, self-review notes, and an explicit confidence verdict (high or low) with reasons. Low confidence means the subagent itself doubts the result: flaky or incomplete verification, untested edge cases, or behavior it could not directly observe. Keep the return compact: patch plus results, no full-file echoes; output tokens cost several times input on every profile.
    - Do NOT dispatch the same task twice (no dedup exists); a retry is a new dispatch only after a recorded failure.
-   - For a big artifact, have the worker write it to a file and return the path.
+   - For a big artifact, have the subagent write it to a file and return the path.
 
 3. Aggregate and validate.
-   - Collect all patches and apply them sequentially to the main worktree (or merge the worktrees).
+   - Collect all patches and apply them sequentially to the main worktree (or merge the worktrees when worktree isolation was used).
    - Run the full relevant validation: test suite, typecheck, and lint.
-   - If any task fails validation, route it back to an implement worker (at most 2 retries per task). If it still fails, checkpoint with the failure as residual risk instead of pretending it is solved.
+   - If any task fails validation, route it back to a General-Purpose subagent (at most 2 retries per task). If it still fails, checkpoint with the failure as residual risk instead of pretending it is solved.
 
-4. Run staged review.
-   - Pass 1 (always): dispatch the worker-review subagent (via the Agent tool, maxWallClockMs 300000) over the unified diff for correctness against acceptance criteria, code quality and consistency, security and performance regressions, and test coverage. Categorize findings as minor (style, nits) or major (logic, architecture).
-   - If pass 1 finds no major issues, finish here.
-   - Pass 2 (major issues only): dispatch a fix worker (via the Agent tool, maxWallClockMs 300000) at the 200K default window using the Sol model at medium effort with the flagged areas, the failing checks, and the pass-1 findings. It returns fixed patches or an explicit escalate-to-user with reasons.
+4. Decide whether external review is warranted (default: skip it).
+   - Skip the reviewer when every task reports high confidence AND full validation (tests, typecheck, lint) passes AND the change avoids high-risk areas (auth, user input, database queries, crypto, serialization, data migration, cross-boundary contracts) AND the lead judges the change non-complex. Record the skip with reasons in the implementation report; self-validation plus green checks is the default path, not a shortcut.
+   - Dispatch the reviewer subagent (via the Agent tool, subagent_type reviewer) ONLY when a task reports low confidence, validation is incomplete or unconvincing, the change touches high-risk areas, or the lead explicitly requested review. Scope the brief to the uncertain areas, the acceptance criteria, and the failing or insufficient checks. Categorize findings as minor (style, nits) or major (logic, architecture). Advisory: keep the review under ~5 minutes.
+   - If the reviewer finds no major issues (or review was skipped with recorded reasons), finish here.
+   - Fix pass (major reviewer findings only): dispatch a General-Purpose subagent (via the Agent tool) at the 200K default window with the flagged areas, the failing checks, and the reviewer findings. It returns fixed patches or an explicit escalate-to-user with reasons. At most 2 review-fix cycles.
 
 5. Finalize.
    - Apply any review fixes and re-run full validation.
@@ -2227,14 +2287,16 @@ Return:
 - Implementation report path.
 - Task completion status per task id.
 - Test, typecheck, and lint results.
-- Review summary (pass 1 findings; pass 2 findings and fixes if used).
+- Review summary (skipped with recorded reasons, or reviewer findings; fix-pass findings and fixes if used).
 - Final residual risks and next action.
 
 ## Non-goals
 
-- Do not start without a user-approved plan.md.
-- Do not serialize work that has no data dependency; independent tasks in a group run concurrently.
-- Do not nest workflow invocations: workers are internal sessions and must not re-invoke /gh-implement.
+- Do not start without a user-approved plan.md plus its .complete approval record.
+- Do not start while Plan dispatches still run; record them superseded first.
+- Do not dispatch a reviewer by default; self-validation plus green checks is the default path.
+- Do not serialize work that has no data dependency; independent tasks in a group run concurrently (sequentialize only in-place edits to shared files).
+- Do not nest workflow invocations: subagents must not re-invoke /gh-implement (or any /gh-* pipeline skill).
 - Do not claim completeness when retries or review cycles are exhausted with open failures.
 `
 };
@@ -2382,59 +2444,108 @@ const PLAN_SKILL = {
 	name: "gh-plan",
 	md: `---
 name: gh-plan
-description: Holistic planning from gathered context: ingests the context brief, creates a scoped modular ordered implementation plan with explicit tasks for cheap implementation workers, surfaces open questions for user approval, and persists plan.md. Use when a non-trivial change needs a reviewed plan before implementation.
+description: Create an implementation plan from gathered context. Use when a non-trivial change needs a reviewed, ordered task list with acceptance criteria before implementing. Requires user approval. Not for trivial changes or missing context.
 user-invocable: true
+requires: [fresh context.md with .complete marker]
+produces: [plan.md, .complete]
+consumes: [context.md, context.compact.md]
+excludes: [trivial changes, implementation, missing context]
 ---
 
-# gh-plan: holistic planning for cheap implementation
+# gh-plan: native Plan-subagent planning
 
 Use this skill after /gh-gather-context (or when equivalent context is already
-available) and before any implementation. The planner runs at the 200K default
-window using the Sol model at medium effort. The plan must be scoped, modular,
-non-overlapping, and ordered, with enough detail for Luna implementation
-workers to execute each task in isolation. User approval is mandatory before
-implementation.
+available) and before any implementation. For non-trivial work, dispatch the
+native Plan subagent (subagent_type Plan) present on every pipeline profile
+roster; profile frontmatter pins its model and effort (Sol at the 200K default
+window). The plan must be scoped, modular, non-overlapping, and ordered, with
+enough detail for a native General-Purpose (or implementer, where the profile
+provides one) subagent to execute each task in isolation. User approval is
+mandatory before implementation. This skill dispatches ONLY the native Plan
+subagent via the Agent tool, never worker-* MCP dispatchers. Plan self-serves
+Explore follow-ups per its delegation graph; the skill does not dispatch
+Explore directly.
 
 ## Prerequisites
 
 - A freshness-stamped context brief from /gh-gather-context, or equivalent context.
 - Read context.compact.md first; read context.md sections on demand (residual unknowns, evidence table).
 
+## Stage gate 0 (do this BEFORE any planning)
+
+1. Verify the context stage is finished: .github-router/context/<slug>/.complete
+   exists. If the marker is missing, STOP: do not plan on a partial brief.
+   Finish or re-invoke gathering first.
+2. Check freshness: if HEAD or the working-tree diff hash moved since the
+   brief's stamp, re-verify stale load-bearing claims before using them.
+3. Close the previous stage: send no further follow-ups to any lingering
+   gather-context Explore dispatches and record them as superseded with the
+   reason. Native subagents cannot be killed mid-run: let them finish but do
+   not wait on or use their output. Planning while Explore subagents still run
+   builds on shifting evidence and wastes both stages. Only advance once every
+   Explore dispatch has returned or is recorded as superseded.
+
+## Triviality reassessment (do this AFTER gate 0, BEFORE dispatching Plan)
+
+1. Reassess with fresh context: if the ask is trivial (typo, one-line config
+   read, obvious change of at most a few lines, pure explanation) or the
+   context shows no multi-file, risky, uncertain, or high-impact work, STOP.
+   Do NOT dispatch Plan. Do NOT write plan.md or .complete.
+2. Return a trivial verdict: one-sentence reason, the recommended direct
+   action, and an explicit statement that no downstream stage (/gh-implement,
+   /gh-swe-pipeline stage 3) may run. A trivial ask must never pay planning
+   cost as ritual.
+
 ## Hard bounds
 
 - Maximum tasks: 20.
 - Maximum parallel groups: 5.
 - Keep planner input well under the 200K window (target at most around 150K tokens of context) so there is headroom for reasoning and output. This is self-discipline, not an enforced cap: prefer the compact brief and read full sections only on demand.
+- Advisory budget: keep the Plan dispatch under ~5 minutes; the Task tool enforces no wall-clock. At most 2 bounded follow-up rounds to the same Plan dispatch for gaps.
 
-## Procedure
+## Procedure (non-trivial work only)
 
 1. Ingest context.
    - Read context.compact.md fully.
    - Read the evidence table and residual unknowns from context.md.
    - Identify acceptance criteria, constraints, integration seams, and forbidden changes.
 
-2. Build a blind-spot table before decomposing.
-   - Wrong-spec risk: judgment-only, mitigated only by user-blessed acceptance criteria.
-   - Root-cause risk: executable-checkable if reproduced or covered by a failing test; otherwise advisory.
-   - Integration risk: usually source-verified plus tests where possible.
-   - Regression risk: executable-checkable when tests, typecheck, or lint cover it.
-   - Review risk: advisory cross-lab review reduces correlated blind spots.
-   - Concurrency or merge risk: source-verified and sometimes executable-checkable.
-   - Missing-test risk: executable-checkable only after a test exists and runs.
-   - Tag every blind spot as executable-checkable or judgment-only.
-
-3. Decompose into minimal safe increments.
-   - Each task touches a single file or a tightly coupled file group.
-   - Each task states input artifacts, output artifact, acceptance criteria, verification commands, and rollback concern.
-   - Order tasks by dependency (topological sort); tasks with no data dependency share a parallel group.
-   - Keep each task small enough for one Luna worker at the 200K window (target at most 50K context tokens of relevant files per task).
-   - If the ask needs discovery follow-ups, delegate them to worker-explore background subagents (via the Agent tool, maxWallClockMs 180000) rather than bloating the plan.
-
-4. Surface open questions before finalizing.
-   - Ask about ambiguous acceptance criteria, design decisions with multiple valid approaches, risk tolerance, and test strategy.
-   - Present a short candidate list for confirmation where possible.
-
-5. Persist the plan to .github-router/plans/<slug>/plan.md.
+2. Compose the Plan dispatch brief. Include every item below; a vague brief
+   produces a vague plan, and a vague plan fails downstream:
+   - Ask summary and acceptance criteria (or candidates where ambiguous).
+   - Constraints, integration seams, and forbidden changes.
+   - Context pointers: context.compact.md path, the evidence table and
+     residual sections of context.md, plus the freshness stamp.
+   - Required output shape: objective; architectural invariants; interface
+     contracts; execution steps with files touched plus a done condition per
+     step; acceptance commands with the observable pass result; critical files
+     as file:line; a blind-spot table tagging each risk executable-checkable
+     or judgment-only (wrong-spec, root-cause, integration, regression,
+     review, concurrency or merge, missing-test); open questions as options
+     with a recommendation; cost estimate (task count, parallel groups,
+     context tokens).
+   - Plan-mode rule: plan and acceptance criteria only, no implementation
+     file edits.
+   - Permission to use Explore and reviewer per the delegation graph.
+   - Write the brief as plain directives, never reflective first-person prose:
+     Gemini-run subagents may suppress tool calls when the prompt contains
+     reflective text.
+   - Demand compact output: file:line plus one-line purposes, never pasted
+     source blocks. Output tokens cost several times input on every profile.
+   - Advisory ~5 minute budget.
+
+3. Dispatch ONE Plan subagent via the Agent tool (subagent_type Plan) with
+   that brief, then WAIT for its full return. Do not plan inline in parallel
+   and do not dispatch implementation subagents while it runs.
+
+4. Validate the returned plan. Every task must name files, state the change
+   and its done condition, and carry runnable acceptance commands;
+   trade-offs must appear as options with a recommendation. If gaps remain,
+   send ONE bounded follow-up to the same Plan dispatch naming the exact gaps
+   (at most 2 follow-up rounds total). If still underspecified, checkpoint
+   with the gaps as residual risk instead of pretending the plan is complete.
+
+5. Persist the validated plan to .github-router/plans/<slug>/plan.md.
    - Ask summary and user-blessed acceptance criteria.
    - Blind-spot table with executable-checkable or judgment-only tags.
    - Ordered task list with ids, files, dependencies, parallel groups, acceptance criteria, verification commands, rollback concerns, and estimated context tokens.
@@ -2446,11 +2557,13 @@ implementation.
    - Present the goal, acceptance criteria, task-to-group map, per-task blind spot killed, residual risks, and cost estimate.
    - If the user rejects scope or cost, downshift to the smallest plan that kills the important blind spots.
    - Do not proceed to implementation without approval.
+   - Write .github-router/plans/<slug>/.complete ONLY after explicit user approval, recording the approval in the marker. A plan without an approval record is NOT complete, and no downstream stage (/gh-implement, /gh-swe-pipeline stage 3) may start without it.
 
 ## Return format
 
 Return:
 
+- Trivial exit: yes with the recommended direct action and no plan file, or no with the plan below.
 - Plan file: path to the durable plan.md.
 - Task count and parallel groups.
 - Open questions and user answers.
@@ -2459,9 +2572,12 @@ Return:
 
 ## Non-goals
 
+- Do not dispatch Plan for a trivial ask; exit with a trivial verdict instead.
 - Do not edit implementation files while planning; in plan mode, produce the plan and acceptance criteria only.
 - Do not present judgment-only conclusions as executable guarantees.
 - Do not hide open unknowns because the plan looks complete.
+- Do not start planning while gather-context Explore subagents still run; record them superseded first.
+- Do not dispatch implementation subagents from planning: stages never overlap.
 `
 };
 //#endregion
@@ -2576,6 +2692,129 @@ Return a compact brief, not the whole research dump:
 `
 };
 //#endregion
+//#region src/lib/injected-skills/swe-pipeline-skill.ts
+const SWE_PIPELINE_SKILL = {
+	name: "gh-swe-pipeline",
+	md: `---
+name: gh-swe-pipeline
+description: Strict sequential SWE pipeline for non-trivial code changes: runs gather-context to completion, then plan with user approval, then implement with conditional review. Each stage waits for the previous to finish fully, superseding leftover subagents before advancing. Use when the user wants the full structured engineering workflow in one command.
+user-invocable: true
+---
+
+# gh-swe-pipeline: strict sequential SWE workflow
+
+Use this skill when the user invokes /gh-swe-pipeline for a non-trivial code
+change. It coordinates the three pipeline stages in STRICT SEQUENCE. No two
+stages ever overlap: each stage runs to completion, its subagents are all
+finished or explicitly superseded, and its completion artifact exists before
+the next stage starts. Every stage dispatches ONLY native subagents present on
+the profile roster (Explore, Plan, General-Purpose, reviewer, implementer
+where provided) via the Agent tool, never worker-* MCP dispatchers.
+
+All work runs at the 200K default window with bare slugs (no 1M accounting).
+Advisory budgets (the Task tool enforces no wall-clock): gather ~3 minutes
+per round, plan ~5 minutes total, implement ~10 minutes per task.
+
+## The one rule
+
+WATERFALL ONLY. Never start a stage while the previous stage still has running
+subagents or an unwritten completion artifact. If a stage already has enough
+evidence to proceed, FIRST record every still-running subagent from the
+previous stage as superseded (native subagents cannot be killed mid-run: send
+no further follow-ups, let them finish, and do not use their output), record
+what was superseded and why, THEN advance. Overlapping stages waste money and
+produce plans built on shifting evidence. This is the failure the pipeline
+exists to prevent.
+
+## Stage 0: triage (no subagents)
+
+1. Restate the ask in one sentence.
+2. Decide trivial versus non-trivial. Trivial (typo, one-line config read,
+   obvious three-line fix, pure explanation) SKIPS the pipeline: say why and
+   do the work directly. Do not pay orchestration cost as ritual.
+3. For non-trivial work, derive a run slug and create
+   .github-router/swe/<slug>/run.md with the ask, the triage verdict, and
+   per-stage status (pending, running, complete, skipped).
+
+## Stage 1: gather context (to completion)
+
+1. Invoke the gh-gather-context skill and WAIT for its full return. Do not
+   plan, sketch tasks, or dispatch Plan subagents while it runs.
+2. Its completion artifact is
+   .github-router/context/<slug>/context.md plus context.compact.md and a
+   .complete marker. If the marker is missing, the stage is NOT complete:
+   keep waiting or re-invoke; never advance on a partial brief.
+3. Early-stop rule: if the returned brief already saturates the ask (root
+   cause at least verified-source, no material unknowns), record any
+   still-running Explore dispatches as superseded (no follow-ups), accept the
+   brief, and advance. Do not keep searching after saturation.
+4. Cap-hit rule: if the brief reports cap-hit with residuals, surface the
+   residuals in run.md and ask the user whether to proceed to planning with
+   the gap or to spend one more bounded round. Do not silently treat a
+   cap-hit brief as complete.
+
+## Stage 2: plan (to user approval, or trivial exit)
+
+1. Precondition check BEFORE invoking gh-plan: the context .complete marker
+   exists AND every gather-context Explore dispatch has returned or been
+   recorded as superseded. If either is false, do not invoke planning. Fix
+   stage 1 first.
+2. Invoke the gh-plan skill and WAIT for its full return. For non-trivial
+   work gh-plan dispatches the native Plan subagent with an
+   implementation-ready brief; do not dispatch implementation subagents,
+   sketch diffs, or edit implementation files while it runs. Plan mode means
+   plan and acceptance criteria only.
+3. Trivial exit: if gh-plan returns a trivial verdict (no plan.md, no
+   .complete), STOP the pipeline here. Record the verdict and the recommended
+   direct action in run.md and do NOT advance to implementation.
+4. Its completion artifact is .github-router/plans/<slug>/plan.md with a
+   user-approval record (.complete marker written only after explicit
+   approval). A plan without explicit user approval is NOT complete.
+5. Present the goal, acceptance criteria, task-to-group map, residual risks,
+   and cost estimate. Wait for explicit approval. If the user rejects scope
+   or cost, downshift to the smallest plan that kills the important blind
+   spots and re-seek approval. NEVER advance to implementation without
+   approval recorded in run.md.
+
+## Stage 3: implement (to validated diff, reviewed only when warranted)
+
+1. Precondition check BEFORE invoking gh-implement: plan.md exists, its
+   .complete marker exists, and run.md records explicit user approval. If
+   any is missing, do not invoke implementation. Fix stage 2 first.
+2. Record any lingering Plan dispatches (Explore follow-ups) as superseded
+   before the first implement dispatch.
+3. Invoke the gh-implement skill and WAIT for its full return: unified diff,
+   implementation report, test/typecheck/lint results, and review summary
+   (or recorded skip when self-validation plus green checks sufficed).
+   gh-implement dispatches a reviewer only on low-confidence validation or
+   complex and risky changes; do not demand a review that the stage skipped
+   with recorded reasons.
+4. If retries or review cycles exhaust with open failures, checkpoint with
+   the failure as residual risk instead of pretending it is solved.
+
+## Return format
+
+Return:
+
+- Run file: path to .github-router/swe/<slug>/run.md with per-stage status.
+- Context files: paths to context.md and context.compact.md, freshness
+  (HEAD commit, diff hash, timestamp), termination (saturated or cap-hit).
+- Plan file: path to plan.md, task count, parallel groups, open questions
+  and user answers, cost estimate, approval record.
+- Implement output: unified diff path, report path, per-task status, test
+  results, review summary or recorded skip.
+- Residual risks and next action.
+
+## Non-goals
+
+- Do not run stages in parallel or overlap subagents across stages.
+- Do not advance past a missing completion artifact or a missing approval.
+- Do not nest pipeline invocations: subagents must not re-invoke
+  /gh-swe-pipeline or any /gh-* pipeline skill.
+- Do not present judgment-only conclusions as executable guarantees.
+`
+};
+//#endregion
 //#region src/lib/injected-skills/worker-skill.ts
 /**
 * The `/gh-worker` skill: the operating model for the NON-BLOCKING workers
@@ -2832,6 +3071,79 @@ You are running inside an ai-or-die tab, so the \`${toolPrefix}*\` tools drive a
 * dashes and does not mention any Claude / Anthropic attribution.
 */
 const STYLE_DIRECTIVE = "Write concisely without losing detail. Use a natural human voice. Avoid em dashes. Do not attribute work to Claude, AI, LLM, or Anthropic anywhere (commits, PRs, issues, code, comments, docs).";
+/**
+* Operating-defaults directive injected at the TOP of the mirrored CLAUDE.md.
+* The main agent's system prompt (`--append-system-prompt`) gets
+* OPERATING_DEFAULTS_DIGEST instead, with this full statement available through
+* CLAUDE.md. Three defaults, layered under the user's own
+* direction and the domain's standards as addons (on a direct conflict the
+* user's direction wins, then the domain standard, then the default below):
+*
+*   1. Orchestrate (strong default): delegate the heavy / parallel /
+*      context-heavy work to the right subagent / worker / model, keeping the
+*      main context free to reason and collaborate with the user, while still
+*      doing trivial / surgical / last-mile work directly (delegating that
+*      would only add relay-fidelity loss + latency).
+*   2. Adversarial review: WHEN a peer critic earns its keep and, equally
+*      important, when reaching for one is ritual rather than review. Same
+*      failure shape the delegation default had: "consult a critic for
+*      non-trivial changes" is unfalsifiable in advance, so it collapses into
+*      either never (four of four unprimed agents) or always (worse than
+*      never). The discriminator is whether the conclusion still turns on
+*      judgment once the direct evidence is in: a consequential recommendation
+*      cannot be run, which is exactly where confabulation hides, while a
+*      tracing question a search already proved gains nothing from a second
+*      model re-deriving it. The roster, the lens-to-artifact match, the
+*      advisor-complements-rather-than-substitutes distinction, and the
+*      do-not-anchor-the-critic rule live here; the digest carries only the
+*      trigger and the ritual exclusion.
+*   3. Excellence lens: the principles stated plainly and concretely (radical
+*      simplicity + real-user focus; whole-system first-principles thinking that
+*      anticipates scale; work back from the customer outcome). Named exemplars
+*      were dropped per the injected-surface review: a named entity is a dense,
+*      high-variance vector that pulls in persona mannerisms at top salience, and
+*      the guidance favors specific functional framing over comparison, so
+*      specificity carries the vividness instead.
+*   4. Engineering excellence: quality / robustness / maintainability over
+*      development cost; reproduce a bug end-to-end (as a real user hits it)
+*      before fixing so the fix targets the real cause; a pixel-perfect UI bar;
+*      and fix any lint error / test failure / flake on sight, whoever caused it,
+*      folded into the current work rather than derailing the user's task (the
+*      scope guardrail keeps proactive quality from becoming yak-shaving). The
+*      digest carries a one-line form; the full statement lives here so it does
+*      not cost the context window every turn.
+*
+* Self-referentially compliant with the style directive: no em dashes, no
+* Claude / Anthropic attribution.
+*
+* Availability-aware: four of the natives (`scout`, `implementer-fast`,
+* `reviewer-fast`, and `general-purpose-fast`) are DROPPED rather than
+* downgraded when no model in
+* their chain resolves, so naming them unconditionally here would tell the lead to delegate
+* to an agent that has no `.md` file and is absent from the Task
+* `subagent_type` enum. Build the directive with
+* `buildOperatingDefaultsDirective` and the same availability booleans used for
+* the `.md` generation and the awareness snippet; the exported const below is
+* the all-available form, kept for callers and tests that do not model a thin
+* catalog.
+*/
+/**
+* Pipeline skills (`/gh-gather-context`, `/gh-plan`, `/gh-implement`,
+* `/gh-swe-pipeline`) injected ONLY for `--swe` launches on pinned profiles
+* (fast, max, cheap, cheap1m, cheapest, balanced). Standard is intentionally
+* excluded. Without `--swe` the skill files are not written and this text is
+* not referenced. Stages dispatch ONLY native subagents present on the
+* profile roster (Explore, Plan, General-Purpose, reviewer, implementer
+* where provided), never worker-* MCP dispatchers. All roles run at the
+* 200K default window (bare slugs, no 1M accounting) with advisory budgets:
+* gather ~3 min per round (3 rounds max, 6 Explore per round); plan ~5 min
+* via the profile-pinned Plan subagent (trivial asks exit planless);
+* implement ~10 min per task (8 concurrent max, worktree:true only when
+* parallel tasks need isolation); reviewer only on low-confidence or complex
+* and risky changes, plus a General-Purpose fix pass for major reviewer
+* findings.
+*/
+const PIPELINE_SKILLS_AWARENESS = "Pipeline skills (all 200K default context, native subagents only, never worker-*). Prefer `/gh-swe-pipeline`: strict sequence, each stage completing before the next starts, user approval before implementation. Stages in order: (1) `/gh-gather-context` BEFORE planning when grounded context is needed: lexical search plus bounded Explore subagents (~3 min each, 3 rounds max), writes context.md plus context.compact.md; (2) `/gh-plan` AFTER context and BEFORE implementation: native Plan subagent plans non-trivial asks (trivial exits planless), ordered plan.md (~5 min), open questions, waits for user approval; (3) `/gh-implement` AFTER plan approval: bounded parallel General-Purpose subagents (implementer first on max; worktree:true if parallel tasks need isolation), reviewer only on low-confidence or risky changes, plus fix pass for major findings. Skip for trivial work. Never implement without an approved plan. Never overlap stages.";
 /** Oxford-comma join: "a", "a and b", "a, b, and c". */
 function joinClauses(parts) {
 	if (parts.length <= 1) return parts[0] ?? "";
@@ -2901,7 +3213,8 @@ function buildOperatingDefaultsDirective(opts = {}) {
 	if (opts.profile === "max") {
 		const peersKey = opts.peersKey ?? opts.groupKeys?.peers ?? "peers";
 		const artifactClause = opts.artifactAvailable ? ` Live human review is available in the artifact panel via \`mcp__${peersKey}__artifact_*\`.` : "";
-		return "## Operating defaults (these layer with the user's explicit direction and the domain's own standards as addons, not replacements: follow all three together; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\nMax launch profile. The lead owns the outcome. Start with direct repository or runtime evidence. Handle narrow, obvious, surgical, and single-command work directly; delegate a bounded workstream when it is broad, slow, context-heavy, or benefits from a genuinely independent perspective. " + MAX_PARALLELISM_RULE + " Brief each role with the desired outcome, relevant context, constraints, expected evidence, and verification. Use the roster as complementary capabilities, never as a required Explore → Plan → implement → review sequence. Avoid overlapping assignments and do not ask several models the same generic question. Synthesize results against the repository and executable checks: model agreement is not verification. Use one fresh-context peer only when a consequential judgment remains after direct checks; use the coordinator only when several distinct lenses could change the decision. Advisor is optional, non-binding counsel for one focused consequential uncertainty that evidence and the appropriate roles cannot settle; it has no approval or workflow authority, and a further consultation requires materially new or conflicting evidence." + artifactClause + "\n\nPipeline skills (all 200K default context). For non-trivial changes, run in order: (1) `/gh-gather-context` BEFORE planning when grounded context is needed: it decomposes the ask, runs lexical search, fans out to bounded Luna-high explore workers, and writes context.md plus context.compact.md; (2) `/gh-plan` AFTER context and BEFORE implementation: it ingests the context brief with Sol-medium, produces a scoped modular ordered plan.md with explicit tasks for Luna workers, surfaces open questions, and waits for user approval; (3) `/gh-implement` AFTER plan approval: it runs bounded parallel Luna-max task workers in isolated worktrees (each self-tests and self-reviews), aggregates a unified diff, and runs staged review (Luna max, then Sol medium for major issues only). Skip the pipeline for trivial surgical work. Never implement without an approved plan.";
+		const pipelineClause = opts.sweEnabled === false ? "" : `\n\n${PIPELINE_SKILLS_AWARENESS}`;
+		return "## Operating defaults (these layer with the user's explicit direction and the domain's own standards as addons, not replacements: follow all three together; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\nMax launch profile. The lead owns the outcome. Start with direct repository or runtime evidence. Handle narrow, obvious, surgical, and single-command work directly; delegate a bounded workstream when it is broad, slow, context-heavy, or benefits from a genuinely independent perspective. " + MAX_PARALLELISM_RULE + " Brief each role with the desired outcome, relevant context, constraints, expected evidence, and verification. Use the roster as complementary capabilities, never as a required Explore → Plan → implement → review sequence. Avoid overlapping assignments and do not ask several models the same generic question. Synthesize results against the repository and executable checks: model agreement is not verification. Use one fresh-context peer only when a consequential judgment remains after direct checks; use the coordinator only when several distinct lenses could change the decision. Advisor is optional, non-binding counsel for one focused consequential uncertainty that evidence and the appropriate roles cannot settle; it has no approval or workflow authority, and a further consultation requires materially new or conflicting evidence." + artifactClause + pipelineClause;
 	}
 	if (opts.profile === "fast" || opts.profile === "cheap" || opts.profile === "cheap1m" || opts.profile === "cheapest" || opts.profile === "balanced") {
 		const isCheap = opts.profile === "cheap" || opts.profile === "cheap1m";
@@ -2922,9 +3235,9 @@ ${profileLabel} profile runtime wiring is unavailable. Work directly, use only t
 		const workerBrowseClause = opts.browseAvailable ? ` \`worker-browse\` runs delegated autonomous browsing tasks through \`mcp__${workersKey}__browse\`.` : "";
 		const artifactClause = opts.artifactAvailable ? ` \`mcp__${peersKey}__artifact_*\` provides human review in the artifact panel with auto-open on plan completion.` : "";
 		const astraClause = opts.astraAvailable && (opts.profile === "fast" || opts.profile === "cheap1m") ? ` \`mcp__${peersKey}__astra\` (GPT-6 Astra ${astraDescriptor}) is the terminal escalation consultant for the lead only, reserved strictly for the hardest dead ends when direct evidence, Advisor, and Oracle have all failed to produce a defensible path (consulted at most 1-2 times per decision with concise context and specific questions).` : "";
-		return "## Operating defaults (these layer with the user's explicit direction and the domain's own standards as addons, not replacements: follow all three together; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\n" + (isCheapest ? `${profileLabel} launch profile. The lead owns the outcome and handles straightforward work directly. ` + buildNativeReachClauses(opts) + ". Handle trivial, surgical, single-file, or single-command tasks directly; you do not need to justify skipping delegation. `Explore` may be used for discovery spanning more than a couple of files; `Plan` for sequencing with complex interfaces or acceptance criteria; `General-Purpose` for mixed multi-step execution; `reviewer` for behavior-changing or risk-sensitive changes. Delegation graph: the lead may invoke all four; `Plan` may invoke `Explore` and `reviewer`; `General-Purpose` may invoke `reviewer`; `Explore`, `reviewer`, and `worker-browse` cannot invoke native subagents.\n\n" : `${profileLabel} launch profile. The lead coordinates execution across specialized native roles: ` + buildNativeReachClauses(opts) + ". In plan mode or when designing changes with complex sequencing, interface contracts, or acceptance criteria, delegate architectural planning to `Plan` (in plan mode, produce the plan and acceptance criteria; do not edit files). Phase pipeline (budget gather, expensive plan, budget execution, expensive verification). GATHER: delegate to `Explore` instead of exploring yourself. For any question spanning more than a couple of files, launch one or more `Explore` subagents in parallel with scoped evidence questions and let them return file:line citations; read directly only the small subset you must touch to decide or edit. `Plan` follows the same rule when it needs repository facts. PLAN: `Plan` produces handoff-ready steps (ordered, file:line, done conditions, acceptance criteria) for a `General-Purpose` executor that cannot see its reasoning; `Plan` may consult Oracle on unresolved trade-offs and reports any remaining gap to the lead. EXECUTE: delegate mixed multi-step work and Plan handoffs to `General-Purpose` in a fresh context to preserve lead context; brief with outcome, constraints, files in scope, and verification. VERIFY: after behavior-changing, cross-boundary, or risk-sensitive implementation, run relevant build/tests then invoke `reviewer` before declaring done. Handle trivial, surgical, single-file, or single-command tasks directly; you do not need to justify skipping delegation. `Explore` is cheap and may be launched in parallel across independent discovery questions. Send independent subagent calls in parallel within a single turn. Delegation graph: the lead may invoke all four; `Plan` may invoke `Explore` and `reviewer`; `General-Purpose` may invoke `reviewer`; `Explore`, `reviewer`, and `worker-browse` cannot invoke native subagents.\n\n") + `Consultation guidance: Follow an evidence-first escalation ladder. Direct empirical evidence (search, code, tests, builds) settles factual questions first. Advisor is an optional, non-binding, lead-only transcript-aware sounding board for trajectory guidance or framing checks (direction, not dictation), and never use it for routine progress, waiting, directly verifiable facts, or completion ritual. \`mcp__${peersKey}__oracle\` is ${oracleDescriptor}, an expert consultant available to the lead and \`Plan\`, preferred over advisor for difficult conceptual, algorithmic, spec/protocol, or architectural tradeoffs evaluated in a self-contained brief; \`reviewer\` and other subagents cannot call Oracle. \`Plan\` may consult Oracle on unresolved trade-offs, and reports any remaining tie-breaking gap to the lead.${astraClause} ` + searchGuidance + `\`mcp__${searchKey}__web\` provides citable sources.${browserClause}${workerBrowseClause}${artifactClause}\n\nPipeline skills (all 200K default context). For non-trivial changes, run in order: (1) \`/gh-gather-context\` BEFORE planning when grounded context is needed: it decomposes the ask, runs lexical search, fans out to bounded Luna-high explore workers, and writes context.md plus context.compact.md; (2) \`/gh-plan\` AFTER context and BEFORE implementation: it ingests the context brief with Sol-medium, produces a scoped modular ordered plan.md with explicit tasks for Luna workers, surfaces open questions, and waits for user approval; (3) \`/gh-implement\` AFTER plan approval: it runs bounded parallel Luna-max task workers in isolated worktrees (each self-tests and self-reviews), aggregates a unified diff, and runs staged review (Luna max, then Sol medium for major issues only). Skip the pipeline for trivial surgical work. Never implement without an approved plan.
-
-Verify claims with concrete repository evidence and tests before declaring work done. User instructions outrank delegation triggers. Stop named teammates when finished.`;
+		const pipeline = isCheapest ? `${profileLabel} launch profile. The lead owns the outcome and handles straightforward work directly. ` + buildNativeReachClauses(opts) + ". Handle trivial, surgical, single-file, or single-command tasks directly; you do not need to justify skipping delegation. `Explore` may be used for discovery spanning more than a couple of files; `Plan` for sequencing with complex interfaces or acceptance criteria; `General-Purpose` for mixed multi-step execution; `reviewer` for behavior-changing or risk-sensitive changes. Delegation graph: the lead may invoke all four; `Plan` may invoke `Explore` and `reviewer`; `General-Purpose` may invoke `reviewer`; `Explore`, `reviewer`, and `worker-browse` cannot invoke native subagents.\n\n" : `${profileLabel} launch profile. The lead coordinates execution across specialized native roles: ` + buildNativeReachClauses(opts) + ". In plan mode or when designing changes with complex sequencing, interface contracts, or acceptance criteria, delegate architectural planning to `Plan` (in plan mode, produce the plan and acceptance criteria; do not edit files). Phase pipeline (budget gather, expensive plan, budget execution, expensive verification). GATHER: delegate to `Explore` instead of exploring yourself. For any question spanning more than a couple of files, launch one or more `Explore` subagents in parallel with scoped evidence questions and let them return file:line citations; read directly only the small subset you must touch to decide or edit. `Plan` follows the same rule when it needs repository facts. PLAN: `Plan` produces handoff-ready steps (ordered, file:line, done conditions, acceptance criteria) for a `General-Purpose` executor that cannot see its reasoning; `Plan` may consult Oracle on unresolved trade-offs and reports any remaining gap to the lead. EXECUTE: delegate mixed multi-step work and Plan handoffs to `General-Purpose` in a fresh context to preserve lead context; brief with outcome, constraints, files in scope, and verification. VERIFY: after behavior-changing, cross-boundary, or risk-sensitive implementation, run relevant build/tests then invoke `reviewer` before declaring done. Handle trivial, surgical, single-file, or single-command tasks directly; you do not need to justify skipping delegation. `Explore` is cheap and may be launched in parallel across independent discovery questions. Send independent subagent calls in parallel within a single turn. Delegation graph: the lead may invoke all four; `Plan` may invoke `Explore` and `reviewer`; `General-Purpose` may invoke `reviewer`; `Explore`, `reviewer`, and `worker-browse` cannot invoke native subagents.\n\n";
+		const swePipelineClause = opts.sweEnabled === false ? "" : `${PIPELINE_SKILLS_AWARENESS}\n\n`;
+		return "## Operating defaults (these layer with the user's explicit direction and the domain's own standards as addons, not replacements: follow all three together; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\n" + pipeline + `Consultation guidance: Follow an evidence-first escalation ladder. Direct empirical evidence (search, code, tests, builds) settles factual questions first. Advisor is an optional, non-binding, lead-only transcript-aware sounding board for trajectory guidance or framing checks (direction, not dictation), and never use it for routine progress, waiting, directly verifiable facts, or completion ritual. \`mcp__${peersKey}__oracle\` is ${oracleDescriptor}, an expert consultant available to the lead and \`Plan\`, preferred over advisor for difficult conceptual, algorithmic, spec/protocol, or architectural tradeoffs evaluated in a self-contained brief; \`reviewer\` and other subagents cannot call Oracle. \`Plan\` may consult Oracle on unresolved trade-offs, and reports any remaining tie-breaking gap to the lead.${astraClause} ` + searchGuidance + `\`mcp__${searchKey}__web\` provides citable sources.${browserClause}${workerBrowseClause}${artifactClause}\n\n` + swePipelineClause + "Verify claims with concrete repository evidence and tests before declaring work done. User instructions outrank delegation triggers. Stop named teammates when finished.";
 	}
 	return "## Operating defaults (these layer with the user's explicit direction and the domain's own standards as addons, not replacements: follow all three together; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\nOrchestrate. Delegate research, implementation, review, and large reads to the right subagent, worker, or model. Reach for " + buildNativeReachClauses(opts) + "; worker-* agents for background non-blocking runs; Task subagents for parallel work; peer critics for review. That keeps your own context free to reason and collaborate with the user. Launch independent agents concurrently in a single message rather than serially. Delegation pays when the work is WIDE (many files or sources to sweep) or SLOW, and you need only the conclusion: the main thread is where you think with and respond to the user, and its context window is a finite shared resource. It does NOT pay merely because a sub-question is separable. A narrow, deep question whose whole value is file:line fidelity loses exactly that through a summarization layer, and a sub-question you could answer in one command is cheaper done directly than paying a subagent's startup. Do trivial, surgical, and last-mile work yourself. A named teammate persists after it reports so you can send it follow-ups, and nothing reaps it for you: its idle notice means available, not finished. Stop it once you are done with it.\n\nAdversarial review. The peer critics (`codex_critic` and `codex_reviewer`, `gemini_critic` and `gemini_reviewer`, `opus_critic`, and the `peer-review-coordinator` that fans out to several of them) are fresh-context models, so what they add is a blind spot that whoever produced the work cannot reach by thinking harder about it; prefer a critic from a different lab than the producer, since blind spots correlate within a lab. The `advisor` is a complement and not a substitute: it sees your transcript, so it catches your own drift and momentum, but it inherits your framing, which is exactly what a fresh-context critic does not. They earn their keep on consequential design choices, recommendations, and hard-to-reverse decisions: the cases where plausible alternatives remain and the conclusion rests on judgment rather than on something you can verify directly. That is where confabulation hides, so budget the wait even under delivery pressure. Always consult one when the change touches auth, user input, database queries, crypto, or serialization. They do NOT pay for read-only tracing, ordinary repository lookup, or a conclusion that a focused test, a direct reproduction, or unambiguous code evidence already settles. Asking a critic to re-derive a proven fact returns a confident answer either way, which is ritual skepticism rather than review, and skipping them there is the right call and not a shortcut. Match the lens to the artifact: a strategic critic for plans and trade-offs, a code reviewer for a concrete diff, the coordinator only when the risk warrants several independent lenses. Give whichever you pick the artifact and the constraints and not your rationale, since justification anchors the review and dulls it.\n\nAim high. Default to radical simplicity and a relentless focus on the user's real experience: design for the person and the job to be done, not the demo. Reason about the whole system from first principles, anticipating scale and the long arc rather than patching the surface. Work backwards from the outcome the user actually needs. Question every assumption and prefer what you can derive, reproduce, or test.\n\nEngineering excellence. When making technical decisions, give little weight to development cost; prefer quality, simplicity, robustness, scalability, and long-term maintainability. Fix a bug by first reproducing it end to end, as close to how a real user hits it as you can, so you solve the real problem and not a symptom. When testing a product end to end, be picky about the UI and obsessed with pixel perfection: if something clearly looks off, even when it is unrelated to your task, get it fixed along the way. Hold that same bar for the codebase itself: a lint error, a failing test, or a flaky test is worth fixing the moment you see it, whoever introduced it. Fold it into your current work rather than letting it derail the task the user actually asked for.";
 }
@@ -2935,7 +3248,8 @@ Verify claims with concrete repository evidence and tests before declaring work
 const OPERATING_DEFAULTS_DIRECTIVE = buildOperatingDefaultsDirective();
 const STANDARD_OPERATING_DEFAULTS_DIGEST = "## Operating defaults (these layer with the user's direction and the domain's standards as addons: follow all three; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\nDelegate when the work is WIDE (many files or sources to sweep) or SLOW and you need only the conclusion, to protect the main thread's finite context and keep it free for reasoning and interacting with the user; prefer parallel delegation for independent work. Do NOT delegate merely because a sub-question is separable: a narrow, deep question whose value is file:line fidelity loses exactly that through a summarization layer, and one answerable in a single command is cheaper done directly. Do trivial, surgical, and last-mile work yourself. Stop a named teammate once you are done with it: it persists for follow-ups, its idle notice means available rather than finished, and nothing reaps it for you.\n\nVerify, do not assert. Run the code, read the file, check the exit code. A claim in prose is worth nothing against state you did not check, and a check that cannot fail proves nothing. Reproduce a bug end to end, the way a real user hits it, before fixing it. Fix a lint error, failing test, or flake the moment you see it, whoever introduced it, without letting it derail the task at hand. Prefer quality and long-term maintainability over development cost.\n\nVerification has a blind spot: a consequential recommendation, a design or trade-off call, or a hard-to-reverse decision that still turns on judgment among plausible alternatives once the direct evidence is in. That is where confabulation hides, so put it past a peer critic before you ship it and budget the wait even under delivery pressure. When a test, a run, a reproduction, or a search would settle the claim, settle it that way instead; a critic asked to re-derive what you can already prove is ritual, not review.\n\nThe agent roster, the tool surface, and the reasoning behind these defaults are in your CLAUDE.md project instructions. Read them when choosing HOW to work; the rules above apply without a lookup.";
 function buildOperatingDefaultsDigest(opts = {}) {
-	if (opts.profile === "max") return "## Operating defaults (these layer with the user's direction and the domain's standards as addons: follow all three; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\nMax launch profile. The lead owns the outcome. Start with direct repository or runtime evidence. Do narrow, obvious, surgical, and single-command work directly; delegate bounded work that is broad, slow, context-heavy, or independently valuable. " + MAX_PARALLELISM_RULE + " Give delegated workstreams non-overlapping scopes and state the outcome, constraints, evidence, and verification expected.\n\nPipeline skills (all 200K default): `/gh-gather-context` before planning when context is needed, `/gh-plan` before implementation (waits for user approval), `/gh-implement` after approval with bounded parallel workers and staged review. Skip for trivial work.\n\nSynthesize and verify: run the code, inspect outputs, and check tests. Agent count and agreement are not evidence. Use a fresh-context peer only for consequential judgment that remains after direct checks, and use the coordinator only when several distinct lenses could change the decision. Advisor is optional, non-binding, primary-lead-only counsel for one focused consequential uncertainty; it is not an approval or completion gate.";
+	const digestPipelineSentence = opts.sweEnabled === false ? "" : "Pipeline skills (all 200K default, native subagents only): `/gh-gather-context` before planning when context is needed, `/gh-plan` before implementation (trivial exits planless, waits for user approval), `/gh-implement` after approval with parallel subagents and conditional reviewer. Skip for trivial work.\n\n";
+	if (opts.profile === "max") return "## Operating defaults (these layer with the user's direction and the domain's standards as addons: follow all three; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\nMax launch profile. The lead owns the outcome. Start with direct repository or runtime evidence. Do narrow, obvious, surgical, and single-command work directly; delegate bounded work that is broad, slow, context-heavy, or independently valuable. " + MAX_PARALLELISM_RULE + " Give delegated workstreams non-overlapping scopes and state the outcome, constraints, evidence, and verification expected.\n\n" + digestPipelineSentence + "Synthesize and verify: run the code, inspect outputs, and check tests. Agent count and agreement are not evidence. Use a fresh-context peer only for consequential judgment that remains after direct checks, and use the coordinator only when several distinct lenses could change the decision. Advisor is optional, non-binding, primary-lead-only counsel for one focused consequential uncertainty; it is not an approval or completion gate.";
 	if (opts.profile === "fast" || opts.profile === "cheap" || opts.profile === "cheap1m" || opts.profile === "cheapest" || opts.profile === "balanced") {
 		const isCheap = opts.profile === "cheap" || opts.profile === "cheap1m";
 		const isCheapest = opts.profile === "cheapest";
@@ -2944,7 +3258,7 @@ function buildOperatingDefaultsDigest(opts = {}) {
 		const oracleDescriptor = isCheapest ? "(GPT-5.6 Sol 200K/high, lead and Plan)" : isCheap || isBalanced ? "(Grok 4.6 200K/medium, lead and Plan)" : "(Opus 5 1M/high, lead and Plan)";
 		const advisorDescriptor = isCheapest ? "(Gemini/high, lead-only)" : "(Sol/high, lead-only)";
 		const astraStep = opts.astraAvailable && (opts.profile === "fast" || opts.profile === "cheap1m") ? `; (4) \`astra\` (GPT-6 Astra 200K/${isCheap ? "medium" : "high"}, lead-only) only as a last resort when direct evidence, Advisor, and Oracle cannot produce a defensible path (at most 1-2 calls per decision).` : ".";
-		return "## Operating defaults (these layer with the user's direction and the domain's standards as addons: follow all three; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\n" + (isCheapest ? `${profileLabel} launch profile. The lead owns the outcome and handles straightforward work directly: use \`Explore\` for discovery spanning more than a couple of files, \`Plan\` in plan mode or for complex sequencing, \`General-Purpose\` for mixed multi-step execution, and \`reviewer\` for behavior-changing or risk-sensitive changes. Handle trivial and surgical edits directly. Stop named teammates when finished.\n\n` : `${profileLabel} launch profile. The lead coordinates execution across specialized roles: delegate broad discovery to \`Explore\` in parallel and do not sweep the repo yourself (read directly only files you will act on); delegate to \`Plan\` in plan mode or when structuring complex multi-step sequencing (\`Plan\` is an advisory planning capability, not an approval gate, and writes handoff-ready steps for \`General-Purpose\`); delegate mixed multi-step execution and Plan handoffs to \`General-Purpose\` in a fresh context; delegate to \`reviewer\` after behavior-changing or risk-sensitive implementation to verify correctness before declaring done; handle trivial and surgical edits directly. Send independent subagent calls in parallel within a single turn. Stop named teammates when finished.\n\n`) + "Pipeline skills (all 200K default): `/gh-gather-context` before planning when context is needed, `/gh-plan` before implementation (waits for user approval), `/gh-implement` after approval with bounded parallel workers and staged review. Skip for trivial work.\n\nVerify claims against real evidence: run relevant commands and tests. Follow a disciplined consultation ladder for unresolved decisions: (1) direct code inspection, search, builds, and tests settle factual questions; (2) `advisor` " + advisorDescriptor + " for transcript-aware framing checks or trajectory guidance; (3) `oracle` " + oracleDescriptor + " for self-contained technical/architectural trade-offs" + astraStep;
+		return "## Operating defaults (these layer with the user's direction and the domain's standards as addons: follow all three; on a direct conflict the user's direction wins, then the domain standard, then the default below)\n\n" + (isCheapest ? `${profileLabel} launch profile. The lead owns the outcome and handles straightforward work directly: use \`Explore\` for discovery spanning more than a couple of files, \`Plan\` in plan mode or for complex sequencing, \`General-Purpose\` for mixed multi-step execution, and \`reviewer\` for behavior-changing or risk-sensitive changes. Handle trivial and surgical edits directly. Stop named teammates when finished.\n\n` : `${profileLabel} launch profile. The lead coordinates execution across specialized roles: delegate broad discovery to \`Explore\` in parallel and do not sweep the repo yourself (read directly only files you will act on); delegate to \`Plan\` in plan mode or when structuring complex multi-step sequencing (\`Plan\` is an advisory planning capability, not an approval gate, and writes handoff-ready steps for \`General-Purpose\`); delegate mixed multi-step execution and Plan handoffs to \`General-Purpose\` in a fresh context; delegate to \`reviewer\` after behavior-changing or risk-sensitive implementation to verify correctness before declaring done; handle trivial and surgical edits directly. Send independent subagent calls in parallel within a single turn. Stop named teammates when finished.\n\n`) + digestPipelineSentence + "Verify claims against real evidence: run relevant commands and tests. Follow a disciplined consultation ladder for unresolved decisions: (1) direct code inspection, search, builds, and tests settle factual questions; (2) `advisor` " + advisorDescriptor + " for transcript-aware framing checks or trajectory guidance; (3) `oracle` " + oracleDescriptor + " for self-contained technical/architectural trade-offs" + astraStep;
 	}
 	return STANDARD_OPERATING_DEFAULTS_DIGEST;
 }
@@ -3410,14 +3724,21 @@ async function writeInjectedSkill(name, md) {
 * Injected-skill registry: the floor-raising / controller skills the `claude`
 * launcher materializes into the per-launch `CLAUDE_CONFIG_DIR` mirror so the
 * spawned Claude Code session discovers them (`/gh-research`,
-* `/gh-orchestrate`, `/gh-floor-keeper`, `/gh-first-mate`). See
-* `docs/floor-raising-agent-surface.md`.
+* `/gh-orchestrate`, `/gh-floor-keeper`, `/gh-first-mate`, plus the `--swe`
+* pipeline skills `/gh-gather-context`, `/gh-plan`, `/gh-implement`,
+* `/gh-swe-pipeline`). See `docs/floor-raising-agent-surface.md`.
+*/
+/**
+* Pipeline skills for `--swe` launches on pinned profiles (all 200K default
+* context). The orchestrator (`/gh-swe-pipeline`) runs the other three in
+* strict sequence; the three stages stay individually invokable for users who
+* only want one stage.
 */
-/** Pipeline skills for pinned profiles (all 200K default context). */
 const PIPELINE_SKILLS = [
 	GATHER_CONTEXT_SKILL,
 	PLAN_SKILL,
-	IMPLEMENT_SKILL
+	IMPLEMENT_SKILL,
+	SWE_PIPELINE_SKILL
 ];
 /** All injected skills, in dependency order (research underpins the others). */
 const INJECTED_SKILLS = [
@@ -3435,6 +3756,10 @@ const INJECTED_SKILLS = [
 ];
 function injectedSkillsForLaunch(selection) {
 	if (isPipelineSkillProfile(selection.profileId)) {
+		if (!selection.sweEnabled) {
+			if (selection.profileId === "max" && selection.firstMateEnabled) return INJECTED_SKILLS.filter((skill) => skill.name.startsWith("gh-first-mate"));
+			return [];
+		}
 		if (selection.profileId === "max") {
 			const pipeline = PIPELINE_SKILLS.slice();
 			if (selection.firstMateEnabled) return [...pipeline, ...INJECTED_SKILLS.filter((skill) => skill.name.startsWith("gh-first-mate"))];
@@ -3512,4 +3837,4 @@ async function injectAttributionSuppressionIntoSettingsFile(settingsPath) {
 //#endregion
 export { writePeerMcpRuntimeFiles as C, workersKeyOf as S, sanitizeServeSettingsEnv as _, appendPeerAwarenessToMirroredClaudeMd as a, resolveCodexCliBackend as b, buildOperatingDefaultsDirective as c, prependStyleDirectiveToMirroredClaudeMd as d, buildArtifactReviewSkill as f, planModeAllowRules as g, injectAllowRules as h, writeInjectedSkill as i, prependArtifactPanelDirectiveToMirroredClaudeMd as l, configureServeDefaultPermissionMode as m, INJECTED_SKILLS as n, appendToolbeltAwarenessToMirroredClaudeMd as o, SEAMLESS_BUILTIN_TOOLS as p, injectedSkillsForLaunch as r, buildOperatingDefaultsDigest as s, injectAttributionSuppressionIntoSettingsFile as t, prependOperatingDefaultsToMirroredClaudeMd as u, BUILTIN_SUBAGENT_DEFINITIONS as v, resolveGroupKeysFromMirror as x, injectPeerMcpIntoMirror as y };
 
-//# sourceMappingURL=attribution-settings-sTUXqFzx.js.map
+//# sourceMappingURL=attribution-settings-17Ug_BaA.js.map