@lannguyensi/harness 0.64.0 → 1.0.0

package/dist/policy-packs/builtin/post-merge-gate-runtime.js

@@ -1,397 +0,0 @@
-// Shared runtime constants + helpers for the `post-merge-gate` policy pack.
-//
-// The pack itself (`post-merge-gate.ts`) only emits hooks + the audit-copy
-// instructions. The actual enforcement lives in two CLI verbs — `harness
-// pack hook post-merge-gate-record` (producer, PostToolUse) and `harness
-// pack hook post-merge-gate` (blocker, PreToolUse) — both under `src/cli/
-// pack/`. This module is the small shared surface they pull from: the
-// merged-tag format, the curated mutation matcher, the escape allowlist,
-// and a couple of small payload/command helpers.
-//
-// Binding decisions this module encodes (see
-// .ai/runs/2026-07-23-post-merge-gate/03-decisions.md, BINDING):
-//
-//   - The merged fact is keyed on an EXACT branch-tip sha match, not
-//     ancestry. `gh pr merge` merges the PR on the remote side; it does
-//     NOT move the local branch's tip. So the local tip observed by the
-//     PostToolUse producer, right after a successful merge, IS the exact
-//     commit that got merged. The blocker denies only while the current
-//     tip still equals that recorded value — a new local commit moves the
-//     tip and the gate falls silent (deliberate: that is legitimate
-//     continued work, not stale post-merge state), and a recycled branch
-//     name with a different tip never matches either. No expiry /
-//     freshness window is needed as a result (squash-fest, offline).
-//
-//   - Deny scope v1 is a CURATED command list (git commit / add / push /
-//     merge / rebase / cherry-pick / revert / reset / stash pop|apply, gh
-//     pr create / merge), not "every Bash call" — mirrors
-//     branch-protection.ts's documented v1 scope-cut (see its "Out of
-//     scope" section). Read-only git (status/log/diff/branch) and
-//     unrelated shell are never touched.
-//
-//   - DENY WINS over the escape allowlist (task 19356be7, REVERSES the
-//     original escape-first decision): the blocker classifies a command as
-//     gate-eligible iff the curated mutation matcher fires
-//     (`isGateEligibleCommand` below). The escape allowlist no longer
-//     short-circuits the whole command — under escape-first, any chained
-//     command containing an escape verb anywhere (`harness preflight &&
-//     git push origin master`, the documented normal workflow) skipped the
-//     gate entirely. Measured before changing, over a 66-row corpus with
-//     bash ground truth: per-segment evaluation and deny-wins are
-//     0-divergent — a consequence of the pinned verb disjointness between
-//     the escape and deny lists — so the simplest (deny-wins) is
-//     implemented. The third candidate, escape-at-start-only, was measured
-//     and REJECTED: it diverges on 26 rows and still exempts three of the
-//     four lines this task exists to close (`git switch master && git push
-//     origin master` and friends). The recovery-never-starved property is preserved
-//     structurally: a non-eligible command is allowed before any manifest
-//     load or ledger query, exactly where the escape short-circuit used to
-//     sit (see hook-post-merge-gate.ts for the ordering).
-//
-//   - Fails OPEN (allows) when the ledger is unreachable, unlike
-//     branch-protection's fail-closed posture: without the ledger,
-//     "merged" and "not merged" are indistinguishable, and fail-closed
-//     here would block every feature branch's git history forever. This
-//     pack is advisory-strength against a hostile agent, same honesty as
-//     the other `requires.ledger_tag`-style gates
-//     (docs/okf/evidence-ledger-trust-boundary.md).
-import { findGitEntry, resolveCommonDir, resolveOriginHeadBase } from "../../runtime/git-context.js";
-export const PACK_NAME = "post-merge-gate";
-/**
- * Content prefix the producer writes and the blocker substring-matches.
- * The full recorded content is
- * `${MERGED_TAG_PREFIX}:${repo}:${branch}:${sha}[ pr:<n>] at:<iso>`; the
- * blocker only ever tests for the `${MERGED_TAG_PREFIX}:${repo}:${branch}:
- * ${sha}` prefix (an exact 40-hex-char sha), so the trailing `pr:` / `at:`
- * tokens are audit decoration, not part of the match key.
- */
-export const MERGED_TAG_PREFIX = "post-merge-gate:merged";
-/** The exact substring the blocker tests ledger entries for. */
-export function mergedTagMatchKey(repo, branch, sha) {
-    return `${MERGED_TAG_PREFIX}:${repo}:${branch}:${sha}`;
-}
-/** Build the full fact content the producer writes (match key + audit decoration). */
-export function buildMergedTagContent(args) {
-    const prPart = args.pr ? ` pr:${args.pr}` : "";
-    return `${mergedTagMatchKey(args.repo, args.branch, args.sha)}${prPart} at:${args.whenIso}`;
-}
-/**
- * Producer trigger: does this Bash command look like a `gh pr merge`
- * invocation? Same anchoring convention as `DEFAULT_PUSH_BASH_RE`
- * (solution-acceptance-runtime.ts): tolerates a leading `cd … &&`, inline
- * `VAR=val` assignments, and chaining. Known gap, same class as that
- * regex's own documented residual: a heredoc / `sh -c` / `eval`
- * indirection defeats this match before the producer ever runs — not
- * attempted to close here (the MCP merge path, `pull_requests_merge`, is
- * the other documented gap; see the pack's instructions.md).
- *
- * Task 76671e5a: bare `&` added to the boundary alternation (`&&` kept to
- * its left only to mirror `src/runtime/command-normalize.ts`'s alternation
- * order for readability — NOT because order is load-bearing here, unlike
- * that module). Same fix as `d834a065` applied to every policy trigger —
- * bash starts a new command after a single `&`, so `A=x&gh pr merge` used
- * to miss this trigger entirely and the producer silently never recorded
- * the merged-tip fact for that spelling. Broadening a TRIGGER only widens
- * when the producer fires (a strictly safer direction, mirrors the
- * deny-side reasoning below), unlike the escape allowlist further down.
- * Measured: swapping to `&|&&` produces a byte-identical match set for this
- * matcher (a `RegExp.test` existential check over every start offset, not a
- * segmenter — the reasoning that makes order matter in
- * `command-normalize.ts`'s `BOUNDARY_RE`/`AMP_BOUNDARY_RE` does not transfer
- * to a plain `.test()` matcher like this one).
- *
- * The RECORDER (`hook-post-merge-gate-record.ts`) does not test this regex
- * against the raw command alone: it tests it against four forms, raw first
- * and lazily, mirroring the gate's `policyMatchesEvent` arms (raw,
- * `normalizeCommand`, `normalizeCommandAmpAware`,
- * `normalizeCommandQuoteAware`). The regex itself stays anchored for the
- * raw form, so wrapper spellings (`nice gh pr merge 1`), a bare-`&` chain
- * before a wrapper and a quoted assignment value holding a boundary
- * character are matched via the normalised forms, not by this pattern.
- * Named residual: a command longer than MAX_NORMALIZE_LENGTH is not
- * normalised and is tested raw only.
- */
-export const GH_PR_MERGE_BASH_RE = /(?:^|\n|;|\||&&|&|\()\s*(?:\w+=\S+\s+)*gh\s+pr\s+merge\b/;
-/**
- * Blocker deny-scope v1 (03-decisions.md): the curated mutation command
- * list. Deliberately NOT "every Bash command" — read-only git
- * (status/log/diff/branch) and unrelated shell stay unaffected. Same
- * anchoring convention as `GH_PR_MERGE_BASH_RE`.
- *
- * Task 76671e5a: bare `&` added to the boundary alternation, same reasoning
- * as `GH_PR_MERGE_BASH_RE` above — this is a DENY-scope matcher, so
- * broadening it is the STRICTER direction (more commands recognized as
- * curated mutations, none dropped). Verified disjoint from the escape
- * allowlist below on a single-command corpus (no verb overlap), so this
- * broadening cannot lock out the documented recovery path.
- */
-export const CURATED_MUTATION_BASH_RE = /(?:^|\n|;|\||&&|&|\()\s*(?:\w+=\S+\s+)*(?:git(?:\s+-C\s+\S+)?\s+(?:commit|add|push|merge|rebase|cherry-pick|revert|reset|stash\s+(?:pop|apply))\b|gh\s+pr\s+(?:create|merge)\b)/;
-/**
- * Escape allowlist, git verbs (03-decisions.md): the exact recovery path
- * the deny message recommends, plus read-only stash inspection. Since task
- * 19356be7 this list no longer short-circuits the blocker — the deny
- * match decides gate-eligibility, and every one of these verbs stays free
- * simply because it is not a curated mutation (verb disjointness, pinned).
- * The list remains the deny message's recovery vocabulary and a
- * diagnostics aid.
- *
- * Task 76671e5a, DELIBERATELY LEFT on the old (no bare-`&`) boundary
- * alphabet: this is an ALLOW-side matcher, so broadening it is the LOOSER
- * direction. Its remaining consumers (diagnostics, docs interpolation)
- * still must not silently widen what reads as "recovery". Pinned by a
- * regression test asserting this regex's source never gains the `&|`
- * boundary token.
- */
-export const ESCAPE_GIT_BASH_RE = /(?:^|\n|;|\||&&|\()\s*(?:\w+=\S+\s+)*git(?:\s+-C\s+\S+)?\s+(?:switch\b|checkout\b|pull\b|fetch\b|branch\s+-(?:d|D)\b|stash\s+(?:list|show)\b)/;
-/**
- * Escape allowlist, harness verbs (03-decisions.md): names any invocation
- * of harness's own CLI (recovery commands like `harness session-start
- * branch-check`, diagnostics, a future self-check), regardless of
- * spelling — mirrors the `npx` / absolute-path / `./node_modules/.bin`
- * robustness the `deny-kill-switch-bash` regex in
- * `src/cli/init/templates.ts` already established for the same class of
- * bypass concern. Since task 19356be7 its only job is the deny message's
- * / diagnostics' vocabulary: a bare harness command stays free through
- * verb disjointness with the curated deny list, not through a
- * short-circuit.
- *
- * Task 76671e5a: DELIBERATELY LEFT narrow, same reasoning as
- * `ESCAPE_GIT_BASH_RE` immediately above — an allow-side matcher, so
- * broadening its boundary alphabet is the loosening direction.
- */
-export const ESCAPE_HARNESS_BASH_RE = /(?:^|\n|;|\||&&|\()\s*(?:\w+=\S+\s+)*(?:npx\s+|\S*\/)?harness\b/;
-/**
- * True when `command` matches any escape pattern. Since task 19356be7
- * this is DIAGNOSTICS ONLY — the blocker's decision is
- * `isGateEligibleCommand` below; when escape and deny both match, deny
- * wins. (Under the original escape-first ordering this function was the
- * blocker's first, unconditional check, which let `harness preflight &&
- * git push origin master` — the documented normal workflow — skip the
- * gate entirely.)
- */
-export function isEscapeCommand(command) {
-    return ESCAPE_GIT_BASH_RE.test(command) || ESCAPE_HARNESS_BASH_RE.test(command);
-}
-/** True when `command` matches the curated v1 deny-scope. */
-export function isCuratedMutationCommand(command) {
-    return CURATED_MUTATION_BASH_RE.test(command);
-}
-/**
- * The blocker's single classification entry point (task 19356be7): a
- * command is gate-eligible iff the curated mutation matcher fires.
- * Everything else — the whole recovery vocabulary, read-only git,
- * unrelated shell — is allowed by the hook BEFORE any manifest load or
- * ledger query, preserving the recovery-never-starved property the
- * escape-first ordering used to provide.
- *
- * A thin wrapper over `isCuratedMutationCommand` by DELIBERATE choice,
- * not by accident. An earlier iteration of this task pre-processed the
- * command here, stripping the bodies of quoted-delimiter heredocs fed to
- * a harness invocation, so that an `harness approve understanding <<'…'`
- * report body mentioning a mutation verb would not become gate-eligible.
- * Two review rounds found two successive families of UNDER-blocks in that
- * pre-processing (bodies consumed that bash really executes), both rooted
- * in the same cause: deciding where a heredoc body BEGINS requires
- * re-implementing bash's quote and word grammar on the permissive side of
- * a security boundary. Tasks `dbc6d303` and `5b1b24fb` had already been
- * halted for that same reason. It was therefore removed rather than
- * patched a third time; see
- * `.ai/runs/2026-08-02-post-merge-gate-escape-precedence/03-decisions.md`
- * D5/D6 for the measurement history, and task `5b1b24fb` for the real
- * fix, which belongs at the `bash_match` layer for every surface at once.
- *
- * Accepted consequence, OVER-block direction: a harness report heredoc
- * whose body carries a boundary-anchored mutation verb IS gate-eligible.
- * It only denies while the branch tip equals a recorded merged tip, and
- * `git switch <default>` — the gate's own recommended recovery — stays
- * free. Same residual class as the quoted-text false positives this
- * change already accepts. Do NOT reintroduce a strip here without a
- * design that does not re-derive bash's grammar.
- */
-export function isGateEligibleCommand(command) {
-    return isCuratedMutationCommand(command);
-}
-/**
- * Defensive `tool_output.exit_code` reader for the PostToolUse Bash
- * payload — Contract A. Returns `null` on ANY shape other than a plain
- * finite number — missing field, a differently-named variant, a string,
- * etc. — so the producer's "no fact on anything but a confirmed success"
- * rule (03-decisions.md) degrades to "no fact" rather than guessing.
- *
- * PAYLOAD REALITY (2026-07, follow-up to 03-decisions.md): live
- * verification against a real Claude Code 2.1.218 native install (a
- * `claude -p --settings` dump-hook capture, 19/19 fired events) found NO
- * `tool_output` field at all — the field is `tool_response`, shaped
- * `{ stdout, stderr, interrupted, isImage, noOutputExpected }` with no
- * exit-code equivalent (see `tests/fixtures/post-merge-gate/
- * real-posttooluse-payload-2.1.218.json`, a verbatim capture). The
- * `tool_output.stdout/stderr/exit_code` shape this function reads
- * evidently describes a DIFFERENT — newer, or differently-shimmed —
- * Claude Code contract than 2.1.218's, not a documentation error to
- * "fix" here: Contract A is left exactly as it was (any install that
- * DOES send `tool_output.exit_code` still works unchanged), and Contract
- * B below is the fallback that makes the producer fire on 2.1.218 at
- * all. See `resolveMergeConfirmation`.
- */
-export function extractExitCode(toolOutput) {
-    if (typeof toolOutput !== "object" || toolOutput === null)
-        return null;
-    const ec = toolOutput["exit_code"];
-    return typeof ec === "number" && Number.isFinite(ec) ? ec : null;
-}
-// Matches the first bare integer following `gh pr merge` — audit
-// decoration only (the deny/allow decision never depends on this).
-const PR_NUMBER_RE = /gh\s+pr\s+merge\b[^\n;|&]*?(\d+)\b/;
-/** Best-effort PR number extraction from a `gh pr merge` command string. */
-export function extractPrNumber(command) {
-    const m = PR_NUMBER_RE.exec(command);
-    return m ? m[1] : null;
-}
-/**
- * Contract B success-text matcher (2.1.218 payload-reality follow-up).
- * `gh pr merge`'s own past-tense confirmation sentence, verbatim across
- * all three merge methods.
- *
- * SOURCE (verified against the installed `gh` binary, v2.94.0,
- * `pkg/cmd/pr/merge/merge.go` lines 369-376): the success line is built
- * as `infof("%s %s pull request %s#%d (%s)", icon, action,
- * ghrepo.FullName(baseRepo), pr.Number, pr.Title)` — i.e. the repo
- * FULLNAME sits directly between "pull request" and the bare `#<n>`,
- * GLUED to the `#` with no space (`%s#%d`, not `%s #%d`):
- *
- *   ✓ Squashed and merged pull request owner/repo#65 (Some title)
- *   ✓ Rebased and merged pull request owner/repo#65 (Some title)
- *   ✓ Merged pull request owner/repo#65 (Some title)
- *
- * `infof` writes to `gh`'s STDERR (the informational-message channel,
- * distinct from `gh`'s own stdout, which is reserved for machine-
- * consumable output) — another reason this matcher tests the CONCATENATED
- * `stdout`+`stderr`, not stdout alone. `icon` is a bare `✓` (or `!` for
- * warnings) with no ANSI color codes when `gh` detects a non-TTY output
- * stream, which a hook-captured Bash hijacks it into.
- *
- * `[^\s#]*` between "pull request" and `#` accepts BOTH that real
- * `owner/repo#<n>` shape AND a bare `#<n>` (no fullname) — the latter is
- * not `gh`'s actual current wording but is accepted defensively as a
- * documentation-shape / future-`gh`-version tolerance, at zero matching-
- * surface cost (repo fullnames never contain whitespace or `#`, so the
- * character class cannot itself widen what counts as a match beyond
- * "some non-space run immediately before the PR number").
- *
- * Still deliberately narrow overall (conservative — false negatives are
- * the safe direction here, false positives are not):
- *   - exact past-tense phrase, not a bare "merged" substring — excludes
- *     `gh pr merge --auto`'s pending text (real wording, same source
- *     file: "Pull request owner/repo#65 will be automatically merged via
- *     squash when all requirements are met" — capitalized standalone
- *     "Pull request", no "Squashed/Rebased and merged" or standalone
- *     "Merged" immediately precedes it), and excludes the already-merged
- *     warning (real wording: "Pull request owner/repo#65 was already
- *     merged" — word order is reversed: "Pull request ... was already
- *     merged", not "Merged pull request ...").
- *   - case-sensitive, matching gh's own capitalization exactly (no `/i`)
- *     — narrower matching surface, same conservative direction.
- *   - `\b` word boundaries on both ends so a partial-word coincidence
- *     (e.g. a hypothetical "ReMerged") cannot match.
- *
- * KNOWN GAP (documented, not attempted to close here): this is coupled
- * to `gh`'s current wording. A future `gh` release that rephrases its
- * success sentence makes this matcher — and therefore the whole
- * Contract-B path — silently, fail-safely inert (no fact written, same
- * as any other unmatched shape; never a false "merged" record). See the
- * pack's instructions.md / docs/policy-packs/post-merge-gate.md "Known
- * gaps" for the operator-facing verification path.
- */
-export const GH_MERGE_SUCCESS_RE = /\b(?:Squashed and merged|Rebased and merged|Merged)\s+pull request\s+[^\s#]*#(\d+)\b/;
-/**
- * Contract B confirmation: does `toolResponse` carry a real Claude Code
- * 2.1.218-shaped Bash result (`{ stdout, stderr, interrupted, ... }`)
- * whose `stdout`+`stderr` contain a `gh pr merge` success sentence?
- *
- * `interrupted` must be the LITERAL boolean `false` — missing, `true`,
- * or any other value all fail closed (no match), the same fail-safe
- * direction as Contract A's exit_code check. `stdout`/`stderr` default
- * to `""` when absent or non-string (never throws), and are joined with
- * a newline before matching so a phrase cannot accidentally form by
- * concatenating the tail of one stream with the head of the other.
- */
-export function matchGhMergeSuccessText(toolResponse) {
-    if (typeof toolResponse !== "object" || toolResponse === null)
-        return { matched: false };
-    const tr = toolResponse;
-    if (tr["interrupted"] !== false)
-        return { matched: false };
-    const stdout = typeof tr["stdout"] === "string" ? tr["stdout"] : "";
-    const stderr = typeof tr["stderr"] === "string" ? tr["stderr"] : "";
-    const combined = `${stdout}\n${stderr}`;
-    const match = GH_MERGE_SUCCESS_RE.exec(combined);
-    if (!match)
-        return { matched: false };
-    return { matched: true, pr: match[1] ?? null };
-}
-/**
- * Dual-contract merge confirmation (2.1.218 payload-reality follow-up).
- * Tries Contract A (`tool_output.exit_code`, unchanged) first; falls
- * back to Contract B (`tool_response` + a matching `gh` success
- * sentence) only when Contract A yields no verdict at all.
- *
- * BINDING ordering decision — Contract A wins whenever it resolves to
- * ANY definite verdict, success OR failure: a well-formed, non-zero
- * `exit_code` is Contract A's own explicit failure signal and short-
- * circuits WITHOUT consulting Contract B, so a coincidental gh success
- * phrase sitting in a sibling `tool_response` field (the hypothetical
- * "both present" shape) can never override an authoritative failure.
- * Contract B is consulted only when `exit_code` is entirely unresolvable
- * (`extractExitCode` returns `null` — missing field, wrong shape, or the
- * field genuinely absent as on 2.1.218).
- */
-export function resolveMergeConfirmation(toolOutput, toolResponse, command) {
-    const exitCode = extractExitCode(toolOutput);
-    if (exitCode === 0) {
-        return {
-            confirmed: true,
-            contract: "exit_code",
-            pr: extractPrNumber(command),
-            reason: "tool_output.exit_code === 0 (Contract A)",
-        };
-    }
-    if (exitCode !== null) {
-        return {
-            confirmed: false,
-            contract: "none",
-            pr: null,
-            reason: `tool_output.exit_code is ${exitCode}, not 0 (Contract A reports failure; Contract B not consulted)`,
-        };
-    }
-    const ghSuccess = matchGhMergeSuccessText(toolResponse);
-    if (ghSuccess.matched) {
-        return {
-            confirmed: true,
-            contract: "gh_success_text",
-            pr: extractPrNumber(command) ?? ghSuccess.pr,
-            reason: "tool_response carries a confirmed gh merge success sentence (Contract B)",
-        };
-    }
-    return {
-        confirmed: false,
-        contract: "none",
-        pr: null,
-        reason: "no confirming tool_output.exit_code (Contract A) and no matching gh merge success text in tool_response (Contract B)",
-    };
-}
-/**
- * Best-effort default-branch name for the deny message's `git switch
- * <default>` line. Offline, reusing the same `origin/HEAD` resolution
- * `harness record review --base` uses (now shared via
- * `runtime/git-context.ts`, see that module's header). Returns `null`
- * when `cwd` is not in a git work tree, or the repo has no resolvable
- * `origin/HEAD` (e.g. no remote) — the caller falls back to a generic
- * placeholder in that case; this is advisory text, never a gate input.
- */
-export function resolveDefaultBranchName(cwd) {
-    const gitDir = findGitEntry(cwd)?.gitDir;
-    if (!gitDir)
-        return null;
-    return resolveOriginHeadBase(resolveCommonDir(gitDir));
-}
-//# sourceMappingURL=post-merge-gate-runtime.js.map

package/dist/policy-packs/builtin/post-merge-gate-runtime.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"post-merge-gate-runtime.js","sourceRoot":"","sources":["../../../src/policy-packs/builtin/post-merge-gate-runtime.ts"],"names":[],"mappings":"AAAA,4EAA4E;AAC5E,EAAE;AACF,2EAA2E;AAC3E,yEAAyE;AACzE,yEAAyE;AACzE,0EAA0E;AAC1E,sEAAsE;AACtE,yEAAyE;AACzE,iDAAiD;AACjD,EAAE;AACF,6CAA6C;AAC7C,iEAAiE;AACjE,EAAE;AACF,qEAAqE;AACrE,wEAAwE;AACxE,wEAAwE;AACxE,yEAAyE;AACzE,wEAAwE;AACxE,0EAA0E;AAC1E,oEAAoE;AACpE,yEAAyE;AACzE,kEAAkE;AAClE,qEAAqE;AACrE,EAAE;AACF,yEAAyE;AACzE,0EAA0E;AAC1E,0DAA0D;AAC1D,sEAAsE;AACtE,kEAAkE;AAClE,yCAAyC;AACzC,EAAE;AACF,uEAAuE;AACvE,2EAA2E;AAC3E,2DAA2D;AAC3D,sEAAsE;AACtE,yEAAyE;AACzE,wEAAwE;AACxE,2EAA2E;AAC3E,yEAAyE;AACzE,kEAAkE;AAClE,0EAA0E;AAC1E,iEAAiE;AACjE,2EAA2E;AAC3E,0EAA0E;AAC1E,2EAA2E;AAC3E,oFAAoF;AACpF,0EAA0E;AAC1E,2EAA2E;AAC3E,0DAA0D;AAC1D,EAAE;AACF,iEAAiE;AACjE,mEAAmE;AACnE,uEAAuE;AACvE,wEAAwE;AACxE,yEAAyE;AACzE,kDAAkD;AAClD,oDAAoD;AAEpD,OAAO,EAAE,YAAY,EAAE,gBAAgB,EAAE,qBAAqB,EAAE,MAAM,8BAA8B,CAAC;AAErG,MAAM,CAAC,MAAM,SAAS,GAAG,iBAAiB,CAAC;AAE3C;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,wBAAwB,CAAC;AAE1D,gEAAgE;AAChE,MAAM,UAAU,iBAAiB,CAAC,IAAY,EAAE,MAAc,EAAE,GAAW;IACzE,OAAO,GAAG,iBAAiB,IAAI,IAAI,IAAI,MAAM,IAAI,GAAG,EAAE,CAAC;AACzD,CAAC;AAED,sFAAsF;AACtF,MAAM,UAAU,qBAAqB,CAAC,IAMrC;IACC,MAAM,MAAM,GAAG,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC,OAAO,IAAI,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;IAC/C,OAAO,GAAG,iBAAiB,CAAC,IAAI,CAAC,IAAI,EAAE,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,GAAG,CAAC,GAAG,MAAM,OAAO,IAAI,CAAC,OAAO,EAAE,CAAC;AAC9F,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmCG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,0DAA0D,CAAC;AAE9F;;;;;;;;;;;;GAYG;AACH,MAAM,CAAC,MAAM,wBAAwB,GACnC,iLAAiL,CAAC;AAEpL;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAC7B,+IAA+I,CAAC;AAElJ;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,sBAAsB,GAAG,iEAAiE,CAAC;AAExG;;;;;;;;GAQG;AACH,MAAM,UAAU,eAAe,CAAC,OAAe;IAC7C,OAAO,kBAAkB,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,sBAAsB,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;AAClF,CAAC;AAED,6DAA6D;AAC7D,MAAM,UAAU,wBAAwB,CAAC,OAAe;IACtD,OAAO,wBAAwB,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;AAChD,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AACH,MAAM,UAAU,qBAAqB,CAAC,OAAe;IACnD,OAAO,wBAAwB,CAAC,OAAO,CAAC,CAAC;AAC3C,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,eAAe,CAAC,UAAmB;IACjD,IAAI,OAAO,UAAU,KAAK,QAAQ,IAAI,UAAU,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IACvE,MAAM,EAAE,GAAI,UAAsC,CAAC,WAAW,CAAC,CAAC;IAChE,OAAO,OAAO,EAAE,KAAK,QAAQ,IAAI,MAAM,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;AACnE,CAAC;AAED,iEAAiE;AACjE,mEAAmE;AACnE,MAAM,YAAY,GAAG,oCAAoC,CAAC;AAE1D,4EAA4E;AAC5E,MAAM,UAAU,eAAe,CAAC,OAAe;IAC7C,MAAM,CAAC,GAAG,YAAY,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;IACrC,OAAO,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAE,CAAC,CAAC,CAAC,IAAI,CAAC;AAC1B,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsDG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAC9B,sFAAsF,CAAC;AAIzF;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,uBAAuB,CAAC,YAAqB;IAC3D,IAAI,OAAO,YAAY,KAAK,QAAQ,IAAI,YAAY,KAAK,IAAI;QAAE,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;IACzF,MAAM,EAAE,GAAG,YAAuC,CAAC;IACnD,IAAI,EAAE,CAAC,aAAa,CAAC,KAAK,KAAK;QAAE,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;IAC3D,MAAM,MAAM,GAAG,OAAO,EAAE,CAAC,QAAQ,CAAC,KAAK,QAAQ,CAAC,CAAC,CAAC,EAAE,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;IACpE,MAAM,MAAM,GAAG,OAAO,EAAE,CAAC,QAAQ,CAAC,KAAK,QAAQ,CAAC,CAAC,CAAC,EAAE,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;IACpE,MAAM,QAAQ,GAAG,GAAG,MAAM,KAAK,MAAM,EAAE,CAAC;IACxC,MAAM,KAAK,GAAG,mBAAmB,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC;IACjD,IAAI,CAAC,KAAK;QAAE,OAAO,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;IACtC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,EAAE,EAAE,KAAK,CAAC,CAAC,CAAC,IAAI,IAAI,EAAE,CAAC;AACjD,CAAC;AAYD;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,wBAAwB,CACtC,UAAmB,EACnB,YAAqB,EACrB,OAAe;IAEf,MAAM,QAAQ,GAAG,eAAe,CAAC,UAAU,CAAC,CAAC;IAC7C,IAAI,QAAQ,KAAK,CAAC,EAAE,CAAC;QACnB,OAAO;YACL,SAAS,EAAE,IAAI;YACf,QAAQ,EAAE,WAAW;YACrB,EAAE,EAAE,eAAe,CAAC,OAAO,CAAC;YAC5B,MAAM,EAAE,0CAA0C;SACnD,CAAC;IACJ,CAAC;IACD,IAAI,QAAQ,KAAK,IAAI,EAAE,CAAC;QACtB,OAAO;YACL,SAAS,EAAE,KAAK;YAChB,QAAQ,EAAE,MAAM;YAChB,EAAE,EAAE,IAAI;YACR,MAAM,EAAE,4BAA4B,QAAQ,gEAAgE;SAC7G,CAAC;IACJ,CAAC;IACD,MAAM,SAAS,GAAG,uBAAuB,CAAC,YAAY,CAAC,CAAC;IACxD,IAAI,SAAS,CAAC,OAAO,EAAE,CAAC;QACtB,OAAO;YACL,SAAS,EAAE,IAAI;YACf,QAAQ,EAAE,iBAAiB;YAC3B,EAAE,EAAE,eAAe,CAAC,OAAO,CAAC,IAAI,SAAS,CAAC,EAAE;YAC5C,MAAM,EAAE,0EAA0E;SACnF,CAAC;IACJ,CAAC;IACD,OAAO;QACL,SAAS,EAAE,KAAK;QAChB,QAAQ,EAAE,MAAM;QAChB,EAAE,EAAE,IAAI;QACR,MAAM,EACJ,sHAAsH;KACzH,CAAC;AACJ,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,wBAAwB,CAAC,GAAW;IAClD,MAAM,MAAM,GAAG,YAAY,CAAC,GAAG,CAAC,EAAE,MAAM,CAAC;IACzC,IAAI,CAAC,MAAM;QAAE,OAAO,IAAI,CAAC;IACzB,OAAO,qBAAqB,CAAC,gBAAgB,CAAC,MAAM,CAAC,CAAC,CAAC;AACzD,CAAC"}

package/dist/policy-packs/builtin/post-merge-gate.d.ts

@@ -1,56 +0,0 @@
-import { z } from "zod";
-import type { PolicyPack, PolicyUx } from "../../schema/index.js";
-import { type Runtime } from "../runtime.js";
-import type { PackContribution } from "../types.js";
-import { PACK_NAME } from "./post-merge-gate-runtime.js";
-export { PACK_NAME };
-/**
- * Zod schema for this pack's `config:` block. Strict by design so
- * typo'd keys fail loud at lint time (mirrors sibling packs). `ux` is
- * the only operator-tunable key today — the curated mutation list and
- * escape allowlist are fixed in v1 (03-decisions.md); a config override
- * for either can land as a follow-up if operators need it.
- */
-export declare const configSchema: z.ZodObject<{
-    ux: z.ZodOptional<z.ZodObject<{
-        cannot: z.ZodString;
-        required: z.ZodArray<z.ZodString, "many">;
-        run: z.ZodArray<z.ZodString, "many">;
-    }, "strict", z.ZodTypeAny, {
-        cannot: string;
-        required: string[];
-        run: string[];
-    }, {
-        cannot: string;
-        required: string[];
-        run: string[];
-    }>>;
-}, "strict", z.ZodTypeAny, {
-    ux?: {
-        cannot: string;
-        required: string[];
-        run: string[];
-    } | undefined;
-}, {
-    ux?: {
-        cannot: string;
-        required: string[];
-        run: string[];
-    } | undefined;
-}>;
-/**
- * Shipped default `config.ux` for this pack. Canonical source for the
- * `full` init template and `harness pack reseed` (mirrors
- * branch-protection's `defaultUx`): a future wording fix lands here once
- * and reaches both a fresh `harness init --template full` and an
- * operator running `harness pack reseed post-merge-gate` against an
- * already-installed manifest. `${DEFAULT_BRANCH}` is always populated by
- * the blocker (falling back to the literal placeholder `<default-branch>`
- * when it cannot resolve `origin/HEAD`), never left as an unresolved
- * template var.
- */
-export declare function defaultUx(): PolicyUx;
-export declare function resolve(pack: PolicyPack, runtime?: Runtime): {
-    contribution: PackContribution;
-    warnings: string[];
-};