@kya-os/cli 1.8.3 → 2.0.2

package/dist/utils/dco/fix.d.ts

@@ -1,122 +0,0 @@
-import { type FixAttestation } from "@kya-os/contracts/review";
-/**
- * `dco fix` — push a signed, attributed fix commit to an EXISTING PR's head
- * branch, in response to a review that requested changes.
- *
- * `dco dispatch` (`dispatch.ts`) is a demo flow by construction: it always
- * creates a fresh branch and a NEW PR, and its commit is path-scoped to one
- * hardcoded demo file. Neither is safe or even possible for "land a real fix
- * on a PR someone already opened." This command reuses dispatch's signing
- * half in full (`resolveSigningIdentity`) but replaces its branch/commit/PR
- * flow with one that: checks out the PR's actual head branch, commits
- * exactly whatever the caller staged (no path scoping — see the commit step
- * below for why that's the right guard here), pushes to that SAME branch
- * (never a new one, never force), and optionally posts a signed attestation
- * answering the review that requested the fix.
- *
- * Every step fails closed with a named `failure` BEFORE the step that would
- * have side effects, and nothing is ever pushed after a failed verification
- * step (see the signed-commit check before the push call below).
- */
-export interface DcoFixOptions {
-    /** PR number, or a full PR URL. */
-    pr: string;
-    /** owner/name; when omitted, derived from `git remote get-url origin`. */
-    repo?: string;
-    /** Existing agent slug; same resolution rules as `dco dispatch`. */
-    agent?: string;
-    /** `git add -A` before committing. Default false: the caller stages. */
-    stageAll?: boolean;
-    /** Post the signed fix attestation as a PR comment. Default true. */
-    attest?: boolean;
-    /** The reviewed headSha this fix answers (40-hex). Required for attestation. */
-    respondsTo?: string;
-    /** The DIDComm fix task this run was dispatched for, when applicable. */
-    taskId?: string;
-    /** Commit subject. Default "fix: address signed review findings". */
-    message?: string;
-}
-export interface DcoFixResult {
-    ok: boolean;
-    /** Named, human-readable description of the step that failed, when !ok. */
-    failure?: string;
-    agent?: string;
-    did?: string;
-    branch?: string;
-    commitSha?: string;
-    signed?: boolean;
-    pushed?: boolean;
-    attested?: boolean;
-    prUrl?: string;
-}
-export declare function parseOwnerRepoFromRemoteUrl(url: string): string | null;
-/**
- * Parse "owner/repo" out of a full PR URL (`https://github.com/owner/repo/pull/123`).
- * Returns null for a bare PR number (or anything else): a bare number carries
- * no repo of its own, so there is nothing to cross-check it against — every
- * gh call below is scoped to `targetRepo` explicitly regardless.
- *
- * Shares PR_URL_PATTERN with extractPrNumber on purpose, rather than each
- * using its own regex: an input recognized by ONE as URL-shaped but not the
- * OTHER used to let a same-numbered-PR mismatch slip through silently — an
- * uppercase scheme, a missing scheme, or a URL embedded in surrounding text
- * would fail this function's narrower original pattern (skipping the
- * wrong-remote check below, since it only runs when this returns non-null)
- * while still matching extractPrNumber's looser unanchored `/pull/(\d+)`
- * search, so the flow proceeded against this checkout's same-numbered PR
- * with no cross-repo check ever having run. One shared pattern means
- * whatever extractPrNumber accepts as URL-shaped, this function recognizes
- * too, so the check it guards can never be bypassed that way.
- */
-export declare function parseOwnerRepoFromPrUrl(pr: string): string | null;
-/**
- * Normalize `pr` (a bare number or a full PR URL) down to just the number,
- * so every `gh pr` call below can be pinned with an explicit `-R targetRepo`
- * instead of a heterogeneous target that sometimes carries its own repo and
- * sometimes relies on ambient resolution. Ambient resolution is NOT
- * guaranteed to agree with `cwd`'s git remote — `GH_REPO` or a `gh repo
- * set-default` override takes precedence over it — so a bare number handed
- * to `gh` unpinned could read a different repo's PR even after step 2's
- * origin check. Returns null for anything that isn't a plain integer or a
- * `.../pull/<number>` URL matching PR_URL_PATTERN.
- */
-export declare function extractPrNumber(pr: string): string | null;
-/**
- * Strip characters that could break out of the marker-bounded structure
- * `buildFixAttestationCommentBody` builds around a value: a backtick would
- * prematurely close/reopen an adjacent code span; `-->` would prematurely
- * close this function's own HTML comment marker, letting whatever follows
- * render as visible PR-comment content instead of staying hidden inside
- * it; and, the other direction, a bare `<!--` would OPEN a new comment
- * mid-line, hiding everything after it in GitHub's rendered view —
- * including the fenced attestation block that's supposed to stay publicly
- * visible and verifiable. Defense in depth alongside
- * `FixAttestationSubjectSchema.repo`'s tighter character-class validation:
- * this also covers `agentName`, a free-text display name with no schema of
- * its own (an agent's `.mcpi/agent.json` name, sourced from a checkout —
- * see resolve-agent.ts's threat model for the same class of hostile-repo
- * risk applied to CLAUDE.md). Exported so `agent/markers.ts`'s review-verdict
- * marker (the same breakout risk, applied to a reviewer DID/repo instead of
- * an agent name/DID) reuses this exact sanitizer rather than a second copy
- * that could drift on which characters it strips.
- */
-export declare function sanitizeForMarkdownBlock(value: string): string;
-/**
- * Build the PR comment body posted for a fix attestation: an HTML-comment
- * marker (so a future `dco` run can find and dedupe on it), a one-line
- * human summary, and a fenced `kya-os-fix-attestation` JSON block that
- * round-trips `FixAttestationSchema`. The marker's fields are duplicated
- * from `attestation` in a stable, greppable form so tooling never has to
- * parse the fenced block just to know which commit/PR a comment is about.
- * The fenced JSON block itself carries the RAW, unsanitized values (it's
- * the actual signed data — sanitizing it would make it not round-trip);
- * only the marker and summary lines, which render as live markdown, are
- * sanitized. That includes `agentDid`: `DidStringSchema` only requires a
- * `did:<method>:` prefix followed by any non-whitespace method-specific
- * id, so it's exactly as free-form (and exactly as hostile-repo-sourced,
- * for a locally-registered agent whose name/DID this command reads off
- * disk) as `agentName` is — same breakout risk, same fix.
- */
-export declare function buildFixAttestationCommentBody(attestation: FixAttestation, agentName: string): string;
-export declare function runDcoFix(cwd: string, options: DcoFixOptions): Promise<DcoFixResult>;
-//# sourceMappingURL=fix.d.ts.map

package/dist/utils/dco/fix.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"fix.d.ts","sourceRoot":"","sources":["../../../src/utils/dco/fix.ts"],"names":[],"mappings":"AAGA,OAAO,EAGL,KAAK,cAAc,EAEpB,MAAM,0BAA0B,CAAC;AAOlC;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,WAAW,aAAa;IAC5B,mCAAmC;IACnC,EAAE,EAAE,MAAM,CAAC;IACX,0EAA0E;IAC1E,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,oEAAoE;IACpE,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,wEAAwE;IACxE,QAAQ,CAAC,EAAE,OAAO,CAAC;IACnB,qEAAqE;IACrE,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,gFAAgF;IAChF,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,yEAAyE;IACzE,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,qEAAqE;IACrE,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB;AAED,MAAM,WAAW,YAAY;IAC3B,EAAE,EAAE,OAAO,CAAC;IACZ,2EAA2E;IAC3E,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,QAAQ,CAAC,EAAE,OAAO,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAkDD,wBAAgB,2BAA2B,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAWtE;AAaD;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,uBAAuB,CAAC,EAAE,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAGjE;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,eAAe,CAAC,EAAE,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAOzD;AA8BD;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,wBAAwB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAE9D;AAED;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,8BAA8B,CAC5C,WAAW,EAAE,cAAc,EAC3B,SAAS,EAAE,MAAM,GAChB,MAAM,CAaR;AAED,wBAAsB,SAAS,CAAC,GAAG,EAAE,MAAM,EAAE,OAAO,EAAE,aAAa,GAAG,OAAO,CAAC,YAAY,CAAC,CAmY1F"}