opencode-swarm 7.193.0 → 7.195.0

package/.opencode/skills/commit-pr/SKILL.md

@@ -100,3 +100,11 @@ If this session is running an issue trace (`/swarm issue --trace`), call
 right after the PR is opened so the issue-trace workflow can reach its terminal
 `published` state — without it the trace stays at `publication_handoff` and is NOT
 considered resolved.
+
+## Contract addendum (2026-10-12)
+
+- **Publication-time re-derivation.** As the LAST step before `gh pr create`
+  / `pr edit`, re-derive every claim in the body from the final tree: PR head
+  SHA, test counts, file lists, closure evidence. A body drafted earlier is
+  stale by construction — the head moves with every amend — and a stale
+  `PR head:` line in particular is guarded by no validator.

package/.opencode/skills/issue-tracer/references/acceptance-checks.md

@@ -88,3 +88,23 @@ Minimal recipe: `git stash` the fix hunk (or apply the inverse patch) in the thr
 ## When the path does not apply
 
 Some issues (pure documentation fixes, non-executable product decisions already resolved by classification) have no meaningful acceptance check at all. Use NON-EXECUTABLE rows with named substitute evidence rather than forcing an artificial executable check, and let the plan critic confirm the justification is real rather than a shortcut around the loop.
+
+## Contract addendum (2026-10-12)
+
+- **Named-mutation discipline.** Every DISCRIMINATING check must name, in its
+  08-test-results block, one concrete mutation that kills it and the test that
+  fails under it — "the suite passes" is not evidence a check bites. A check
+  whose named mutant survives the shipped suite is a coverage gap, not a pass.
+  Probe hygiene is part of the contract: restore with `git checkout -- <file>`
+  after every probe and verify `git status --porcelain` clean before any
+  commit — a stray uncommitted mutant can ride explicit-path staging into the
+  fix commit.
+- **Frozen-docstring wording.** Check authors must phrase frozen-file
+  docstrings to stay true at both ends: "RED at base, GREEN after the fix",
+  never "must FAIL at the current tree" — the file ships and the claim becomes
+  false, and correcting it costs a checkpoint AMEND plus a re-anchored receipt.
+- **Replay script at freeze.** Write `repro/replay-all.sh` beside the manifest:
+  one explicit `repro-check.sh run` per check with `--base --class --id
+  --expect --copy --deps` spelled out (every file the base leg needs listed in
+  `--copy`). Replays then run one command instead of re-assembling flags — an
+  omitted `--copy` silently rewrites certified RED base logs as ERROR.

package/.opencode/skills/issue-tracer/references/full-resolution-contract.md

@@ -67,3 +67,15 @@ Before declaring the issue ready:
 - [ ] Publication (commit/push/PR) followed the repo's canonical publish protocol.
 - [ ] Merge itself was not performed by this skill; an explicit, quoted, SHA-bound user approval is recorded (`10b-merge-approval.md`).
 - [ ] PR-ready summary is complete.
+
+## Contract addendum (2026-10-12)
+
+- **Closure reconciliation.** Closure is a reconciliation against the final
+  PUBLISHED artifacts: every requirement and every source finding keeps a
+  stable identity through to the closure ledger; each disposition names what
+  was actually discharged (a mutant identity, a file, a published sentence)
+  and is grep-verified against the artifact it claims; any partial closure
+  carries explicit deferment authority (a filed follow-up issue or a quoted
+  user decision). A ledger that keeps the FIXED label while the obligation
+  changed shape is a false closure even when the code is correct, and a
+  mutation identity must never be substituted between obligation and proof.

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

@@ -12,7 +12,7 @@ description: >
   (structural pre-checks) and Stage B (reviewer + test_engineer) gates and the
   reviewer + critic closeout gate are MANDATORY for any change made as part of
   this process.
-swarm-contract-digest: 143d9443a82d
+swarm-contract-digest: aca3f05b0677
 ---
 
 # Swarm PR Feedback
@@ -428,7 +428,7 @@ Rules:
   items.
 - Use explicit IDs for non-review feedback when useful, for example
   `CONFLICT-001` for merge/base drift and `CI-001` for check failures, so PR
-  bodies can show exactly how operational blockers were closed.
+  bodies can show exactly how operational blockers were closed. See `references/operational-gotchas.md` (## Contract addendum (2026-10-12)) for the body-claim-audit, probe-hygiene, and stable-obligation/coverage-diff ledger rules.
 
 ### Mandatory: integrate all PR comments with feedback or findings before branch validation (Stage A)
 

package/.opencode/skills/swarm-pr-feedback/references/operational-gotchas.md

@@ -47,3 +47,21 @@ requirements imposed on unrelated repositories.
    different fixes on different code paths, use separate coder tasks even if
    targeting the same file. The "ONE task per coder" rule is about distinct
    objectives, not about N edits to one file.
+
+## Contract addendum (2026-10-12)
+
+- **Body-claim audit.** Before the reviewer gate, grep the LIVE published
+  artifact (PR body, issue body) against every ledger row whose fix-ref is that
+  artifact: the fixed phrasing present, the contradicting phrasing absent. A
+  row marked FIXED for a file never edited is an unbacked claim — record
+  CLOSED only after the grep matches.
+- **Probe hygiene.** Mutation/revert probes must leave the tree as found:
+  restore with `git checkout -- <file>` after every probe and verify
+  `git status --porcelain` clean before the first commit of the round. An
+  uncommitted mutant left in a tracked source file can ride explicit-path
+  staging into the fix commit — or `git add -A` into the release.
+- **Stable obligation identity + coverage-diff.** Never substitute the
+  obligation between ledger and proof: if the ledger defined mutant M4 as X,
+  closing it with a different mutant Y is a new row, not a closure.
+  Coverage-diff the ledger against EVERY source finding table by ID, both
+  directions, before implementing.

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

@@ -3,7 +3,7 @@ name: swarm-pr-review
 audience: swarm-plugin
 description: Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive tolerance and high recall in any repository, on any agent harness (structured lane controller, native parallel subagents, or single-context sequential passes).
 disable-model-invocation: true
-swarm-contract-digest: a191a66d5a4d
+swarm-contract-digest: 66db247ce302
 ---
 
 # /swarm-pr-review
@@ -167,7 +167,7 @@ receipt; persist post-explorer findings; run reviewers;
 run critics; then persist the final artifact and complete the workflow. Transcript
 `[CANDIDATE]` / `[CLEAN]` rows are deprecated legacy compatibility only for
 lanes whose snapped `pr_review_legacy_transcript_compatibility` contract
-explicitly enables them.
+explicitly enables them. Candidate rows are defect claims only — never verification notes or INFO-severity confirmations (see `references/prompt-templates.md`, ## Contract addendum (2026-10-12)).
 The **initial** micro dispatch MUST supply the complete trigger-evaluation
 ledger; that dispatch freezes it for the session.
 Any subsequent micro batch in that same session MAY omit `trigger_evaluation`
@@ -1444,25 +1444,26 @@ Reviewer output format:
 [REVIEWED] | item_id | classification | evidence_type | severity | introduced_by_pr | file:line | rationale | probe | reviewer_notes | risk_impact | risk_tags
 ```
 
-For the mechanically derived `CLEAN-REVIEW` sentinel, use the same exact row
-with `DISPROVED | STRUCTURALLY_PROVEN | NONE | UNKNOWN | N/A` and concrete
-rationale/probe/reviewer fields; the sentinel means the reviewer independently
-found no surviving actionable candidate, not that reviewer validation was
-skipped.
+CLEAN-REVIEW sentinel and DISPROVED/PRE_EXISTING row details: see
+`references/parser-dry-run.md`.
 
 Every reviewer response must end with one parseable `[REVIEWED]` row per
 assigned candidate. A malformed `[REVIEWED]` row is not a verdict: re-dispatch
 with the exact contract (max 2), then mark the reviewer dimension BLOCKED if no
 valid row returns.
 
-`DISPROVED` reviewer rows must use `NONE` for `final_severity`. `PRE_EXISTING`
-findings must include the base-branch evidence if available.
-
 After reviewer lanes settle, persist the post-reviewer finding ledger before
 critic routing or synthesis. The artifact must preserve `CONFIRMED`,
 `DISPROVED`, `PRE_EXISTING`, and still-`PENDING` records with reviewer IDs and
 next actions.
 
+Counterbalanced reviewer passes (#2906): when the candidate inventory holds more
+than one item, dispatch the reviewer phase as two batches over the same inventory;
+the controller alternates presentation order A (canonical) / B (reversed), stamps
+`presentation_order` on each batch receipt, and marks each merged verdict
+`order_agreement` (agree/disagree/single); unstable items are auto-flagged to the
+critic and the report marks and counts them. Detail: references/counterbalancing.md.
+
 ---
 
 ## Phase 7: Falsification Probe Requirement

package/.opencode/skills/swarm-pr-review/references/counterbalancing.md

@@ -0,0 +1,68 @@
+# Counterbalanced Reviewer Passes (issue #2906)
+
+The review protocol presents candidate findings to the reviewer phase in two
+independent batches over the same full inventory whenever that inventory holds
+more than one item. The controller assigns presentation orders to those
+batches deterministically — the first reviewer batch in the window renders its
+candidates in canonical (lexicographically sorted) order (`presentation_order:
+A`) and the second renders the exact reverse (`presentation_order: B`),
+alternating for any further batches. A retry batch receives the NEXT ordinal,
+so a re-dispatch of a failed pass observes the opposite order by design.
+
+## Where the signal lives
+
+- **Prompt**: each reviewer lane's controller contract carries the
+  `presentation_order:` line and renders `assigned_item_ids` in that pass's
+  order; the lane is instructed to order its candidate prose identically (the
+  mechanical reordering covers the controller-owned id list — prose-order
+  compliance is instruction-mediated).
+- **Receipts**: the per-batch coherence record stamps `presentationOrder`
+  ('A' | 'B'), and the lane collection receipt footer names it when gate state
+  is readable at collection time.
+- **Merged verdicts**: every composed reviewer claim carries `order_agreement`
+  — `agree` when both the A and B passes produced the same
+  (classification, severity) pair for the item, `disagree` when the verdict
+  flipped with presentation order, `single` when fewer than two marked orders
+  observed the item (including single-pass runs and pre-#2906 batches).
+- **Critic routing**: order-unstable items are named on the critic contract's
+  `order_unstable_item_ids:` line so the critic prioritizes them; the critic
+  batch's coherence record keeps an audit-only snapshot of that list.
+- **Findings and report**: findings rows carry `order_agreement` (validated
+  against the composed verdicts at write time — a contradictory or unbacked
+  affirmative label is rejected); the rendered PR-review report marks
+  order-unstable findings with the `order-unstable` token and counts them in a
+  summary line.
+
+## How to read the labels
+
+- `agree` — order-stable: both passes reached the same classification and
+  severity. The strongest reviewer signal.
+- `disagree` — order-unstable: the verdict flipped with presentation order.
+  Not automatically wrong — it means the finding's verdict is sensitive to
+  candidate ordering and deserves critic priority and explicit evidence.
+- `single` — only one presentation order observed the item; no order-effect
+  evidence either way.
+
+A single-item inventory (or single-item lane) renders identical A and B
+sequences; its labels remain computed but are descriptive only — they cannot
+implicate order effects at n=1.
+
+## Operator notes
+
+- The presentation-order ordinal counts retained reviewer batches in the
+  reviewer window (batches after the latest council batch), excluding the
+  batch being recorded. Both the dispatch-time derivation and the record
+  guard apply the SAME pure capacity prune before counting, so at the
+  ≥128-batch cap the derived ordinal already reflects the post-prune window
+  and the two sides cannot disagree about prune parity. A dispatch whose
+  derived order still diverges from its recorded receipt — state genuinely
+  changed between derivation and recording — fails closed; re-derive and
+  re-dispatch. That retry cannot wedge: the derivation is deterministic over
+  the current state, so it re-derives exactly the value the guard will stamp.
+- The capacity prune never drops a reviewer batch that contributed order
+  observations: an older counterbalanced pass is retained even when the newer
+  pass claimed every item (its observations ride the agreement-only
+  continuation), so `agree`/`disagree` labels survive GC and never silently
+  degrade to `single`.
+- The wire `[REVIEWED]` row grammar is unchanged: presentation order is a
+  property of the pass (batch), not of any individual row.

package/.opencode/skills/swarm-pr-review/references/findings-persistence-contract.md

@@ -10,6 +10,7 @@ reviewer_classifications: CONFIRMED | DISPROVED | UNVERIFIED | PRE_EXISTING
 reviewer_evidence_types: STRUCTURALLY_PROVEN | EXECUTION_PROVEN | STATIC_TRACE_PROVEN | PLAUSIBLE_BUT_UNVERIFIED
 critic_fields: marker | item_id | status | severity | rationale | required_change
 critic_statuses: UPHELD | DOWNGRADED | DISPROVED | NEEDS_MORE_EVIDENCE
+order_agreements: agree | disagree | single
 severities: CRITICAL | HIGH | MEDIUM | LOW | INFO | NONE
 finding_statuses: PENDING | CONFIRMED | DISPROVED | PRE_EXISTING
 finding_actions: route_to_reviewer | route_to_critic | report | suppress_with_reason | handoff_to_feedback
@@ -251,3 +252,23 @@ newline, and `\r` a carriage return. The byte-zero contract card injected into
 each Profile A lane is authoritative for the live enums and includes positive
 and explicitly discarded negative examples. Discarded examples are
 documentation only and must never be emitted as live marker rows.
+
+## `order_agreement` (issue #2906)
+
+Every findings record MAY carry `order_agreement`, the order-stability of that
+finding's reviewer verdict across the counterbalanced presentation orders
+(pass A = canonical sorted ids, pass B = the exact reverse):
+
+- `agree` — both marked orders produced the same `(classification, severity)`;
+- `disagree` — they differed. The finding is order-unstable: rendered with an
+  `(order-unstable)` marker and counted in the report summary, and flagged to
+  the critic via `order_unstable_item_ids`;
+- `single` — fewer than two marked orders were observed (a single reviewer
+  pass, or unmarked/legacy batches, which contribute no observations).
+
+The field is **optional**. It is written on `post_reviewer` and `post_critic`
+rows, is cross-checked at write time against the composed reviewer verdicts,
+and **must not be omitted** on a finding whose composed label is `disagree` —
+an omitted label there fails the write closed rather than silently suppressing
+the marker. It is part of the replay-identity key: a re-submission whose
+`order_agreement` differs is not an exact replay.

package/.opencode/skills/swarm-pr-review/references/parser-dry-run.md

@@ -252,3 +252,14 @@ IMPORTANT: If a finding claims behavior is "new" or "introduced by the PR", you
   is split before dispatch.
 - The `invocation_envelope` in the parser response provides audit provenance
   for every extracted candidate.
+
+## Reviewer row details (relocated from SKILL.md, issue #2906)
+
+For the mechanically derived `CLEAN-REVIEW` sentinel, use the same exact row
+with `DISPROVED | STRUCTURALLY_PROVEN | NONE | UNKNOWN | N/A` and concrete
+rationale/probe/reviewer fields; the sentinel means the reviewer independently
+found no surviving actionable candidate, not that reviewer validation was
+skipped.
+
+`DISPROVED` reviewer rows must use `NONE` for `final_severity`. `PRE_EXISTING`
+findings must include the base-branch evidence if available.

package/.opencode/skills/swarm-pr-review/references/prompt-templates.md

@@ -171,3 +171,11 @@ format above remains the extraction contract. Explorers emit structured
 records regardless of which harness runs them.
 
 Do not let speed degrade validation quality.
+
+## Contract addendum (2026-10-12)
+
+- **Candidate rows are defect claims only.** Never emit verification notes,
+  confirmations, or coverage observations as CANDIDATE rows, and no
+  INFO-severity candidates — confirmations belong in the lane's
+  attestation/CLEAN row. A misattributed or confirmatory candidate inflates
+  reviewer adjudication for zero signal.

package/README.md

@@ -151,7 +151,7 @@ Swarm has two independent mode systems:
 
 Full-Auto reduces approval friction by deterministically allowing safe operations (read-only tools, in-scope writes, safe shell) and routing every ambiguous or high-risk action (writes to plugin/build/guardrail paths, network, dependency changes, plan/phase mutations, subagent delegation) through the read-only `critic_oversight` agent before it executes. Denials are returned to the agent as structured signals so it can choose a safer path; repeated denials pause the run; phase completion requires an APPROVED oversight record. See [docs/modes.md](docs/modes.md#full-auto) for `mode`, `permission_policy`, `denials`, and `oversight` config keys, fail-closed semantics, and recovery from a paused run.
 
-Epic binds to the current plan and needs an OpenCode 1.x host for now (on OpenCode 2 the plugin has no SDK client yet, so `/swarm epic start` refuses with `host-unsupported`). `/swarm epic start` also refuses plans too small to benefit and suggests Balanced. The `epic_next_wave` tool then dispatches each phase as waves of tasks whose declared scopes don't conflict; in a git project each coder works in an isolated worktree on an epic branch, and `/swarm epic close` squash-lands the work as staged changes for you to review. Every task in a wave still runs the full per-task QA pipeline (Stage A and Stage B). Epic learns which files tasks tend to write together and uses it to plan later waves and epics. See [docs/modes.md](docs/modes.md#epic-mode-preview); maintainers start with [src/epic/README.md](src/epic/README.md).
+Epic binds to the current plan and runs fully on an OpenCode 1.x host. The OpenCode 2 host-capability guard now passes (the plugin's v2 adapter ships a session-capable client), but the epic entry point stays double-gated on v2 (`human-only` toolPolicy + no v2 command dispatch) and v2 child sessions cannot yet be placed in a coder worktree, so full Epic on OpenCode 2 waits on #3169 (Phase 3/4). `/swarm epic start` also refuses plans too small to benefit and suggests Balanced. The `epic_next_wave` tool then dispatches each phase as waves of tasks whose declared scopes don't conflict; in a git project each coder works in an isolated worktree on an epic branch, and `/swarm epic close` squash-lands the work as staged changes for you to review. Every task in a wave still runs the full per-task QA pipeline (Stage A and Stage B). Epic learns which files tasks tend to write together and uses it to plan later waves and epics. See [docs/modes.md](docs/modes.md#epic-mode-preview); maintainers start with [src/epic/README.md](src/epic/README.md).
 
 **Project mode** — persistent via `execution_mode` config key:
 

package/dist/background/pending-delegations.d.ts

@@ -720,6 +720,14 @@ export declare function buildBackgroundCompletionEventId(input: BuildBackgroundC
  * same eventId identity material, same status-equals-record guarantee.
  */
 export declare function buildTypedDelegationTerminal(record: Pick<BackgroundDelegationRecord, 'correlationId' | 'jobId'>, status: BackgroundTerminalResult['status'], result: BackgroundDelegationResult, now: number): BackgroundTerminalResult;
+/**
+ * The retained receipt for one delegation record (result copy first, the
+ * closed-summary `terminalResult` copy second). Exported for the
+ * `pr_workflow_status` read surface (issue #3095) so the status tool reads
+ * receipts through the same accessor the store's own writers use instead of
+ * duplicating the fallback order.
+ */
+export declare function recordedPrReviewResultReceipt(record: BackgroundDelegationRecord): PrReviewResultReceipt | undefined;
 export type TerminalClaimDisposition = 'claimed' | 'resume_settlement' | 'retry_ingestion' | 'preserved' | 'consumed' | 'duplicate';
 export interface TerminalClaim {
     disposition: TerminalClaimDisposition;

package/dist/background/pr-review-collection-receipt.d.ts

@@ -21,7 +21,11 @@ declare const PrReviewCollectionReceiptPayloadSchema: z.ZodObject<{
         rejected: "rejected";
     }>;
     reviewItemIds: z.ZodArray<z.ZodString>;
-}, z.core.$strict>;
+    presentationOrder: z.ZodOptional<z.ZodEnum<{
+        A: "A";
+        B: "B";
+    }>>;
+}, z.core.$loose>;
 export type PrReviewCollectionReceiptPayload = z.infer<typeof PrReviewCollectionReceiptPayloadSchema>;
 declare const PrReviewCollectionReceiptShedMarkerSchema: z.ZodObject<{
     schemaVersion: z.ZodLiteral<1>;
@@ -50,6 +54,8 @@ export interface PrReviewCollectionReceiptBinding {
     correlationId: string;
     mode?: string;
     workflowLane?: string;
+    /** Issue #2906: optional presentation order threaded from the batch's coherence record. */
+    presentationOrder?: 'A' | 'B';
 }
 export interface PrReviewCollectionReceiptResult {
     text?: string;

package/dist/background/pr-review-contract.d.ts

@@ -340,6 +340,11 @@ export declare const PrReviewFindingSchema: z.ZodObject<{
         GIT: "GIT";
         CONFIGURATION: "CONFIGURATION";
     }>>>;
+    order_agreement: z.ZodOptional<z.ZodEnum<{
+        agree: "agree";
+        disagree: "disagree";
+        single: "single";
+    }>>;
 }, z.core.$strict>;
 export { type PrReviewCriticRoutingInput, prReviewFindingRequiresCritic, } from '../pr-review/critic-routing.js';
 export declare const PrReviewHandoffSchema: z.ZodObject<{
@@ -428,6 +433,11 @@ export declare const WritePrReviewArtifactArgsSchema: z.ZodDiscriminatedUnion<[z
             GIT: "GIT";
             CONFIGURATION: "CONFIGURATION";
         }>>>;
+        order_agreement: z.ZodOptional<z.ZodEnum<{
+            agree: "agree";
+            disagree: "disagree";
+            single: "single";
+        }>>;
     }, z.core.$strict>>;
     partial_base_coverage: z.ZodOptional<z.ZodObject<{
         unresolved_dimensions: z.ZodArray<z.ZodEnum<{

package/dist/cli/{auto-checkpoint-taay16xe.js → auto-checkpoint-anf21wwa.js}

@@ -1,27 +1,27 @@
 // @bun
-import"./index-vbp35frb.js";
+import"./index-82aj6gaj.js";
 import"./index-g22dps7x.js";
 import"./index-0725jpp7.js";
 import {
   appendCoreEventSync
-} from "./index-qh93qjc2.js";
+} from "./index-6183at3v.js";
 import {
   derivePlanIdentityHash
 } from "./index-7pmbnjvj.js";
-import"./index-ndec8akq.js";
-import"./index-mtqwyjrg.js";
+import"./index-gc0aeth5.js";
+import"./index-7rtq2t5n.js";
 import"./index-fzpt2djt.js";
-import"./index-hfssjyxs.js";
+import"./index-yf2z4j7s.js";
 import"./index-gx2vp8gx.js";
 import {
   loadPluginConfigWithMeta
-} from "./index-ngk8hpc3.js";
+} from "./index-c6hyd8hg.js";
 import {
   init_git_executable,
   resolveGitExecutable
 } from "./index-zxdawwc7.js";
-import"./index-1dx5zyss.js";
-import"./index-py8wpe81.js";
+import"./index-jn4mmhqc.js";
+import"./index-hqrkr9ag.js";
 import"./index-bk5tah7q.js";
 import"./index-gknz3bv1.js";
 import"./index-zpsr8rpc.js";
@@ -152,7 +152,7 @@ async function maybeSaveAutoCheckpoint(directory, plan) {
     generation += 1;
     label = buildAutoCheckpointLabel(plan, completedCount, generation);
   }
-  const { saveCheckpointRecord } = await import("./checkpoint-6229g3jq.js");
+  const { saveCheckpointRecord } = await import("./checkpoint-ngdw2qx2.js");
   const result = await saveCheckpointRecord(label, directory);
   if (result.success) {
     emitAutoSavedEvent(directory, {

package/dist/cli/{checkpoint-6229g3jq.js → checkpoint-ngdw2qx2.js}

@@ -3,40 +3,40 @@ import {
   _internals,
   checkpoint,
   saveCheckpointRecord
-} from "./index-nktwf2xm.js";
-import"./index-he2nyr7x.js";
+} from "./index-xs9cn3c0.js";
+import"./index-epdzvp4w.js";
 import"./index-6b295cas.js";
 import"./index-9nyqt3kb.js";
-import"./index-bgtfvst1.js";
+import"./index-peyz4k9k.js";
 import"./index-v3bmwmqw.js";
-import"./index-4gacy6y6.js";
+import"./index-z59414gv.js";
 import"./index-g4fs6z4e.js";
 import"./index-m9zzj4ee.js";
-import"./index-84k9zzv1.js";
+import"./index-kphy4we7.js";
 import"./index-2s7dvzff.js";
-import"./index-vbp35frb.js";
+import"./index-82aj6gaj.js";
 import"./index-g22dps7x.js";
 import"./index-0725jpp7.js";
-import"./index-5ev6f1gj.js";
-import"./index-qh93qjc2.js";
-import"./index-vg8sxg12.js";
-import"./index-0e318vgt.js";
+import"./index-1hcjxz6w.js";
+import"./index-6183at3v.js";
+import"./index-crz772sx.js";
+import"./index-app2rmxv.js";
 import"./index-ry16d01s.js";
 import"./index-rdm3px0g.js";
 import"./index-7pmbnjvj.js";
-import"./index-ndec8akq.js";
-import"./index-e8k0v19e.js";
+import"./index-gc0aeth5.js";
+import"./index-xmbtwtgw.js";
 import"./index-t7hmqgjy.js";
-import"./index-mtqwyjrg.js";
+import"./index-7rtq2t5n.js";
 import"./index-fzpt2djt.js";
 import"./index-ejhxgyvm.js";
 import"./index-7g4c7s5r.js";
-import"./index-hfssjyxs.js";
+import"./index-yf2z4j7s.js";
 import"./index-gx2vp8gx.js";
-import"./index-ngk8hpc3.js";
+import"./index-c6hyd8hg.js";
 import"./index-zxdawwc7.js";
-import"./index-1dx5zyss.js";
-import"./index-py8wpe81.js";
+import"./index-jn4mmhqc.js";
+import"./index-hqrkr9ag.js";
 import"./index-bk5tah7q.js";
 import"./index-gknz3bv1.js";
 import"./index-zpsr8rpc.js";

package/dist/cli/{coder-settlement-hexmmefv.js → coder-settlement-bqb059y2.js}

@@ -14,26 +14,26 @@ import {
   releaseCoderDispatchOwnership,
   settleCoderDispatch,
   transferCoderSettlementToBackground
-} from "./index-ymnathfr.js";
-import"./index-fd6b9f38.js";
-import"./index-6s3ab22d.js";
-import"./index-nz6ehpjn.js";
-import"./index-x2phyvcv.js";
+} from "./index-fk4j26km.js";
+import"./index-ghckhk16.js";
+import"./index-dfrcc46h.js";
+import"./index-kmvy5fr8.js";
+import"./index-479kf368.js";
 import"./index-g4fs6z4e.js";
-import"./index-84k9zzv1.js";
+import"./index-kphy4we7.js";
 import"./index-2s7dvzff.js";
-import"./index-qh93qjc2.js";
-import"./index-ndec8akq.js";
-import"./index-5rkh69f3.js";
-import"./index-e8k0v19e.js";
+import"./index-6183at3v.js";
+import"./index-gc0aeth5.js";
+import"./index-4gmxdkcd.js";
+import"./index-xmbtwtgw.js";
 import"./index-t7hmqgjy.js";
-import"./index-mtqwyjrg.js";
+import"./index-7rtq2t5n.js";
 import"./index-fzpt2djt.js";
 import"./index-ejhxgyvm.js";
 import"./index-7g4c7s5r.js";
-import"./index-hfssjyxs.js";
+import"./index-yf2z4j7s.js";
 import"./index-zxdawwc7.js";
-import"./index-py8wpe81.js";
+import"./index-hqrkr9ag.js";
 import"./index-gknz3bv1.js";
 import"./index-zpsr8rpc.js";
 import"./index-9rwhas09.js";

package/dist/cli/{config-doctor-3ghvthh5.js → config-doctor-vetg215g.js}

@@ -21,36 +21,36 @@ import {
   shouldRunOnStartup,
   writeBackupArtifact,
   writeDoctorArtifact
-} from "./index-4mq8r4be.js";
-import"./index-he2nyr7x.js";
+} from "./index-gns3gc87.js";
+import"./index-epdzvp4w.js";
 import"./index-6b295cas.js";
-import"./index-bgtfvst1.js";
+import"./index-peyz4k9k.js";
 import"./index-v3bmwmqw.js";
-import"./index-4gacy6y6.js";
+import"./index-z59414gv.js";
 import"./index-m9zzj4ee.js";
-import"./index-84k9zzv1.js";
+import"./index-kphy4we7.js";
 import"./index-2s7dvzff.js";
 import"./index-0725jpp7.js";
-import"./index-5ev6f1gj.js";
-import"./index-qh93qjc2.js";
-import"./index-vg8sxg12.js";
-import"./index-0e318vgt.js";
+import"./index-1hcjxz6w.js";
+import"./index-6183at3v.js";
+import"./index-crz772sx.js";
+import"./index-app2rmxv.js";
 import"./index-ry16d01s.js";
 import"./index-rdm3px0g.js";
 import"./index-7pmbnjvj.js";
-import"./index-ndec8akq.js";
-import"./index-e8k0v19e.js";
+import"./index-gc0aeth5.js";
+import"./index-xmbtwtgw.js";
 import"./index-t7hmqgjy.js";
-import"./index-mtqwyjrg.js";
+import"./index-7rtq2t5n.js";
 import"./index-fzpt2djt.js";
 import"./index-ejhxgyvm.js";
 import"./index-7g4c7s5r.js";
-import"./index-hfssjyxs.js";
+import"./index-yf2z4j7s.js";
 import"./index-gx2vp8gx.js";
-import"./index-ngk8hpc3.js";
+import"./index-c6hyd8hg.js";
 import"./index-zxdawwc7.js";
-import"./index-1dx5zyss.js";
-import"./index-py8wpe81.js";
+import"./index-jn4mmhqc.js";
+import"./index-hqrkr9ag.js";
 import"./index-bk5tah7q.js";
 import"./index-gknz3bv1.js";
 import"./index-zpsr8rpc.js";

package/dist/cli/{core-0k7t9fw0.js → core-8qgvsm6x.js}

@@ -14,13 +14,13 @@ import {
   resolveWorktreeBaseDir,
   shortenWorktreePath,
   writeLaneProfileToDiskReal
-} from "./index-x2phyvcv.js";
-import"./index-84k9zzv1.js";
+} from "./index-479kf368.js";
+import"./index-kphy4we7.js";
 import"./index-2s7dvzff.js";
 import"./index-fzpt2djt.js";
-import"./index-hfssjyxs.js";
+import"./index-yf2z4j7s.js";
 import"./index-zxdawwc7.js";
-import"./index-py8wpe81.js";
+import"./index-hqrkr9ag.js";
 import"./index-zpsr8rpc.js";
 import"./index-zgwm4ryv.js";
 import"./index-a76rekgs.js";

package/dist/cli/{curation-policy-8j6qn6nt.js → curation-policy-5hm6328s.js}

@@ -5,18 +5,18 @@ import {
   authorizeCuration,
   buildConfigFingerprintInput,
   readCohortConfigFingerprint
-} from "./index-w2vbaczx.js";
+} from "./index-hy2fqapm.js";
 import"./index-rtry5xyf.js";
 import"./index-vzm6zre7.js";
-import"./index-3atkcqpb.js";
-import"./index-5rkh69f3.js";
-import"./index-e8k0v19e.js";
+import"./index-ry5g9s8d.js";
+import"./index-4gmxdkcd.js";
+import"./index-xmbtwtgw.js";
 import"./index-t7hmqgjy.js";
-import"./index-mtqwyjrg.js";
+import"./index-7rtq2t5n.js";
 import"./index-fzpt2djt.js";
 import"./index-ejhxgyvm.js";
 import"./index-7g4c7s5r.js";
-import"./index-hfssjyxs.js";
+import"./index-yf2z4j7s.js";
 import"./index-gknz3bv1.js";
 import"./index-zpsr8rpc.js";
 import"./index-zgwm4ryv.js";

package/dist/cli/{curator-drift-a5142x0d.js → curator-drift-3gjycbkv.js}

@@ -5,23 +5,23 @@ import {
   readPriorDriftReports,
   runDeterministicDriftCheck,
   writeDriftReport
-} from "./index-d2emv8ap.js";
-import"./index-bgtfvst1.js";
-import"./index-4gacy6y6.js";
-import"./index-84k9zzv1.js";
+} from "./index-863hst4e.js";
+import"./index-peyz4k9k.js";
+import"./index-z59414gv.js";
+import"./index-kphy4we7.js";
 import"./index-2s7dvzff.js";
 import"./index-0725jpp7.js";
-import"./index-0e318vgt.js";
+import"./index-app2rmxv.js";
 import"./index-ry16d01s.js";
 import"./index-rdm3px0g.js";
 import"./index-fzpt2djt.js";
 import"./index-ejhxgyvm.js";
 import"./index-7g4c7s5r.js";
-import"./index-hfssjyxs.js";
-import"./index-ngk8hpc3.js";
+import"./index-yf2z4j7s.js";
+import"./index-c6hyd8hg.js";
 import"./index-zxdawwc7.js";
-import"./index-1dx5zyss.js";
-import"./index-py8wpe81.js";
+import"./index-jn4mmhqc.js";
+import"./index-hqrkr9ag.js";
 import"./index-bk5tah7q.js";
 import"./index-gknz3bv1.js";
 import"./index-zpsr8rpc.js";