opencode-swarm 7.136.1 → 7.136.2

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

@@ -608,7 +608,10 @@ Only exact positive verdict fields pass. A sentence containing “not APPROVE,
 header without item rows, duplicate rows, missing IDs, degraded/truncated
 artifacts, wrong roles, stale content digests, parallel or out-of-order phases,
 and reused pre-edit approvals all fail closed. Any content change after Stage A
-invalidates Stage A and every later gate; restart at step 1. Publication tools
+invalidates Stage A and every later gate; restart at step 1. See
+"Re-recording Stage A on an unchanged revision" below for the one retention
+exception, which applies only when the revision digest itself did not change.
+Publication tools
 and `git commit`/`git push` remain blocked until all four ordered lane phases
 settle on the Stage-A digest. After they settle, only one standalone `git commit`
 command may create the reviewed commit; push and remote publication remain
@@ -704,6 +707,43 @@ full stdout/stderr is inlined instead so evidence is never lost. A successful
 run persists nothing — there is no failure evidence to recover, and the
 per-check summaries are the useful record.
 
+### Re-recording Stage A on an unchanged revision
+
+Re-recording Stage A always requires a fresh, complete receipt set on the
+current revision digest — that part is unconditional. What happens to the
+already-recorded Stage B and closeout gate batches depends on whether the
+revision digest itself changed. If the digest is unchanged from the prior
+Stage A record **and** the newly declared applicable obligations/categories
+are equal to or a superset of the prior declaration, the already-approved
+independent gate batches are retained: re-recording Stage A to add a
+previously-missed obligation, or to re-attest the same set, does not by
+itself discard Stage B and closeout work that already passed on that
+revision. A narrower obligation set than the prior declaration, or any actual
+digest change, still wipes every recorded gate batch and un-arms publication
+exactly as before — a controller cannot narrow what it declares in order to
+dodge re-verification.
+
+### Why gate evidence is not item-scoped
+
+Stage A, Stage B, and closeout evidence invalidate as whole gate batches, not
+per feedback item, and that is a deliberate design decision, not unfinished
+work:
+
+- **No trustworthy item-to-file mapping exists to key invalidation on.** The
+  file scope a caller declares for a feedback item is caller-asserted and
+  only path-sanitized — it is never intersected with the actual changed-file
+  set, and it carries no persisted binding back to feedback item IDs. Keying
+  invalidation on that declaration would let a controller dodge
+  re-verification by under-declaring scope, turning a fail-closed guarantee
+  into a fail-open one (AGENTS.md invariant 9) — the same failure class that
+  already ruled out keying digest invalidation on `git diff --raw` blob OIDs.
+- **The four gate phases are holistic by contract.** Each recorded batch must
+  own every inventory item exactly once and in declared order. Retaining
+  evidence for a subset of items per gate would re-partition that
+  independent-review contract itself, and would need its own
+  collusion/independence analysis before it could be trusted — it is not a
+  drop-in extension of the revision-level retention above.
+
 ### Stage B — reviewer + test_engineer (mandatory after Stage A passes)
 
 Two independent agents on the Stage-A-green diff, run in order: **reviewer

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

@@ -757,9 +757,9 @@ never which review dimensions or risk families get evaluated:
 
 | Tier | Diff shape | Dispatch shape (Profiles B/C) |
 |---|---|---|
-| S | ≤ ~50 changed lines, ≤ 3 files, no risk triggers | Consolidate: 1–2 explorer lanes covering all six dimensions (B), or one candidate-generation pass (C); Phase 4 risk families fold into the same lanes as an explicit per-family checklist |
-| M | ≤ ~500 changed lines, or any risk trigger | Dedicated lanes for the triggered dimensions/families; consolidate the remaining thin dimensions into 1–2 lanes |
-| L | > ~500 changed lines, > ~20 files, multi-subsystem, or security-sensitive surface | Full fan-out: one lane per dimension (six) and per-family micro dispatch in Phase 4 |
+| S | ≤ ~100 changed lines, ≤ 5 files, no risk triggers | Consolidate: 1–2 explorer lanes covering all six dimensions (B), or one candidate-generation pass (C); Phase 4 risk families fold into the same lanes as an explicit per-family checklist |
+| M | ≤ ~1500 changed lines, or any risk trigger | Dedicated lanes for the triggered dimensions/families; consolidate the remaining thin dimensions into 1–2 lanes |
+| L | > ~1500 changed lines, > ~50 files, multi-subsystem, or security-sensitive surface | Full fan-out: one lane per dimension (six) and per-family micro dispatch in Phase 4 |
 
 Risk triggers (any one escalates to at least tier M, and the triggered
 dimension/family always gets a dedicated lane at M and above):
@@ -775,14 +775,29 @@ cost, or predicted simplicity — permits fewer lanes than the classified tier,
 and no tier permits skipping a dimension or family. Under Profile A the
 controller computes the tier itself from the bound `base_sha...pr_head_sha`
 diff (`--numstat` totals; an uncomputable diff fails strict to tier L) and
-mechanically enforces the matching floors on every base and micro batch —
-initial waves and retries alike: tier L requires the historical
-full fan-out (six singleton base lanes, one micro-lane per family, on every
-batch, not only the first), while
-tiers S and M accept consolidated lanes that declare their complete
-`owned_workflow_lanes` set — every dimension and family still owned exactly
-once and attested per family. Risk triggers remain caller-side escalation on
-every profile: dispatch MORE than the floor whenever a trigger warrants it.
+mechanically enforces the matching floors on every base and micro batch. The
+initial base wave and every micro batch keep the historical tier-L full
+fan-out (six singleton base lanes on the initial base wave; one micro-lane
+per family on every micro batch, not only the first), while tiers S and M
+accept consolidated lanes that declare their complete `owned_workflow_lanes`
+set — every dimension and family still owned exactly once and attested per
+family. A tier-L base **retry** may consolidate dimensions that each have a
+recorded, terminally-failed prior attempt and currently have no successful
+source, subject to two lane floors: no single lane may own all six
+dimensions, and — counted cumulatively across every recorded base batch, not
+per batch, and including batches the capacity GC has since dropped — the six
+dimensions must stay backed by at least four distinct lanes (each dimension
+no consolidated lane claims counts as one, plus the FEWEST declared
+consolidated lanes that suffice to cover the rest). That permits a small
+consolidation as failure recovery and rejects re-doing the whole wave in two
+or three lanes, whether the attempt is split across several batches or
+disguised as overlapping or duplicate consolidations — declaring more lanes
+than the cover needs buys no budget. A dimension that already has a
+successful source, or whose prior attempt is still in flight, still requires
+its own dedicated retry lane, and
+a full six-lane singleton re-dispatch is always accepted. Risk triggers
+remain caller-side escalation on every profile: dispatch MORE than the floor
+whenever a trigger warrants it.
 
 ### Dispatch
 
@@ -1295,23 +1310,47 @@ machine enforcement cannot safely infer every repository-specific trust
 boundary from prose. Completion is blocked until that exact derived inventory
 has valid critic rows.
 
-Reviewer and critic retries cannot be combined as complementary partial verdict
-sets. Each phase requires at least one fully successful exact batch covering its
-entire mechanically assigned inventory on one revision. A later degraded,
-truncated, stale, wrong-identity, or malformed batch cannot replace an earlier
-valid batch or suppress critic routing.
-
-Any newer reviewer batch invalidates every older critic batch, even when the
-new reviewer rows happen to be identical. Dispatch a fresh critic wave from the
-latest coherent reviewer batch; critic evidence can never predate the reviewer
-evidence it purports to challenge.
+Reviewer and critic settlement compose across batches, item by item: a phase
+settles once every review item in the current mechanically assigned inventory
+holds a successful verdict, whether that coverage comes from one batch or from
+several complementary partial retries. A later degraded, truncated, stale,
+wrong-identity, or malformed batch never supplies a verdict for the items it
+touches, but it does not discard verdicts other batches already supplied for
+different items.
+
+When more than one successful batch covers the same item, the most recent
+successful batch wins that item. This conflict rule is one shared computation,
+so settlement and every downstream verdict use (candidate inventory, critic
+routing, final synthesis) never disagree about which claim is authoritative
+for an item. A batch contributes only when it was validated against the exact
+candidate inventory current at validation time; a batch recorded before that
+binding existed contributes only if it is wholly successful and its item set
+exactly matches the current inventory — the historical all-or-nothing rule,
+preserved unchanged for state that predates composition.
+
+A critic claim is bound per item to the exact reviewer row it was validated
+against, not to the reviewer batch as a whole. A reviewer retry that
+reproduces a byte-identical row for an item retains that item's critic work;
+a reviewer row that changed at all — even one field — invalidates only that
+item's critic claim, not the whole critic wave. Critic batches recorded
+before per-item binding existed keep the old behavior: any newer reviewer
+batch invalidates them wholesale. Dispatch a fresh critic wave to cover
+whatever items composition leaves unclaimed; critic evidence can never
+predate the reviewer evidence it purports to challenge.
+
+Settlement is item completeness, not lane completeness: a declared lane that
+never completes produces a diagnostic naming the abandoned lane, not an
+automatic block, as long as every item in the inventory already holds a
+successful verdict from some lane.
 
 Under Profile A, dispatch critic chunks with `dispatch_lanes_async`,
 `mode: "swarm-pr-review:critic"`, a unique non-empty `workflow_lane` per
 chunk, `review_item_ids` containing the exact finding IDs assigned to that
 chunk, critic-role agents only, and the same exact `pr_head_sha`. The runtime
 requires one parseable `[CRITIC]` row for every structurally assigned ID and
-requires one coherent fully successful exact reviewer batch before a critic wave.
+requires the reviewer phase to have settled — every item in the current
+inventory holding a successful reviewer verdict, composed across batches —
+before a critic wave.
 Under Profile B, dispatch each critic chunk to a fresh subagent that was
 neither the explorer nor the reviewer for those findings; under Profile C, run
 a separate critic pass. The one-parseable-`[CRITIC]`-row-per-assigned-ID
@@ -1744,8 +1783,17 @@ checkout …` is repeatedly rejected as read-only shell syntax (the runtime
 requires each git intake command to be a single standalone command), when
 the PR ref is missing, or when the working tree is on the wrong branch and
 the merge-base bind can never verify. In that state the response gate
-suspends further auto-resumes after a small number of consecutive
-unproductive wakes, and the only exits are:
+suspends further auto-resumes for either of two independent reasons: a
+small number of consecutive unproductive wakes (the durable gate `revision`
+did not advance), or the total wake ceiling being reached (tier-scaled
+defaults S=12 / M=54 / L=102, overridable via the `totalWakeCeiling`
+option, and in-memory/per-process so the count resets on plugin reload and
+when the durable gate clears — but NOT across the PR_REVIEW → PR_FEEDBACK
+handoff, which keeps accumulating). Either suspension appends a
+`pr_workflow_wake_suspended` record to `.swarm/events.jsonl` naming the
+reason, both counters, the tier, and the ceiling in force — read that first
+when diagnosing why a review stopped resuming. Either way, the only exits
+are:
 
 1. **Diagnose and retry the canonical standalone sequence.** Run
    `git fetch origin refs/pull/<N>/head`, verify

package/README.md

@@ -37,6 +37,7 @@ Most AI coding tools let one model write code and ask that same model whether th
 - 🔎 **Independent auto-review engine** — bounded whole-diff review in a fresh read-only model session, structured diff-anchored findings, optional independent validation, advisory-by-default phase review, and an evidence-backed opt-in completion gate. v7 remains opt-in; v8's default is pinned to a committed 30-diff cost burn-in.
 - 🔍 **DEEP_DIVE Protocol** — High-rigor, on-demand read-only codebase audit via specialized skills
 - 🔬 **External Skill Curation Pipeline** — Opt-in discovery, quarantine, evaluation, and promotion of external skill candidates from configured sources (disabled by default; enable via `external_skills.curation_enabled: true` in config). Includes 7 tools: `external_skill_discover`, `external_skill_list`, `external_skill_inspect`, `external_skill_promote`, `external_skill_reject`, `external_skill_delete`, `external_skill_revoke`. Candidates pass through a 3-gate validation pipeline before evaluation: **prompt injection scan** (12 regex patterns), **unsafe instruction scan** (25 patterns), and **provenance integrity check** (SHA-256, timestamp, URL, publisher, and hash verification).
+- 🎯 **Governed Skill Optimizer** — Manually-activated, single-skill optimizer (`/swarm skill-opt plan|run|status|diff|approve|reject|rollback|history`) that drives one allowlisted `SKILL.md` candidate at a time through deterministic draft → smoke → evaluation-substrate validation → manual approval → atomic activation/rollback. Bounded, restartable, reversible, and unable to mutate source/harness/security surfaces. Disabled by default (`skill_opt.enabled: false`); see [docs/skill-optimizer.md](docs/skill-optimizer.md).
 - 🔄 **Phase completion gates** — completion-verify and drift verifier gates enforced before phase completion
 - 🔁 **Resumable sessions** — all state saved to `.swarm/`; pick up any project any day
 - 🖥️ **PR Monitor** — GitHub PR subscription and background polling via `gh` CLI; delivers real-time CI, review, and merge status updates via the AutomationEventBus (FR-001, opt-in via `pr_monitor.enabled: true`). Subscribe with `/swarm pr subscribe <pr-url|owner/repo#N|N>`; unsubscribe with `/swarm pr unsubscribe <pr-url|owner/repo#N|N>`; check status with `/swarm pr status`. With `auto_pr_feedback: true`, CI failures and merge conflicts mechanically activate PR_FEEDBACK only when no other workflow owns the session; otherwise they are durably queued for a later round.
@@ -637,6 +638,19 @@ Seven skill-management tools (`skill_generate`, `skill_list`, `skill_apply`, `sk
 
 - **Proposal cleanup** — When a draft skill proposal is activated via `skill_apply`, the source proposal file is deleted as part of the activation process (best-effort; permission errors are logged but do not block activation).
 
+### Governed Skill Optimizer
+
+`/swarm skill-opt` (issue #1822 — SkillOpt 3/7) is a **manually-activated, governed** optimizer that drives ONE allowlisted `SKILL.md` candidate at a time through deterministic draft → static smoke → evaluation-substrate validation (`split:'test'`) → manual approval → atomic activation (or rollback). The loop is bounded, restartable, reversible, and unable to mutate harness/source/security surfaces.
+
+Commands: `/swarm skill-opt plan|run|status|diff|approve|reject|rollback|history`.
+
+- **Disabled by default.** `/swarm skill-opt run` requires `skill_opt.enabled: true` AND `--confirm`. `plan`/`status`/`diff`/`history` are always available (read-only / proposal-only).
+- **No autonomous mutation.** `approve`/`activate`/`reject`/`rollback` are human-only and require `--expected-content-hash` to refuse a stale base.
+- **Validation reuse.** Uses the existing evaluation substrate (`evaluateCandidateV1`) — no duplicate runner/scorer. Held-out test sets are single-use (`claimHeldOutTest`), so a single `run` performs at most one validation.
+- **Durable lifecycle.** Append-only state machine under `.swarm/evolution/skills/<slug>/<candidateId>/` with hash-chain integrity and corrupt-tail quarantine.
+
+See `docs/skill-optimizer.md` for the full architecture and the `skill_opt` config block.
+
 ### External Skill Curation
 
 Swarm provides an opt-in, quarantine-first pipeline for discovering, validating, and promoting external skills. Disabled by default — no network calls are made until explicitly enabled.
@@ -711,6 +725,10 @@ Every candidate passes a 3-gate pipeline before entering quarantine:
 | `context_budget.unified_injection_tokens` | number | `undefined` | Opt-in unified ceiling (tokens) for combined system-enhancer + knowledge-injector injection per turn. When set, both hooks share this budget with proportional split |
 | `context_budget.tool_output_mask_threshold` | number | `2000` | Threshold for masking tool outputs (chars) |
 | `skills.enabled` | boolean | `false` | Gates the 7 skill-management tools (`skill_generate`, `skill_list`, `skill_apply`, `skill_inspect`, `skill_regenerate`, `skill_retire`, `skill_improve`) behind an opt-in flag. When `false` (default), these tools are hidden from the architect's tool map. |
+| `skill_opt.enabled` | boolean | `false` | Master opt-in for the governed skill optimizer (`/swarm skill-opt`). `run` also requires `--confirm`; `plan`/`status`/`diff`/`history` are always available. See `docs/skill-optimizer.md`. |
+| `skill_opt.deadband` | number | `0` | Promotion policy deadband forwarded to the evaluation substrate. |
+| `skill_opt.max_rounds` | number | `5` | Hard cap on draft/smoke retries before a validation (held-out test set is single-use). |
+| `skill_opt.max_transient_retries` | number | `5` | Max transient-infra retries before an infra failure becomes inconclusive. |
 | `context_budget.scoring.enabled` | boolean | `false` | Enable context scoring/ranking |
 | `context_budget.scoring.max_candidates` | number | `100` | Maximum items to score (10-500) |
 | `context_budget.scoring.weights` | object | `{ recency: 0.3, ... }` | Scoring weights for priority |

package/dist/background/workspace-snapshot.d.ts

@@ -120,18 +120,49 @@ export declare function resolvePrFeedbackTrackingCandidatesAsync(directory: stri
 } | null>;
 /** Run the exact array-form switch selected by the controller. */
 export declare function switchPrFeedbackTrackingCandidateAsync(directory: string, candidate: PrFeedbackTrackingCandidate): Promise<boolean>;
+/**
+ * Discriminated result for the revision-digest twins (issue #1968 P6). A
+ * bare `null` on any failure made the digest cap a dead end: a gate consumer
+ * could not tell "revision too large" (a bound the operator can act on) from
+ * "Git failed" or "output truncated" (an environment problem). `detail` is a
+ * best-effort human-readable diagnostic and is not part of the failure
+ * contract; only `reason` is.
+ */
+export type RevisionDigestFailureReason = 'file-cap' | 'byte-cap' | 'buffer-truncated' | 'timeout' | 'git-failed' | 'containment' | 'read-failed';
+export type RevisionDigestResult = {
+    ok: true;
+    digest: string;
+} | {
+    ok: false;
+    reason: RevisionDigestFailureReason;
+    detail?: string;
+};
 /**
  * Bind a mutable working tree to its actual content, not merely porcelain status.
  * This lets PR-feedback approvals fail closed when a same-path edit occurs after a
  * gate. Paths come from Git, are containment-checked, and are hashed without
  * following symlinks outside the project.
+ *
+ * This is the one implementation of the sync digest; {@link
+ * resolvePrWorkflowRevisionDigest} is a thin `.ok ? digest : null` delegate
+ * that preserves the pre-existing signature/behavior for existing callers.
  */
+export declare function resolvePrWorkflowRevisionDigestDetailed(directory: string, baseHeadSha: string): RevisionDigestResult;
 export declare function resolvePrWorkflowRevisionDigest(directory: string, baseHeadSha: string): string | null;
 /**
  * Asynchronously bind a mutable working tree to its actual content. File
  * reads are chunked with bounded cooperative yields so a large, permitted
  * revision cannot stall the synchronous plugin gate path.
+ *
+ * This is the one implementation of the async digest; {@link
+ * resolvePrWorkflowRevisionDigestAsync} is a thin `.ok ? digest : null`
+ * delegate that preserves the pre-existing signature/behavior for existing
+ * callers. Sequenced after P2 (see issue #1968 05-fix-plan.md P6.4): the sync
+ * twin above has no chunking/yield, so enlarging its `readFileSync` loop
+ * before P2 threads the digest through a single gate-entry-point resolve
+ * would have worsened blocking on the production path.
  */
+export declare function resolvePrWorkflowRevisionDigestDetailedAsync(directory: string, baseHeadSha: string): Promise<RevisionDigestResult>;
 export declare function resolvePrWorkflowRevisionDigestAsync(directory: string, baseHeadSha: string): Promise<string | null>;
 /** Parse `git status --porcelain=v1 -z`, including both sides of renames. */
 export declare function parsePorcelainPaths(output: string): string[] | null;
@@ -174,5 +205,28 @@ export declare const _internals: {
     gitTimeoutMs: number;
     yieldControl: () => Promise<void>;
     parsePorcelainV2Snapshot: typeof parsePorcelainV2Snapshot;
+    /**
+     * Revision-digest bound seams (issue #1968 P6). Defaults mirror the
+     * top-level constants; tests lower these to deterministically produce
+     * `file-cap` / `byte-cap` / `buffer-truncated` against small real temp
+     * git repos instead of materializing tens of thousands of real files.
+     */
+    revisionMaxFiles: number;
+    revisionMaxTotalBytes: number;
+    gitSnapshotMaxBuffer: number;
+    revisionEnumerationTimeoutMs: number;
+    /**
+     * The synchronous digest's changed-file content read, behind the same kind
+     * of seam as `spawnSync` above. The `read-failed` reason it guards has no
+     * portable filesystem trigger: Windows normalizes every crafted-path failure
+     * (nested-under-a-file, reserved characters, over-length) to `ENOENT`, which
+     * this code deliberately treats as "deleted, keep hashing", and `chmod` is a
+     * no-op there — so without this seam the sync twin's `read-failed` arm is
+     * unreachable from a test while remaining reachable in production (EACCES,
+     * EIO, a vanished mount). The async twin needs no equivalent: its chunked
+     * reader reaches `read-failed` through the short-read branch, which a test
+     * drives via the existing `yieldControl` seam.
+     */
+    readChangedFileSync: (filePath: string) => Buffer;
 };
 export {};

package/dist/cli/{config-doctor-6fphg5xm.js → config-doctor-b67nb84b.js}

@@ -12,8 +12,8 @@ import {
   shouldRunOnStartup,
   writeBackupArtifact,
   writeDoctorArtifact
-} from "./index-gf7hqbmz.js";
-import"./index-r9v98d0y.js";
+} from "./index-7ayaq27q.js";
+import"./index-y0xaq4f3.js";
 import"./index-bk5tah7q.js";
 import"./index-3jcyn8g6.js";
 import"./index-bpmtbmy9.js";

package/dist/cli/{curation-policy-m24jbyag.js → curation-policy-kvzhfaj1.js}

@@ -4,9 +4,9 @@ import {
   authorizeCuration,
   buildConfigFingerprintInput,
   readCohortConfigFingerprint
-} from "./index-jwrydqjp.js";
+} from "./index-rw3f73aq.js";
 import"./index-rtry5xyf.js";
-import"./index-kzc2ygea.js";
+import"./index-84nz7bhe.js";
 import"./index-ae75rja9.js";
 import"./index-dzyjb33e.js";
 import"./index-ey29aap6.js";

package/dist/cli/{curator-llm-factory-w5arq7tr.js → curator-llm-factory-x7kvry9x.js}

@@ -1,33 +1,36 @@
 // @bun
 import {
   createCuratorLLMDelegate
-} from "./index-prnjt2jr.js";
+} from "./index-sr2cynyw.js";
 import"./index-vm4xw9z3.js";
-import"./index-tfa40hwb.js";
-import"./index-gf7hqbmz.js";
-import"./index-cggqh2dz.js";
+import"./index-wjm896ey.js";
+import"./index-m5fw4mer.js";
+import"./index-7ayaq27q.js";
+import"./index-kwwxevne.js";
+import"./index-z1tm47nj.js";
+import"./index-y8552snf.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
-import"./index-1sq47n6t.js";
-import"./index-h3bweb88.js";
-import"./index-9gxp450h.js";
+import"./index-ad6j0m7k.js";
+import"./index-21115szq.js";
+import"./index-1kn24ja0.js";
 import"./index-6mjf4vr1.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
-import"./index-y6a7gjtj.js";
+import"./index-wsdnttf4.js";
 import"./index-mrtms113.js";
-import"./index-dyy3hvk3.js";
-import"./index-jwrydqjp.js";
+import"./index-s0rbdp61.js";
+import"./index-rw3f73aq.js";
 import"./index-rtry5xyf.js";
-import"./index-hzkvbycn.js";
-import"./index-kzc2ygea.js";
+import"./index-0755132s.js";
+import"./index-84nz7bhe.js";
 import"./index-ae75rja9.js";
 import"./index-dzyjb33e.js";
 import"./index-ey29aap6.js";
-import"./index-p1pqqwgp.js";
+import"./index-s0vahtdm.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
-import"./index-r9v98d0y.js";
+import"./index-y0xaq4f3.js";
 import"./index-bk5tah7q.js";
 import"./index-8fwhhayc.js";
 import"./index-q1exe2b3.js";

package/dist/cli/{curator-zrt5sqj2.js → curator-nrmj8bds.js}

@@ -14,33 +14,36 @@ import {
   runCuratorInit,
   runCuratorPhase,
   writeCuratorSummary
-} from "./index-prnjt2jr.js";
+} from "./index-sr2cynyw.js";
 import"./index-vm4xw9z3.js";
-import"./index-tfa40hwb.js";
-import"./index-gf7hqbmz.js";
-import"./index-cggqh2dz.js";
+import"./index-wjm896ey.js";
+import"./index-m5fw4mer.js";
+import"./index-7ayaq27q.js";
+import"./index-kwwxevne.js";
+import"./index-z1tm47nj.js";
+import"./index-y8552snf.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
-import"./index-1sq47n6t.js";
-import"./index-h3bweb88.js";
-import"./index-9gxp450h.js";
+import"./index-ad6j0m7k.js";
+import"./index-21115szq.js";
+import"./index-1kn24ja0.js";
 import"./index-6mjf4vr1.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
-import"./index-y6a7gjtj.js";
+import"./index-wsdnttf4.js";
 import"./index-mrtms113.js";
-import"./index-dyy3hvk3.js";
-import"./index-jwrydqjp.js";
+import"./index-s0rbdp61.js";
+import"./index-rw3f73aq.js";
 import"./index-rtry5xyf.js";
-import"./index-hzkvbycn.js";
-import"./index-kzc2ygea.js";
+import"./index-0755132s.js";
+import"./index-84nz7bhe.js";
 import"./index-ae75rja9.js";
 import"./index-dzyjb33e.js";
 import"./index-ey29aap6.js";
-import"./index-p1pqqwgp.js";
+import"./index-s0vahtdm.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
-import"./index-r9v98d0y.js";
+import"./index-y0xaq4f3.js";
 import"./index-bk5tah7q.js";
 import"./index-8fwhhayc.js";
 import"./index-q1exe2b3.js";

package/dist/cli/{evidence-summary-service-w006jnpg.js → evidence-summary-service-cf8sz2bq.js}

@@ -6,7 +6,9 @@ import {
   loadPlanJsonOnly,
   mergeDurableGateEntriesFromEvidence,
   readDurableGateEvidence
-} from "./index-cggqh2dz.js";
+} from "./index-kwwxevne.js";
+import"./index-z1tm47nj.js";
+import"./index-y8552snf.js";
 import"./index-9ss2m4rs.js";
 import"./index-mrtms113.js";
 import"./index-ey29aap6.js";

package/dist/cli/{guardrail-explain-462jwhbh.js → guardrail-explain-5kd44rcj.js}

@@ -1,34 +1,37 @@
 // @bun
 import {
   handleGuardrailExplain
-} from "./index-zkddc5ye.js";
-import"./index-prnjt2jr.js";
+} from "./index-azghvnja.js";
+import"./index-sr2cynyw.js";
 import"./index-vm4xw9z3.js";
-import"./index-tfa40hwb.js";
-import"./index-gf7hqbmz.js";
-import"./index-cggqh2dz.js";
+import"./index-wjm896ey.js";
+import"./index-m5fw4mer.js";
+import"./index-7ayaq27q.js";
+import"./index-kwwxevne.js";
+import"./index-z1tm47nj.js";
+import"./index-y8552snf.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
-import"./index-1sq47n6t.js";
-import"./index-h3bweb88.js";
-import"./index-9gxp450h.js";
+import"./index-ad6j0m7k.js";
+import"./index-21115szq.js";
+import"./index-1kn24ja0.js";
 import"./index-6mjf4vr1.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
-import"./index-y6a7gjtj.js";
+import"./index-wsdnttf4.js";
 import"./index-mrtms113.js";
-import"./index-dyy3hvk3.js";
-import"./index-jwrydqjp.js";
+import"./index-s0rbdp61.js";
+import"./index-rw3f73aq.js";
 import"./index-rtry5xyf.js";
-import"./index-hzkvbycn.js";
-import"./index-kzc2ygea.js";
+import"./index-0755132s.js";
+import"./index-84nz7bhe.js";
 import"./index-ae75rja9.js";
 import"./index-dzyjb33e.js";
 import"./index-ey29aap6.js";
-import"./index-p1pqqwgp.js";
+import"./index-s0vahtdm.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
-import"./index-r9v98d0y.js";
+import"./index-y0xaq4f3.js";
 import"./index-bk5tah7q.js";
 import"./index-8fwhhayc.js";
 import"./index-q1exe2b3.js";

package/dist/cli/{guardrail-log-ax21jd9e.js → guardrail-log-aksrzqdx.js}

@@ -1,9 +1,9 @@
 // @bun
 import {
   handleGuardrailLog
-} from "./index-g7g4hqh3.js";
-import"./index-tfa40hwb.js";
-import"./index-r9v98d0y.js";
+} from "./index-37v2wxqe.js";
+import"./index-m5fw4mer.js";
+import"./index-y0xaq4f3.js";
 import"./index-bk5tah7q.js";
 import"./index-3jcyn8g6.js";
 import"./index-bpmtbmy9.js";

package/dist/cli/hashing-mjwn6j4y.js

@@ -0,0 +1,34 @@
+// @bun
+import {
+  _internals,
+  canonicalHash,
+  canonicalJson,
+  computeCandidateInputContentHash,
+  computeManifestContentHash,
+  computeRunIntegrityHash,
+  computeTaskContentHash,
+  computeTaskInputContentHash,
+  computeTaskLineageInputHash,
+  computeTaskSetContentHash,
+  contentHashWithout,
+  resolveContainedExistingPath,
+  resolveContainedExistingPathAsync,
+  sha256
+} from "./index-y8552snf.js";
+import"./index-a76rekgs.js";
+export {
+  sha256,
+  resolveContainedExistingPathAsync,
+  resolveContainedExistingPath,
+  contentHashWithout,
+  computeTaskSetContentHash,
+  computeTaskLineageInputHash,
+  computeTaskInputContentHash,
+  computeTaskContentHash,
+  computeRunIntegrityHash,
+  computeManifestContentHash,
+  computeCandidateInputContentHash,
+  canonicalJson,
+  canonicalHash,
+  _internals
+};

package/dist/cli/{hive-promoter-2vacnbws.js → hive-promoter-cy21rhnd.js}

@@ -7,35 +7,38 @@ import {
   isHiveEligible,
   promoteFromSwarm,
   promoteToHive
-} from "./index-prnjt2jr.js";
+} from "./index-sr2cynyw.js";
 import"./index-vm4xw9z3.js";
-import"./index-tfa40hwb.js";
-import"./index-gf7hqbmz.js";
-import"./index-cggqh2dz.js";
+import"./index-wjm896ey.js";
+import"./index-m5fw4mer.js";
+import"./index-7ayaq27q.js";
+import"./index-kwwxevne.js";
+import"./index-z1tm47nj.js";
+import"./index-y8552snf.js";
 import"./index-4905hd2m.js";
 import"./index-134d35c1.js";
-import"./index-1sq47n6t.js";
-import"./index-h3bweb88.js";
-import"./index-9gxp450h.js";
+import"./index-ad6j0m7k.js";
+import"./index-21115szq.js";
+import"./index-1kn24ja0.js";
 import"./index-6mjf4vr1.js";
 import"./index-c8s9a3zh.js";
 import"./index-9ss2m4rs.js";
-import"./index-y6a7gjtj.js";
+import"./index-wsdnttf4.js";
 import"./index-mrtms113.js";
-import"./index-dyy3hvk3.js";
-import"./index-jwrydqjp.js";
+import"./index-s0rbdp61.js";
+import"./index-rw3f73aq.js";
 import"./index-rtry5xyf.js";
 import {
   resolveHiveKnowledgePath
-} from "./index-hzkvbycn.js";
-import"./index-kzc2ygea.js";
+} from "./index-0755132s.js";
+import"./index-84nz7bhe.js";
 import"./index-ae75rja9.js";
 import"./index-dzyjb33e.js";
 import"./index-ey29aap6.js";
-import"./index-p1pqqwgp.js";
+import"./index-s0vahtdm.js";
 import"./index-k5jrywpr.js";
 import"./index-n832052r.js";
-import"./index-r9v98d0y.js";
+import"./index-y0xaq4f3.js";
 import"./index-bk5tah7q.js";
 import"./index-8fwhhayc.js";
 import"./index-q1exe2b3.js";

package/dist/cli/{index-hzkvbycn.js → index-0755132s.js}

@@ -702,7 +702,7 @@ async function applyConfidenceFloorAction(directory, touched, options) {
   const recovered = touched.filter((e) => e.confidence > CONFIDENCE_FLOOR + FLOOR_EPSILON && e.confidence_floor_demoted);
   if (atFloor.length === 0 && recovered.length === 0)
     return;
-  const { readKnowledgeCounterRollups, effectiveRetrievalOutcomes } = await import("./knowledge-events-ej3s9tsm.js");
+  const { readKnowledgeCounterRollups, effectiveRetrievalOutcomes } = await import("./knowledge-events-dk6banmz.js");
   const rollups = await readKnowledgeCounterRollups(directory);
   const flagIds = new Set;
   for (const e of atFloor) {
@@ -769,11 +769,11 @@ async function applyConfidenceFloorAction(directory, touched, options) {
     });
   }
   if (action === "quarantine" && toQuarantine.length > 0) {
-    const { quarantineEntry } = await import("./knowledge-validator-zwmq7s2c.js");
-    const { KnowledgeConfigSchema } = await import("./schema-mhd7xqwr.js");
+    const { quarantineEntry } = await import("./knowledge-validator-jsz1dxkr.js");
+    const { KnowledgeConfigSchema } = await import("./schema-f937b9cs.js");
     let config;
     try {
-      const { loadPluginConfigWithMeta } = await import("./index-f4cmtd89.js");
+      const { loadPluginConfigWithMeta } = await import("./index-wnz282j3.js");
       const { config: loadedConfig } = loadPluginConfigWithMeta(directory);
       config = KnowledgeConfigSchema.parse(loadedConfig.knowledge ?? {});
     } catch {