opencode-swarm 7.125.5 → 7.126.0

package/.opencode/skills/brainstorm/SKILL.md

@@ -57,6 +57,7 @@ If `council.general.enabled` is true in the resolved opencode-swarm config AND a
     - **Important:** If research is ongoing, apply a fixed 5-minute protocol budget to `research_needed`. If research does not complete before the budget expires, automatically reclassify the item to `user_decision` with a note that research was incomplete, then surface it to the user. This prevents the clarification funnel from stalling while waiting for external research.
 - Cross-reference design sections by name where relevant context helps (but keep HOW out of the spec).
 - Delegate to `the active swarm's reviewer agent` for an independent review of the draft spec. Reviewer must flag: requirements that encode HOW, untestable requirements, missing edge cases, silent assumptions.
+    → REQUIRED: The reviewer Task dispatch MUST contain a literal `ACCEPTANCE:` line. This is a pre-plan spec review (no fr_refs yet), so resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt using a one-line task-derived DONE restatement, e.g. "DONE = reviewer flags HOW-encoded requirements, untestable requirements, missing edge cases, and silent assumptions in the draft spec." A missing line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED.
 - Apply reviewer feedback. If reviewer rejects, iterate once and re-review. After two rounds, surface remaining disagreements to the user.
 - Before writing `.swarm/spec.md`, apply the FR-002 non-shadowing check: if a non-native spec already exists, do not shadow it (see MODE: SPECIFY step 1b).
 - Write the final spec to `.swarm/spec.md`.
@@ -73,24 +74,28 @@ until PLAN; MODE: PLAN will choose safe parallelism automatically. Keep commit
 frequency at phase-level only.
 Now ask the user which QA gates to enable for this plan, how many parallel coders to use, the commit frequency, and auto_proceed -- do not select on their behalf. Present all four items together as one unified exchange.
 
+<!-- BEGIN QA_GATE_BODY -->
+
 Present the eleven gates with their defaults (DEFAULT_QA_GATES), parallel coder count, commit frequency, and auto_proceed as a single user-facing section. Offer the user a one-shot choice: accept defaults, or customize. The eleven gates are:
-- reviewer (default: ON) -- code review of coder output
-- test_engineer (default: ON) -- test verification of coder output
-- sme_enabled (default: ON) -- SME consultation during planning/clarification
-- critic_pre_plan (default: ON) -- critic review before plan finalization
-- sast_enabled (default: ON) -- static security scanning
-- council_mode (default: OFF) -- replaces per-task Stage B (reviewer + test_engineer) with the full 5-member council (critic, reviewer, sme, test_engineer, explorer). Requires council.enabled: true in config. (recommended for high-impact architecture, public APIs, schema/data mutation, security-sensitive code)
-- hallucination_guard (default: OFF) -- when enabled, mandatory per-phase API/signature/claim/citation verification via critic_hallucination_verifier at PHASE-WRAP; phase_complete will REJECT phase completion unless .swarm/evidence/{phase}/hallucination-guard.json exists with an APPROVED verdict (recommended for claim-heavy or research-heavy work)
-- mutation_test (default: OFF) -- when enabled, runs mutation testing on source files touched this phase via generate_mutants + mutation_test + write_mutation_evidence at PHASE-WRAP; FAIL verdict blocks phase_complete; WARN is non-blocking (recommended for projects with coverage gaps or safety-critical code)
-- phase_council (default: OFF) -- full 5-member council reviews all work in a phase holistically at phase_complete time. Requires council.enabled: true in config. (recommended for multi-task phases with cross-cutting concerns or high-risk integration)
-- drift_check (default: ON) -- when enabled, mandatory per-phase drift verification via critic_drift_verifier at PHASE-WRAP; compares implemented changes against spec.md intent; hard-blocks phase_complete when spec.md exists and drift evidence is missing or REJECTED; advisory-only when no spec.md exists (recommended for all projects with a specification)
-- final_council (default: OFF) -- when enabled, after all phases complete the architect dispatches the full 5-member council (critic, reviewer, sme, test_engineer, explorer) -- NOT the General Council -- at project scope, collects `CouncilMemberVerdict` objects, and calls `write_final_council_evidence`. This does not require `council.general.enabled`.
+- reviewer (default: ON) - code review of coder output
+- test_engineer (default: ON) - test verification of coder output
+- sme_enabled (default: ON) - SME consultation during planning/clarification
+- critic_pre_plan (default: ON) - critic review before plan finalization
+- sast_enabled (default: ON) - static security scanning
+- council_mode (default: OFF) - replaces per-task Stage B (reviewer + test_engineer) with the full 5-member council (critic, reviewer, sme, test_engineer, explorer). Requires council.enabled: true in config.
+- hallucination_guard (default: OFF) - when enabled, mandatory per-phase API/signature/claim/citation verification at PHASE-WRAP; phase_complete will REJECT phase completion unless .swarm/evidence/{phase}/hallucination-guard.json exists with an APPROVED verdict.
+- mutation_test (default: OFF) - when enabled, runs mutation testing on source files touched this phase via generate_mutants + mutation_test + write_mutation_evidence at PHASE-WRAP; FAIL verdict blocks phase_complete; WARN is non-blocking.
+- phase_council (default: OFF) - full 5-member council reviews all work in a phase holistically at phase_complete time. Requires council.enabled: true in config.
+- drift_check (default: ON) - mandatory per-phase drift verification via critic_drift_verifier at PHASE-WRAP; hard-blocks phase_complete when spec.md exists and drift evidence is missing or REJECTED; advisory-only when no spec.md exists.
+- final_council (default: OFF) - when enabled, after all phases complete the architect dispatches the full 5-member council (critic, reviewer, sme, test_engineer, explorer) - NOT the General Council - at project scope, collects `CouncilMemberVerdict` objects, and calls `write_final_council_evidence`. This does not require `council.general.enabled`.
 
 Additionally, present these three sub-items as part of the same exchange:
-- Parallel coders (default: 1, range: 1-6) -- how many coders should run in parallel. Parallel coders each run in an isolated git worktree (separate working dir + branch) and merge back automatically, so they never overwrite each other's files -- safe and faster, but only for tasks whose file scopes do NOT overlap. The per-task file scopes that determine a safe parallel count are not known until the plan is finalized, so default to 1 (serial) here; the precise recommendation is made at plan time once the tasks and their scopes exist.
+- Parallel coders (default: 1, range: 1-6) - how many coders should run in parallel. Parallel coders each run in an isolated git worktree (separate working dir + branch) and merge back automatically, so they never overwrite each other's files - safe and faster, but only for tasks whose declared file scopes do NOT overlap. The per-task file scopes that determine a safe parallel count are not known until the plan is finalized, so default to 1 (serial) here; the precise recommendation is made at plan time once the tasks and their scopes exist.
   > COMMON MISCONCEPTION: worktree isolation is baseline for standard parallel coders, governed by the parallel execution profile plus top-level `worktree.policy`. It is not provided by Lean Turbo or Epic. Do not recommend Lean Turbo or Epic to obtain worktree isolation; recommend them only for what they add beyond baseline (Lean Turbo: lane planning, file locks, phase reviewer, integrated diff; Epic: co-change awareness and auto-decide). Worktrees also do not make overlapping scopes safe: dependency readiness, file-disjoint scopes, and merge-back ownership are still required.
-- Commit frequency (default: phase-level only) -- optional per-task checkpoint commit after each task completion.
-- auto_proceed (boolean, default: false) -- when true, auto-advance to the next phase without asking "Ready for Phase N+1?"; runtime toggle via /swarm auto-proceed on|off.
+- Commit frequency (default: phase-level only) - optional per-task checkpoint commit after each task completion.
+- auto_proceed (boolean, default: false) - when true, auto-advance to the next phase without asking "Ready for Phase N+1?"; runtime toggle via /swarm auto-proceed on|off.
+
+<!-- END QA_GATE_BODY -->
 
 The user answers all four items (gates, parallel coders, commit frequency, auto_proceed) in one exchange. Wait for the user's response.
 

package/.opencode/skills/execute/SKILL.md

@@ -38,6 +38,7 @@ TASK: Fix [gate name] failure
 FILE: [affected file(s)]
 INPUT: [exact error output from the gate]
 CONSTRAINT: Fix ONLY the reported issue, do not modify other code
+ACCEPTANCE: [resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt — REQUIRED on every coder/reviewer dispatch; a missing line is blocked by ACCEPTANCE_FIELD_REQUIRED. Copy the SAME ACCEPTANCE text used on the original coder dispatch for this task.]
 ✓ After coder returns, re-run the failed gate from the step that failed
 ✓ Print "Coder attempt [N/configured QA retry limit] on task [X.Y]"
 
@@ -56,6 +57,7 @@ All other gates: failure → return to coder. No self-fixes. No workarounds.
     → Subsequent `pre_check_batch` calls with `phase: <N>` will automatically diff against this baseline — only NEW findings (not in baseline) drive the fail verdict.
     -> PREFLIGHT CHECKLIST: Before first coder delegation, answer "SAST baseline captured before first coder delegation? yes/no/disabled/error". If the answer is no, do not delegate to coder; run 5b-BASE first. If disabled or error, record the exact tool result.
 5b. the active swarm's coder agent - Implement (if designer scaffold produced, include it as INPUT).
+    → REQUIRED: The coder Task dispatch MUST contain a literal `ACCEPTANCE:` line — resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt (verbatim FR/SC text when fr_refs is non-empty, otherwise a one-line task-derived DONE restatement). A missing line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED before the coder runs. Do NOT confuse the plan-task `acceptance` field with this per-dispatch header — both are required.
     → If this dispatch fails with `PLAN_CRITIC_GATE_VIOLATION`: the plan has no current critic-approved snapshot (commonly a plan approved before this mechanical gate existed). Do NOT retry the coder dispatch as-is — re-run MODE: CRITIC-GATE to get a fresh critic `APPROVED` verdict, then retry this step.
 5b-bis. **CODER OUTPUT VERIFICATION**: After the coder reports completion, do NOT accept the self-report alone. Run `diff` (step 5c) and inspect at least one of the modified files yourself to confirm the change exists. The coder may report DONE without having produced any diff. A 30-second read of the changed file(s) catches this failure mode. This is NOT a separate explorer dispatch — the existing `diff` tool at step 5c is the verification mechanism; the key discipline is checking that `diff` returns actual changes before proceeding, rather than forwarding the coder's self-report to the next gate.
 5c. Run `diff` tool. If `hasContractChanges` → the active swarm's explorer agent integration analysis. If COMPATIBILITY SIGNALS=INCOMPATIBLE or MIGRATION_SURFACE=yes → coder retry. If COMPATIBILITY SIGNALS=COMPATIBLE and MIGRATION_SURFACE=no → proceed.
@@ -105,6 +107,7 @@ Treating pre_check_batch as a substitute for the active swarm's reviewer agent i
     After Stage A (pre_check_batch) passes:
     1. Ensure `declare_council_criteria` was called for this task (prerequisite).
     2. Dispatch all 5 council members (critic, reviewer, sme, test_engineer, explorer) in PARALLEL with task-scoped context.
+       → REQUIRED: Any council member whose agent role is `coder` or `reviewer` MUST receive a Task prompt containing a literal `ACCEPTANCE:` line — resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt (same text as the coder delegation for this task). In the standard 5-member council only the reviewer member is gated (ACCEPTANCE_FIELD_REQUIRED); the wording covers coder too in case a future council profile includes one.
     3. Collect all 5 verdict objects. Do NOT fabricate or substitute verdicts.
     4. Call `submit_council_verdicts` with the collected verdicts.
     5. Act on the verdict: APPROVE → task passes. CONCERNS with `success: false` + `reason: 'blocking_concerns_unresolved'` → HIGH/CRITICAL findings are blocking, no evidence written, return to coder with requiredFixes and re-council after fixes. CONCERNS with `success: true` → only MEDIUM/LOW advisory findings, task passes. REJECT → return to coder with requiredFixes.
@@ -114,8 +117,10 @@ Treating pre_check_batch as a substitute for the active swarm's reviewer agent i
     For set-dispatch reviewer/test_engineer verdict rows that must be attributed to plan tasks, read `file:.swarm/bundled-skills/gate-attribution/SKILL.md`. Before re-dispatching a coder for a task that already has a lane (any prior dispatch status), read `file:.swarm/bundled-skills/worktree-retry-cleanup/SKILL.md`.
 
     5j. the active swarm's reviewer agent - General review. REJECTED before the configured QA retry limit → coder retry. REJECTED at the configured QA retry limit → escalate.
+    → REQUIRED: The reviewer Task dispatch MUST contain a literal `ACCEPTANCE:` line — same text as the coder delegation for this task. Resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt. A missing line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED.
     → REQUIRED: Print "reviewer: [APPROVED | REJECTED — reason]"
     5k. Security gate: if change matches TIER 3 criteria OR content contains SECURITY_KEYWORDS OR secretscan has ANY findings OR sast_scan has ANY findings at or above threshold → MUST delegate the active swarm's reviewer agent security-only review. REJECTED before the configured QA retry limit → coder retry. REJECTED at the configured QA retry limit → escalate to user.
+    → REQUIRED: The security-reviewer Task dispatch MUST contain a literal `ACCEPTANCE:` line — same text as the coder delegation for this task (the security review is still a reviewer dispatch; the gate does not exempt security-only reviews). Resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt. A missing line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED.
     → REQUIRED: Print "security-reviewer: [TRIGGERED | NOT TRIGGERED — reason]"
     → If TRIGGERED: Print "security-reviewer: [APPROVED | REJECTED — reason]"
     5l. the active swarm's test_engineer agent - Verification tests. FAIL → coder retry from 5g.

package/.opencode/skills/phase-wrap/SKILL.md

@@ -135,6 +135,7 @@ There is no project where code ships without review, tests, and required documen
    If `phase_council` is enabled:
    1. Build a PHASE DOSSIER from all completed tasks in this phase, their evidence artifacts, changed-file summaries, and any drift/hallucination/mutation evidence.
    2. Dispatch the full 5-member council (`the active swarm's critic agent`, `the active swarm's reviewer agent`, `the active swarm's sme agent`, `the active swarm's test_engineer agent`, and `the active swarm's explorer agent`) in PARALLEL with phase-scoped context. Each member reviews the entire phase's work holistically and returns a `CouncilMemberVerdict` JSON object.
+      → REQUIRED: The reviewer council member Task dispatch MUST contain a literal `ACCEPTANCE:` line — resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt (phase-scoped: concatenate the verbatim FR/SC text for every task in this phase when fr_refs is non-empty, otherwise a one-line phase-derived DONE restatement). A missing line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED. The other four members are not gated by this rule.
    3. Collect all 5 verdict objects. Do NOT fabricate or substitute verdicts.
    4. Act on the verdict: APPROVE → proceed. CONCERNS with `success: false` + `reason: 'blocking_concerns_unresolved'` → HIGH/CRITICAL findings are blocking, no evidence written, must resolve requiredFixes and re-council. CONCERNS with `success: true` → only MEDIUM/LOW advisory findings, phase may proceed per `phaseConcernsAllowComplete` flag. REJECT → surface required fixes to the user before proceeding.
    5. YOU (the architect) call the `submit_phase_council_verdicts` tool with the phase number and the collected council verdicts to persist the phase-council evidence. The council members do NOT write files — they are read-only. Only the `submit_phase_council_verdicts` tool writes `.swarm/evidence/{phase}/phase-council.json` (with plan binding, member verdicts, and quorum metadata). Do this BEFORE calling `phase_complete`.
@@ -144,6 +145,7 @@ There is no project where code ships without review, tests, and required documen
    If enabled AND this is the LAST phase in the plan (all other phases have status 'complete' and no more phases remain):
    1. Build a PROJECT DOSSIER from the completed plan, all phase summaries, changed-file summaries, and all relevant evidence artifacts. This is the full 5-member council (NOT the General Council) running a completed-project review.
    2. Dispatch the full 5-member council (`the active swarm's critic agent`, `the active swarm's reviewer agent`, `the active swarm's sme agent`, `the active swarm's test_engineer agent`, and `the active swarm's explorer agent`) in PARALLEL with project-scoped context. Each member must review the entire completed body of work and return a `CouncilMemberVerdict` JSON object using `agent`, `verdict` (APPROVE|CONCERNS|REJECT), `confidence`, `findings[]`, `criteriaAssessed[]`, `criteriaUnmet[]`, and `durationMs`.
+      → REQUIRED: The reviewer council member Task dispatch MUST contain a literal `ACCEPTANCE:` line — resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt (project-scoped: concatenate the verbatim FR/SC text across all phases, otherwise a one-line project-derived DONE restatement). A missing line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED. The other four members are not gated by this rule.
    3. Collect the five returned verdict objects. Do NOT fabricate, infer, or substitute verdicts. If a member does not return valid JSON, re-dispatch that member.
    4. Call `write_final_council_evidence` with `phase`, `projectSummary`, `roundNumber`, and the collected `verdicts` array. This writes `.swarm/evidence/final-council.json` with plan binding, member verdicts, and quorum metadata.
    ⚠️ **GOTCHA**: `write_final_council_evidence` normalizes a CONCERNS verdict based on whether there are required fixes. CONCERNS with `requiredFixes > 0` → the tool writes NO evidence file (early-return `blocking_concerns_unresolved`) and `phase_complete` then blocks on the MISSING `final-council.json`. CONCERNS with zero required fixes → the tool writes a `concerns` verdict which is NON-blocking (advisory warning only). So: you MUST address required fixes from a CONCERNS verdict and re-council, or you will block on a missing evidence file. (Note: the **phase-level** council's `phaseConcernsAllowComplete` flag makes CONCERNS advisory at phase scope; the final council does not have that flag.)

package/.opencode/skills/plan/SKILL.md

@@ -228,22 +228,28 @@ After `save_plan` succeeds, read `.swarm/context.md`:
 - If a `## Pending Parallelization Config` section also exists: parse the values and call `save_plan` again with `execution_profile` set to `{ parallelization_enabled: <parsed>, max_concurrent_tasks: <parsed>, council_parallel: false, locked: true }`. Then remove the section from context.md. If the plan already had `execution_profile.locked: true`, skip this step — the profile is already locked and immutable.
 - If a `## Task Completion Commit Policy` section exists: preserve it in `.swarm/context.md` (do NOT remove). This section is execution-time guidance for optional per-task checkpoint commits after `update_task_status(status="completed")`.
 - If no pending section exists, ask the user inline now. Present the eleven gates with their defaults (DEFAULT_QA_GATES), parallel coder count, commit frequency, and auto_proceed as a single user-facing section. Offer the user a one-shot choice: accept defaults, or customize. The eleven gates are:
-  - reviewer (default: ON) - code review of coder output
-  - test_engineer (default: ON) - test verification of coder output
-  - sme_enabled (default: ON) - SME consultation during planning/clarification
-  - critic_pre_plan (default: ON) - critic review before plan finalization
-  - sast_enabled (default: ON) - static security scanning
-  - council_mode (default: OFF) - replaces per-task Stage B (reviewer + test_engineer) with the full 5-member council (critic, reviewer, sme, test_engineer, explorer). Requires council.enabled: true in config.
-  - hallucination_guard (default: OFF) - mandatory per-phase API/signature/claim/citation verification at PHASE-WRAP
-  - mutation_test (default: OFF) - mutation testing on source files touched this phase at PHASE-WRAP
-  - phase_council (default: OFF) - full 5-member council reviews all work in a phase holistically at phase_complete time. Requires council.enabled: true in config.
-  - drift_check (default: ON) - mandatory per-phase drift verification at PHASE-WRAP
-  - final_council (default: OFF) - when enabled, after all phases complete the architect dispatches the full 5-member council (critic, reviewer, sme, test_engineer, explorer) -- NOT the General Council -- at project scope, collects `CouncilMemberVerdict` objects, and calls `write_final_council_evidence`. This does not require `council.general.enabled`.
-  Additionally, present these three sub-items as part of the same exchange:
-  - Parallel coders (default: 1, range: 1-6) - how many coders should run in parallel. Parallel coders each run in an isolated git worktree (separate working dir + branch) and merge back automatically, so they never overwrite each other's files - safe and faster, but only for tasks whose declared file scopes do NOT overlap. Inspect the plan and recommend a count equal to the number of dependency-ready, file-disjoint task groups (clamped 1-6); recommend 1 (serial) when scopes overlap or are unknown. State your recommendation and reasoning when you ask.
+  <!-- BEGIN QA_GATE_BODY -->
+
+Present the eleven gates with their defaults (DEFAULT_QA_GATES), parallel coder count, commit frequency, and auto_proceed as a single user-facing section. Offer the user a one-shot choice: accept defaults, or customize. The eleven gates are:
+- reviewer (default: ON) - code review of coder output
+- test_engineer (default: ON) - test verification of coder output
+- sme_enabled (default: ON) - SME consultation during planning/clarification
+- critic_pre_plan (default: ON) - critic review before plan finalization
+- sast_enabled (default: ON) - static security scanning
+- council_mode (default: OFF) - replaces per-task Stage B (reviewer + test_engineer) with the full 5-member council (critic, reviewer, sme, test_engineer, explorer). Requires council.enabled: true in config.
+- hallucination_guard (default: OFF) - when enabled, mandatory per-phase API/signature/claim/citation verification at PHASE-WRAP; phase_complete will REJECT phase completion unless .swarm/evidence/{phase}/hallucination-guard.json exists with an APPROVED verdict.
+- mutation_test (default: OFF) - when enabled, runs mutation testing on source files touched this phase via generate_mutants + mutation_test + write_mutation_evidence at PHASE-WRAP; FAIL verdict blocks phase_complete; WARN is non-blocking.
+- phase_council (default: OFF) - full 5-member council reviews all work in a phase holistically at phase_complete time. Requires council.enabled: true in config.
+- drift_check (default: ON) - mandatory per-phase drift verification via critic_drift_verifier at PHASE-WRAP; hard-blocks phase_complete when spec.md exists and drift evidence is missing or REJECTED; advisory-only when no spec.md exists.
+- final_council (default: OFF) - when enabled, after all phases complete the architect dispatches the full 5-member council (critic, reviewer, sme, test_engineer, explorer) - NOT the General Council - at project scope, collects `CouncilMemberVerdict` objects, and calls `write_final_council_evidence`. This does not require `council.general.enabled`.
+
+Additionally, present these three sub-items as part of the same exchange:
+- Parallel coders (default: 1, range: 1-6) - how many coders should run in parallel. Parallel coders each run in an isolated git worktree (separate working dir + branch) and merge back automatically, so they never overwrite each other's files - safe and faster, but only for tasks whose declared file scopes do NOT overlap. The per-task file scopes that determine a safe parallel count are not known until the plan is finalized, so default to 1 (serial) here; the precise recommendation is made at plan time once the tasks and their scopes exist.
   > COMMON MISCONCEPTION: worktree isolation is baseline for standard parallel coders, governed by the parallel execution profile plus top-level `worktree.policy`. It is not provided by Lean Turbo or Epic. Do not recommend Lean Turbo or Epic to obtain worktree isolation; recommend them only for what they add beyond baseline (Lean Turbo: lane planning, file locks, phase reviewer, integrated diff; Epic: co-change awareness and auto-decide). Worktrees also do not make overlapping scopes safe: dependency readiness, file-disjoint scopes, and merge-back ownership are still required.
-  - Commit frequency (default: phase-level only) - optional per-task checkpoint commit after each task completion.
-  - auto_proceed (boolean, default: false) - when true, auto-advance to the next phase without asking "Ready for Phase N+1?"; runtime toggle via /swarm auto-proceed on|off.
+- Commit frequency (default: phase-level only) - optional per-task checkpoint commit after each task completion.
+- auto_proceed (boolean, default: false) - when true, auto-advance to the next phase without asking "Ready for Phase N+1?"; runtime toggle via /swarm auto-proceed on|off.
+
+<!-- END QA_GATE_BODY -->
   The user answers all four (gates, parallel coders, commit frequency, auto_proceed) in one exchange. Wait for the user's response.
   If the user says parallel coders > 1, write a `## Pending Parallelization Config` section to `.swarm/context.md` alongside the gate selection:
   ```
@@ -283,6 +289,7 @@ TASK: Write the implementation plan to .swarm/plan.md
 OUTPUT: .swarm/plan.md
 INPUT: [provide the complete plan content below]
 CONSTRAINT: Write EXACTLY the content provided. Do not modify, summarize, or interpret.
+ACCEPTANCE: DONE = .swarm/plan.md contains the verbatim plan content provided in INPUT, byte-for-byte, with no modification, summarization, or interpretation. (This fallback has no fr_refs — per ACCEPTANCE FIELD RESOLUTION in your system prompt, use this one-line task-derived DONE restatement. A missing or empty ACCEPTANCE line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED before the coder runs.)
 
 TASK GRANULARITY RULES:
 - SMALL task: 1 file, 1 logical concern. Delegate as-is.

package/.opencode/skills/specify/SKILL.md

@@ -53,24 +53,28 @@ Activates when: user asks to "specify", "define requirements", "write a spec", o
 5b. **QA GATE SELECTION, PARALLEL CODERS, COMMIT FREQUENCY, AND AUTO_PROCEED (dialogue only).**
 Ask the user which QA gates to enable for this plan, how many parallel coders to use, the commit frequency, and auto_proceed -- do not select on their behalf. Present all four items together as one unified exchange. Exception: when SPECIFY is running inside MODE: LOOP with `autonomy=auto`, write the balanced-speed default `## Pending QA Gate Selection` instead (reviewer, test_engineer, sme_enabled, critic_pre_plan, sast_enabled, drift_check ON; council_mode, hallucination_guard, mutation_test, phase_council, final_council OFF), keep phase-level commits, and let MODE: PLAN choose safe parallelism after task scopes exist.
 
+<!-- BEGIN QA_GATE_BODY -->
+
 Present the eleven gates with their defaults (DEFAULT_QA_GATES), parallel coder count, commit frequency, and auto_proceed as a single user-facing section. Offer the user a one-shot choice: accept defaults, or customize. The eleven gates are:
-- reviewer (default: ON) -- code review of coder output
-- test_engineer (default: ON) -- test verification of coder output
-- sme_enabled (default: ON) -- SME consultation during planning/clarification
-- critic_pre_plan (default: ON) -- critic review before plan finalization
-- sast_enabled (default: ON) -- static security scanning
-- council_mode (default: OFF) -- replaces per-task Stage B (reviewer + test_engineer) with the full 5-member council (critic, reviewer, sme, test_engineer, explorer). Requires council.enabled: true in config. (recommended for high-impact architecture, public APIs, schema/data mutation, security-sensitive code)
-- hallucination_guard (default: OFF) -- when enabled, mandatory per-phase API/signature/claim/citation verification via critic_hallucination_verifier at PHASE-WRAP; phase_complete will REJECT phase completion unless .swarm/evidence/{phase}/hallucination-guard.json exists with an APPROVED verdict (recommended for claim-heavy or research-heavy work)
-- mutation_test (default: OFF) -- when enabled, runs mutation testing on source files touched this phase via generate_mutants + mutation_test + write_mutation_evidence at PHASE-WRAP; FAIL verdict blocks phase_complete; WARN is non-blocking (recommended for projects with coverage gaps or safety-critical code)
-- phase_council (default: OFF) -- full 5-member council reviews all work in a phase holistically at phase_complete time. Requires council.enabled: true in config. (recommended for multi-task phases with cross-cutting concerns or high-risk integration)
-- drift_check (default: ON) -- when enabled, mandatory per-phase drift verification via critic_drift_verifier at PHASE-WRAP; compares implemented changes against spec.md intent; hard-blocks phase_complete when spec.md exists and drift evidence is missing or REJECTED; advisory-only when no spec.md exists (recommended for all projects with a specification)
-- final_council (default: OFF) -- when enabled, after all phases complete the architect dispatches the full 5-member council (critic, reviewer, sme, test_engineer, explorer) -- NOT the General Council -- at project scope, collects `CouncilMemberVerdict` objects, and calls `write_final_council_evidence`. This does not require `council.general.enabled`.
+- reviewer (default: ON) - code review of coder output
+- test_engineer (default: ON) - test verification of coder output
+- sme_enabled (default: ON) - SME consultation during planning/clarification
+- critic_pre_plan (default: ON) - critic review before plan finalization
+- sast_enabled (default: ON) - static security scanning
+- council_mode (default: OFF) - replaces per-task Stage B (reviewer + test_engineer) with the full 5-member council (critic, reviewer, sme, test_engineer, explorer). Requires council.enabled: true in config.
+- hallucination_guard (default: OFF) - when enabled, mandatory per-phase API/signature/claim/citation verification at PHASE-WRAP; phase_complete will REJECT phase completion unless .swarm/evidence/{phase}/hallucination-guard.json exists with an APPROVED verdict.
+- mutation_test (default: OFF) - when enabled, runs mutation testing on source files touched this phase via generate_mutants + mutation_test + write_mutation_evidence at PHASE-WRAP; FAIL verdict blocks phase_complete; WARN is non-blocking.
+- phase_council (default: OFF) - full 5-member council reviews all work in a phase holistically at phase_complete time. Requires council.enabled: true in config.
+- drift_check (default: ON) - mandatory per-phase drift verification via critic_drift_verifier at PHASE-WRAP; hard-blocks phase_complete when spec.md exists and drift evidence is missing or REJECTED; advisory-only when no spec.md exists.
+- final_council (default: OFF) - when enabled, after all phases complete the architect dispatches the full 5-member council (critic, reviewer, sme, test_engineer, explorer) - NOT the General Council - at project scope, collects `CouncilMemberVerdict` objects, and calls `write_final_council_evidence`. This does not require `council.general.enabled`.
 
 Additionally, present these three sub-items as part of the same exchange:
-- Parallel coders (default: 1, range: 1-6) -- how many coders should run in parallel. Parallel coders each run in an isolated git worktree (separate working dir + branch) and merge back automatically, so they never overwrite each other's files -- safe and faster, but only for tasks whose file scopes do NOT overlap. The per-task file scopes that determine a safe parallel count are not known until the plan is finalized, so default to 1 (serial) here; the precise recommendation is made at plan time once the tasks and their scopes exist.
+- Parallel coders (default: 1, range: 1-6) - how many coders should run in parallel. Parallel coders each run in an isolated git worktree (separate working dir + branch) and merge back automatically, so they never overwrite each other's files - safe and faster, but only for tasks whose declared file scopes do NOT overlap. The per-task file scopes that determine a safe parallel count are not known until the plan is finalized, so default to 1 (serial) here; the precise recommendation is made at plan time once the tasks and their scopes exist.
   > COMMON MISCONCEPTION: worktree isolation is baseline for standard parallel coders, governed by the parallel execution profile plus top-level `worktree.policy`. It is not provided by Lean Turbo or Epic. Do not recommend Lean Turbo or Epic to obtain worktree isolation; recommend them only for what they add beyond baseline (Lean Turbo: lane planning, file locks, phase reviewer, integrated diff; Epic: co-change awareness and auto-decide). Worktrees also do not make overlapping scopes safe: dependency readiness, file-disjoint scopes, and merge-back ownership are still required.
-- Commit frequency (default: phase-level only) -- optional per-task checkpoint commit after each task completion.
-- auto_proceed (boolean, default: false) -- when true, auto-advance to the next phase without asking "Ready for Phase N+1?"; runtime toggle via /swarm auto-proceed on|off.
+- Commit frequency (default: phase-level only) - optional per-task checkpoint commit after each task completion.
+- auto_proceed (boolean, default: false) - when true, auto-advance to the next phase without asking "Ready for Phase N+1?"; runtime toggle via /swarm auto-proceed on|off.
+
+<!-- END QA_GATE_BODY -->
 
 The user answers all four (gates, parallel coders, commit frequency, auto_proceed) in one exchange. Wait for the user's response.
 

package/.opencode/skills/swarm-pr-feedback/SKILL.md

@@ -214,6 +214,7 @@ available scope controller merely to reduce ceremony.
 **When to use `declare_scope` (preferred):** any feedback round that touches 2+ files, OR any feedback round where the file scope is not 100% obvious from the prompt. Before delegating, save a minimal plan via `save_plan` with a single phase containing the feedback-closure tasks, then call `declare_scope` per task with the exact file list.
 
 **Carve-out for direct Task delegation:** 1-file, single-function changes where the file path appears verbatim in the coder's prompt may use direct `Task(subagent_type="<coder>", ...)` delegation without `declare_scope`, where `<coder>` is the active swarm's coder agent (e.g. `coder`, or `paid_coder` when the swarm id is `paid`). This is a narrow exception; the orchestrator is responsible for verifying the scope is unambiguous.
+→ REQUIRED: even under this carve-out, the direct Task dispatch MUST contain a literal `ACCEPTANCE:` line — resolve per ACCEPTANCE FIELD RESOLUTION in your system prompt (one-line task-derived DONE restatement for the feedback fix, since feedback-closure runs typically have no fr_refs). A missing line is BLOCKED by ACCEPTANCE_FIELD_REQUIRED.
 
 **Anti-pattern:** do not use `Task` delegation for multi-file feedback fixes just to skip `save_plan` — the loss of scope discipline is not worth the saved ceremony.
 

package/dist/agents/architect.d.ts

@@ -61,14 +61,16 @@ export declare function buildArchitectureSupervisionWorkflow(arch?: Architecture
  */
 export declare function buildCouncilWorkflow(council?: CouncilWorkflowConfig): string;
 /**
- * Build the user-facing QA gate selection dialogue, used by MODE: SPECIFY
- * (step 5b), MODE: BRAINSTORM (Phase 6), and MODE: PLAN (post-`save_plan`
- * inline path). The dialogue is dialogue-only — persistence happens during
- * MODE: PLAN after `save_plan` creates `plan.json`.
+ * TEST-ONLY ORACLE: This function is no longer wired into the architect prompt
+ * (the {{QA_GATE_DIALOGUE_*}} placeholder substitution was removed in #1690,
+ * task 3.1). It is retained here because three test files import it directly:
+ *   - src/__tests__/qa-gate-hardening.test.ts:17
+ *   - tests/unit/agents/architect-hallucination-gate.test.ts:3
+ *   - tests/unit/skills/plan-protocol.test.ts:8
  *
- * The lead-in sentence varies per mode, but the body (ten gates with
- * defaults, one-shot accept-or-customize prompt) is shared so SPECIFY,
- * BRAINSTORM, and PLAN inline paths stay in lockstep.
+ * Future work (task 3.2) will create `references/qa-gate-gates-body.md` and
+ * migrate those tests to assert against the canonical body. Once migrated,
+ * this helper may be deleted.
  */
 export declare function buildQaGateSelectionDialogue(modeLabel: 'BRAINSTORM' | 'SPECIFY' | 'PLAN'): string;
 export declare function createArchitectAgent(model: string, customPrompt?: string, customAppendPrompt?: string, adversarialTesting?: AdversarialTestingConfig, council?: CouncilWorkflowConfig, uiReview?: UIReviewConfig, memoryEnabled?: boolean, architecturalSupervision?: ArchitectureSupervisionWorkflowConfig, designDocsEnabled?: boolean, externalSkillsEnabled?: boolean, turboEnabled?: boolean, skillsEnabled?: boolean): AgentDefinition;

package/dist/cli/{curation-policy-62w2pwfz.js → curation-policy-dptr1rfe.js}

@@ -4,9 +4,9 @@ import {
   authorizeCuration,
   buildConfigFingerprintInput,
   readCohortConfigFingerprint
-} from "./index-1htanqp1.js";
+} from "./index-mgrsx5hn.js";
 import"./index-rtry5xyf.js";
-import"./index-gbnpz7rh.js";
+import"./index-2bnfwmk3.js";
 import"./index-ae75rja9.js";
 import"./index-q27bajqb.js";
 import"./index-zgwm4ryv.js";

package/dist/cli/{curator-mhhvx2pw.js → curator-23hynz78.js}

@@ -14,28 +14,28 @@ import {
   runCuratorInit,
   runCuratorPhase,
   writeCuratorSummary
-} from "./index-s6hskqg6.js";
+} from "./index-0ff5cm9j.js";
 import"./index-dezgmvtw.js";
 import"./index-jt7hnr7q.js";
 import"./index-kk1scggc.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
 import"./index-6n2jpz7x.js";
-import"./index-gd5w3ef8.js";
-import"./index-0f45t7xy.js";
-import"./index-e315gwc9.js";
+import"./index-yfzn5r9s.js";
+import"./index-bcgfhxzv.js";
+import"./index-cdx337js.js";
 import"./index-vxv732ex.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
 import"./index-23zsx7dm.js";
-import"./index-yq4s3q43.js";
-import"./index-1htanqp1.js";
+import"./index-kwnsatzq.js";
+import"./index-mgrsx5hn.js";
 import"./index-rtry5xyf.js";
-import"./index-1012f47p.js";
-import"./index-gbnpz7rh.js";
+import"./index-2yd75hms.js";
+import"./index-2bnfwmk3.js";
 import"./index-ae75rja9.js";
 import"./index-q27bajqb.js";
-import"./index-74xejn4v.js";
+import"./index-a1c9az5e.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
 import"./index-r1gdkn2d.js";

package/dist/cli/{curator-llm-factory-av2tcfy9.js → curator-llm-factory-r648jn8e.js}

@@ -1,28 +1,28 @@
 // @bun
 import {
   createCuratorLLMDelegate
-} from "./index-s6hskqg6.js";
+} from "./index-0ff5cm9j.js";
 import"./index-dezgmvtw.js";
 import"./index-jt7hnr7q.js";
 import"./index-kk1scggc.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
 import"./index-6n2jpz7x.js";
-import"./index-gd5w3ef8.js";
-import"./index-0f45t7xy.js";
-import"./index-e315gwc9.js";
+import"./index-yfzn5r9s.js";
+import"./index-bcgfhxzv.js";
+import"./index-cdx337js.js";
 import"./index-vxv732ex.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
 import"./index-23zsx7dm.js";
-import"./index-yq4s3q43.js";
-import"./index-1htanqp1.js";
+import"./index-kwnsatzq.js";
+import"./index-mgrsx5hn.js";
 import"./index-rtry5xyf.js";
-import"./index-1012f47p.js";
-import"./index-gbnpz7rh.js";
+import"./index-2yd75hms.js";
+import"./index-2bnfwmk3.js";
 import"./index-ae75rja9.js";
 import"./index-q27bajqb.js";
-import"./index-74xejn4v.js";
+import"./index-a1c9az5e.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
 import"./index-r1gdkn2d.js";

package/dist/cli/{guardrail-explain-kqx2bczn.js → guardrail-explain-6atsd4vr.js}

@@ -1,29 +1,29 @@
 // @bun
 import {
   handleGuardrailExplain
-} from "./index-ccfkfrew.js";
-import"./index-s6hskqg6.js";
+} from "./index-y4ry07h8.js";
+import"./index-0ff5cm9j.js";
 import"./index-dezgmvtw.js";
 import"./index-jt7hnr7q.js";
 import"./index-kk1scggc.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
 import"./index-6n2jpz7x.js";
-import"./index-gd5w3ef8.js";
-import"./index-0f45t7xy.js";
-import"./index-e315gwc9.js";
+import"./index-yfzn5r9s.js";
+import"./index-bcgfhxzv.js";
+import"./index-cdx337js.js";
 import"./index-vxv732ex.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
 import"./index-23zsx7dm.js";
-import"./index-yq4s3q43.js";
-import"./index-1htanqp1.js";
+import"./index-kwnsatzq.js";
+import"./index-mgrsx5hn.js";
 import"./index-rtry5xyf.js";
-import"./index-1012f47p.js";
-import"./index-gbnpz7rh.js";
+import"./index-2yd75hms.js";
+import"./index-2bnfwmk3.js";
 import"./index-ae75rja9.js";
 import"./index-q27bajqb.js";
-import"./index-74xejn4v.js";
+import"./index-a1c9az5e.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
 import"./index-r1gdkn2d.js";

package/dist/cli/{hive-promoter-6mhnhrbx.js → hive-promoter-bnkhzd46.js}

@@ -7,30 +7,30 @@ import {
   isHiveEligible,
   promoteFromSwarm,
   promoteToHive
-} from "./index-s6hskqg6.js";
+} from "./index-0ff5cm9j.js";
 import"./index-dezgmvtw.js";
 import"./index-jt7hnr7q.js";
 import"./index-kk1scggc.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
 import"./index-6n2jpz7x.js";
-import"./index-gd5w3ef8.js";
-import"./index-0f45t7xy.js";
-import"./index-e315gwc9.js";
+import"./index-yfzn5r9s.js";
+import"./index-bcgfhxzv.js";
+import"./index-cdx337js.js";
 import"./index-vxv732ex.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
 import"./index-23zsx7dm.js";
-import"./index-yq4s3q43.js";
-import"./index-1htanqp1.js";
+import"./index-kwnsatzq.js";
+import"./index-mgrsx5hn.js";
 import"./index-rtry5xyf.js";
 import {
   resolveHiveKnowledgePath
-} from "./index-1012f47p.js";
-import"./index-gbnpz7rh.js";
+} from "./index-2yd75hms.js";
+import"./index-2bnfwmk3.js";
 import"./index-ae75rja9.js";
 import"./index-q27bajqb.js";
-import"./index-74xejn4v.js";
+import"./index-a1c9az5e.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
 import"./index-r1gdkn2d.js";