codex-orchestrator 2.0.11 → 2.0.13

package/internal-workflow/skills/to-spec/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: to-spec
+description: Turn the current conversation and codebase context into a proportionate, human-readable product spec or PRD in the user's language without another interview. In Plan combined mode, return the draft in context without intermediate publication; in standalone use, publish durable planning context only when requested. Planning output never authorizes implementation.
+---
+
+Synthesize what is already known; do not interview the user. Produce a product
+spec or PRD in the user's conversation language and preserve exact domain or
+technical identifiers. The result is planning authority, never executable
+delivery authority by itself.
+
+## Modes
+
+- **Combined flow:** Combined mode is invoked by Plan. Return the draft to Plan
+  in the current context so it can pass the draft directly to `$to-tickets`.
+  Do not review or publish an intermediate PRD. `$to-tickets` owns every
+  remaining packet step. The approved ticket packet is the last planning
+  artifact before separately authorized delivery.
+- **Standalone:** publish one durable planning-context issue only when
+  requested. Mark it `Artifact: planning-context`. Do not apply a triage state
+  or imply implementation authority.
+
+If synthesis exposes a new product decision, keep the PRD unapproved and return
+the decision to the user. Publication alone is never approval.
+
+Before standalone publication, read the repository's issue-tracker policy. If
+no authoritative tracker or publication procedure exists, stop and ask where
+to publish; do not invent one. Combined mode does not need a tracker until
+`$to-tickets` prepares publication.
+
+## Artifact Shape
+
+Choose the smallest content that preserves product intent and proof. A narrow
+bug, incident, data repair, or understood implementation correction may use a
+**Fix Brief** with one to three observable stories. Otherwise use the same
+template and include only sections that carry a real decision, consequence,
+scope boundary, or proof obligation.
+
+`$to-spec` does not determine implementation-ticket count. PRD length, section
+count, file count, and risk do not size a later ticket packet; Plan and
+`$to-tickets` retain composition and slicing ownership. Material risk
+strengthens `Risk / Proof Notes`; it does not make the PRD or solution broader.
+Omit that section when no material risk exists.
+
+## Process
+
+1. Explore the repo if needed. Use project domain language, respect relevant
+   ADRs, and reuse cited `$research` artifacts. Keep unsupported external facts
+   open instead of converting them into product scope.
+
+2. Sketch the seams at which the outcome will be proved. Existing seams should
+   be preferred to new ones. Use the highest seam possible. If new seams are
+   needed, propose them at the highest point you can. The fewer seams across the
+   codebase, the better; the ideal number is one. Record only seams that
+   materially define behavior, proof, or ownership, and ask the user only when
+   a seam choice changes scope, risk, or ownership.
+
+3. Write the template below, then follow the requested mode. A standalone
+   planning-context issue is marked `Artifact: planning-context`; it is not an
+   implementation ticket and receives no triage state.
+
+<spec-template>
+
+## Problem Statement
+
+The problem that the user is facing, from the user's perspective.
+
+## Solution
+
+The solution to the problem, from the user's perspective.
+
+## Decisions For Approval
+
+The product, behavior, scope, ownership, rollout, and risky trade-off decisions
+the user is being asked to approve. Separate confirmed decisions from open
+decisions. If implementation discovery later changes one of these decisions,
+the delivery workflow must return a decision delta instead of guessing.
+
+## Non-Obvious Consequences
+
+Important hidden state, background behavior, failure behavior, limitations, or
+trade-offs that the user would not infer from the happy-path solution. Write
+`None` only when there genuinely are no material consequences.
+
+## User Stories
+
+A numbered list of distinct, observable user stories in the format:
+
+1. As an <actor>, I want a <feature>, so that <benefit>
+
+Include only stories that change scope, acceptance, or proof; do not create
+variants to make the list look complete. For a Fix Brief spec, use 1-3 stories
+or operational scenarios that directly explain the bug, repair, or regression
+risk.
+
+## Implementation Decisions
+
+A list of already approved implementation constraints or technical decisions
+that materially protect product behavior. Omit architecture vocabulary when
+ownership and public seams do not change.
+
+Do NOT include specific file paths or code snippets. They may end up being
+outdated very quickly.
+
+Exception: if a prototype produced a snippet that encodes a decision more
+precisely than prose can, inline it within the relevant decision and note
+briefly that it came from a prototype. Trim to the decision-rich parts — not a
+working demo, just the important bits.
+
+## Testing Decisions
+
+A list of testing decisions that were made. Describe what makes a good
+behavior-level test, which modules will be tested, and relevant test prior art
+in the codebase.
+
+## Out of Scope
+
+A description of the things that are out of scope for this spec.
+
+## Risk / Proof Notes
+
+Required only when material risk exists:
+
+- Primary risk:
+- Key invariants:
+- Expected proof:
+- Review focus:
+- Out-of-scope risk:
+
+## Further Notes
+
+Any further notes about the feature.
+
+</spec-template>

package/internal-workflow/skills/to-spec/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "To Spec"
+  short_description: "Turn context into product authority"
+  default_prompt: "Use $to-spec to synthesize product authority; in Plan combined mode, return the contextual draft so Plan can pass it to $to-tickets."
+policy:
+  allow_implicit_invocation: false

package/internal-workflow/skills/to-spec/evals/evals.json

@@ -0,0 +1,24 @@
+{
+  "schema_version": 1,
+  "skill": "to-spec",
+  "cases": [
+    {
+      "id": "combined-prd-stays-contextual",
+      "prompt": "Plan invoked to-spec in combined mode for a spec-and-tickets outcome.",
+      "expected": ["synthesize the PRD from known context", "return the draft to Plan without review or publication"],
+      "forbidden": ["publish an intermediate PRD", "run the packet review"]
+    },
+    {
+      "id": "standalone-planning-context",
+      "prompt": "Publish this synthesized PRD as standalone durable planning context.",
+      "expected": ["publish one Artifact: planning-context issue", "apply no triage state", "preserve planning as non-executable authority"],
+      "forbidden": ["create implementation tickets", "imply implementation authorization"]
+    },
+    {
+      "id": "proportional-prd-does-not-size-tickets",
+      "prompt": "Write a proportional PRD for this risky cross-module outcome without deciding its implementation breakdown.",
+      "expected": ["preserve Decisions For Approval and Non-Obvious Consequences", "include Risk / Proof Notes because risk is material", "leave ticket count and slicing to Plan and to-tickets"],
+      "forbidden": ["make user stories extremely extensive", "determine ticket count from modules, files, or risk"]
+    }
+  ]
+}

package/internal-workflow/skills/to-tickets/SKILL.md

@@ -0,0 +1,189 @@
+---
+name: to-tickets
+description: Compile Plan's contextual PRD draft or approved product authority into the smallest executable ticket packet, run one fresh semantic packet review, obtain one approval, publish serially, verify authoritative tracker read-back, and stop before implementation.
+---
+
+# To Tickets
+
+Compile product authority into the smallest number of independently verifiable
+vertical tickets. Keep one coherent outcome as one ticket. Each generated AFK
+ticket must be executable from its body plus the Parent PRD and current
+repository evidence without another planning artifact.
+
+The Parent PRD remains the sole product and final-acceptance authority. Each
+ticket contains only its local observable outcome, scope, blockers, proof, and
+Parent link. The approved ticket body plus Parent PRD is the final execution
+authority; no later planning pass is inserted.
+
+`$to-tickets` owns one fresh semantic reviewer, one explicit user approval,
+serialized publication, deterministic reconciliation, and authoritative
+tracker read-back for the complete packet.
+
+The primary route remains `planning-only` while compiling or publishing these
+artifacts. `ticket-graph` begins only after separate delivery authorization;
+never report it merely because the planning output is a graph.
+
+Read the repository's issue-tracker policy and triage vocabulary before
+preparing publication. If either required authority is missing, stop before
+tracker effects and ask the user; do not invent a tracker, schema, or labels.
+
+## Progressive Reference
+
+Read [publishing-details.md](references/publishing-details.md) before preparing
+the complete publish-ready packet, requesting approval, or publishing any
+tracker effect.
+
+## Shape
+
+Split only for an independent outcome, owner, release, real blocker, safe
+parallel boundary, or human/live gate. Do not split by technical layer.
+
+Each ticket is a tracer-bullet vertical slice: it cuts a narrow but COMPLETE
+path through every relevant layer, is demoable or verifiable on its own, and is
+sized to fit in a single fresh context window. Keep one coherent outcome as one
+ticket. Add discovery, integration, or HITL tickets only when each has its own
+outcome and blocking relationship. Risk strengthens proof and review focus; it
+does not create tickets. Merge steps that share one owner, release, and
+validation path.
+
+Where repository evidence proves a small prefactor is required, "Make the
+change easy, then make the easy change." Keep it inside the same vertical
+outcome unless it is independently verifiable and genuinely blocks later work.
+
+## Process
+
+### 1. Gather authority
+
+Read the complete source and its decision-changing comments. Reuse cited
+`$research` artifacts. If a material external contract remains unresolved,
+create a blocking discovery ticket.
+
+Explore only enough repository code, tests, ADRs, and domain docs to identify
+the real owner/public seam and a compatible proof. Never invent paths, symbols,
+commands, fixtures, ownership, or behavior.
+
+When an applicable owner/public seam is honestly unknown, create a blocking
+discovery ticket whose observable outcome is the missing owner, seam, and proof
+evidence. Do not publish the dependent implementation ticket as AFK-ready until
+that discovery resolves it.
+
+### 2. Draft executable vertical tickets
+
+Each ticket must:
+
+- deliver one observable end-to-end outcome;
+- link directly to its Parent PRD;
+- bound local scope and out-of-scope work;
+- name the owner/public seam when repository evidence confirms it;
+- state observable acceptance criteria and a compatible behavior proof or exact
+  non-TDD proof;
+- explain why the proof cannot pass while the approved claim is false;
+- declare real blockers and dependency edges.
+
+Keep unresolved product decisions with the user and unresolved external or
+technical discovery in a blocking AFK/HITL ticket. If the generated ticket
+would need a later planning artifact, it is not ready to publish.
+
+For user-facing work, include an end-to-end walkthrough criterion and use
+`$ui-evidence-proof` as the proof standard. For a wide mechanical refactor, use
+expand-contract and keep each migration batch independently green.
+
+If repository evidence proves an **indivisible migration** whose intermediate
+batches cannot be independently green, do not publish those batches as child
+tickets and do not create a shared red integration branch. Compile one
+executable migration ticket with one owner, one isolated execution scope, and
+one final green acceptance boundary over the complete migrated state. In this
+fallback, intermediate batches are not child checkpoints and release no successor. If
+that complete outcome cannot fit one fresh implementation context or lacks a
+credible final proof, return a Decision Delta instead of publishing an
+unexecutable graph.
+
+### 3. Freeze the complete publish-ready packet
+
+Keep one contextual packet containing the complete Parent PRD and every exact
+ticket body, plus:
+
+- source solution, scope, exclusions, decisions, and consequences;
+- ordered graph and blocking edges;
+- material risks and open questions.
+
+This packet is contextual planning data, not a separately published artifact or
+workflow owner. Do not publish any intermediate PRD.
+
+### 4. Run one fresh semantic packet review
+
+For the settled packet, launch exactly one fresh `standards_reviewer` without a
+history fork (`fork_context=false` on V1; `fork_turns="none"` on V2). Begin its
+brief with `Assigned role: standards_reviewer`, provide the full source authority
+and complete publish-ready packet, and require both internal lenses in the same
+review activation: source fidelity and ticket executability.
+
+- **Source fidelity:** every product claim, decision, scope boundary,
+  consequence, and blocker is grounded in the source; no behavior or ownership
+  is invented or lost.
+- **Ticket executability:** every ticket is a cohesive vertical outcome that a
+  fresh implementation context can execute and prove from its body plus the
+  Parent PRD; dependencies are real, proof observes the claim, and no later
+  planning artifact is required.
+
+The reviewer is read-only and returns `APPROVE` or `NEEDS_WORK` with exact
+source/artifact evidence. Capture a non-empty fresh child identity and wait for
+that same child. Do not split the lenses across children and do not launch the
+delivery Standards review. A missing, failed, or non-approving review
+blocks approval and publication. If repairs change a product decision, return
+that decision to the user rather than resolving it in review.
+
+### 5. Get one explicit approval
+
+After the semantic review approves, show the complete publish-ready packet and
+obtain one explicit user approval of the exact Parent and ticket bodies, product
+decisions, scope, exclusions, ticket boundaries, blockers/dependencies,
+ownership, HITL/live gates, and proof obligations. Tracker identifiers, native
+links, and final state are the only fields publication may fill afterward.
+
+The single exact-packet approval also answers Matt's useful breakdown checks:
+
+- Does the granularity feel right?
+- Are the blocking edges correct — does each ticket only depend on tickets that
+  genuinely gate it?
+- Should any tickets be merged or split further?
+
+These are not separate quizzes or approvals. Any requested change rebuilds the
+complete packet under the Decision Delta rule below.
+
+A change to behavior, scope, ownership, ticket boundaries, blockers, or proof
+obligations invalidates approval and returns a Decision Delta. The changed
+complete packet requires one new fresh semantic review and one new explicit
+user approval before publication can continue.
+
+### 6. Publish final artifacts
+
+Follow [publishing-details.md](references/publishing-details.md). Publication is
+serialized through the single current root publisher. If product context is
+not durable, first publish one non-executable Parent marked
+`Artifact: planning-context` and without a triage state. When a source tracker
+issue already exists, reference it without closing or relabeling it. Publish
+blockers first.
+
+- **Local files:** write one file per ticket under
+  `.scratch/<feature-slug>/issues/<NN>-<slug>.md`.
+- **Real tracker:** publish one issue per ticket in dependency order and use
+  native Parent/sub-issue and blocking links.
+
+Record the future frontier — tickets whose blockers are all done — in the
+approved graph, but do not work it. Delivery starts only under separate
+authorization after this planning flow stops.
+
+The issue body plus Parent PRD is the durable execution authority. Apply
+`ready-for-agent` to AFK and `ready-for-human` to HITL tickets directly; do not
+invoke `$triage` or add a duplicate brief comment. Publish the approved terms
+unchanged except for tracker identifiers, native links, and final state.
+
+Reject AFK publication when criteria require later interpretation, proof can
+pass while the claim is false, an applicable owner/seam is unknown, or a future
+planning artifact is required. After all publication effects, perform the
+authoritative tracker read-back and deterministic reconciliation defined in the
+reference.
+
+Successful read-back stops planning before implementation. Publication, links,
+and labels do not authorize delivery.

package/internal-workflow/skills/to-tickets/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "To Tickets"
+  short_description: "Review and publish executable ticket packets"
+  default_prompt: "Use $to-tickets to compile the complete executable packet, run one fresh semantic review, obtain one approval, publish serially, verify tracker read-back, and stop before implementation."
+policy:
+  allow_implicit_invocation: false

package/internal-workflow/skills/to-tickets/evals/evals.json

@@ -0,0 +1,79 @@
+{
+  "schema_version": 1,
+  "skill": "to-tickets",
+  "cases": [
+    {
+      "id": "coherent-outcome-stays-one-ticket",
+      "prompt": "Break down one coherent outcome with one owner, release, and validation path.",
+      "expected": ["create one ticket"],
+      "forbidden": ["split from size, file count, statefulness, or generic risk"]
+    },
+    {
+      "id": "ordinary-one-ticket-stays-direct",
+      "prompt": "Compile the approved one-ticket PRD into its final executable ticket and stop before delivery.",
+      "expected": ["publish one ticket containing its local outcome, scope, blockers, proof, and Parent link", "keep the Parent PRD as sole product and final authority"],
+      "forbidden": ["create duplicate durable planning state", "request another execution artifact"]
+    },
+    {
+      "id": "complete-packet-gets-one-semantic-review",
+      "prompt": "Prepare a publish-ready PRD and three-ticket graph after Plan passed the combined PRD draft to you.",
+      "expected": ["launch one fresh semantic reviewer over the complete packet", "apply source fidelity and ticket executability in that one review", "obtain one explicit user approval before publication"],
+      "forbidden": ["review the intermediate PRD", "launch separate workflow owners for each lens", "request multiple approvals"]
+    },
+    {
+      "id": "serialized-publication-recovers-response-loss",
+      "prompt": "Publish an approved Parent and two children when responses may be lost after create, link, or label effects.",
+      "expected": ["serialize every effect", "reread authoritative tracker state before retrying", "retry only a proven-missing effect", "finish with authoritative tracker read-back"],
+      "forbidden": ["recreate an identifiable issue", "retry an unknown effect blindly", "publish concurrently"]
+    },
+    {
+      "id": "readback-repairs-only-technical-mismatch",
+      "prompt": "Authoritative read-back finds one missing label while all approved bodies and relationships match.",
+      "expected": ["repair the proven technical mismatch and reread", "do not launch another semantic reviewer", "do not request another approval"],
+      "forbidden": ["treat integrity proof as semantic review", "start implementation"]
+    },
+    {
+      "id": "material-change-invalidates-approval",
+      "prompt": "During reconciliation, the proposed repair changes one ticket boundary and its proof obligation.",
+      "expected": ["return a Decision Delta", "run one new fresh complete semantic review", "obtain one new user approval before publication continues"],
+      "forbidden": ["call the change technical refinement", "reuse the old approval"]
+    },
+    {
+      "id": "ambiguous-partial-packet-fails-closed",
+      "prompt": "Search finds two matching Parents or publication concurrency cannot be excluded.",
+      "expected": ["perform no writes", "fail closed for reconciliation"],
+      "forbidden": ["pick one Parent by guess", "create another packet"]
+    },
+    {
+      "id": "tracer-bullet-vertical-outcome",
+      "prompt": "Slice one approved outcome that crosses schema, API, UI, and behavior proof.",
+      "expected": ["create the smallest tracer-bullet ticket that completes the relevant end-to-end path", "keep the ticket demoable or verifiable in one fresh context"],
+      "forbidden": ["split by schema, API, UI, and tests", "create tickets from generic risk"]
+    },
+    {
+      "id": "unknown-owner-seam-becomes-discovery",
+      "prompt": "The approved outcome is clear, but repository evidence cannot identify the applicable owner or public proof seam.",
+      "expected": ["create a blocking discovery ticket for owner, seam, and proof evidence", "block the dependent implementation ticket"],
+      "forbidden": ["guess the owner or seam", "publish the dependent ticket as AFK-ready"]
+    },
+    {
+      "id": "one-exact-packet-approval",
+      "prompt": "The complete Parent and ticket bodies passed the one combined semantic review.",
+      "expected": ["show the exact complete packet", "obtain one approval covering granularity, blocking edges, boundaries, ownership, and proof", "publish only the approved terms"],
+      "forbidden": ["run separate fidelity and executability reviewers", "request multiple approvals", "change ticket boundaries during publication"]
+    },
+    {
+      "id": "indivisible-migration-one-green-ticket",
+      "prompt": "A broad migration has one owner and final proof, but its intermediate batches cannot remain green independently.",
+      "expected": [
+        "compile one executable migration ticket with one final green acceptance boundary",
+        "keep intermediate batches inside that ticket rather than child checkpoints",
+        "return a Decision Delta if the complete migration cannot fit one fresh context"
+      ],
+      "forbidden": [
+        "publish red migration batches as graph children",
+        "create a shared red integration branch"
+      ]
+    }
+  ]
+}

package/internal-workflow/skills/to-tickets/references/publishing-details.md

@@ -0,0 +1,117 @@
+# To Tickets Publishing Details
+
+## Executable ticket body
+
+Every ticket is executable from its body plus the Parent PRD without another
+planning artifact. Keep the body local and include only:
+
+- the Parent link;
+- the local observable outcome and acceptance criteria;
+- in-scope and out-of-scope boundaries;
+- confirmed owner/public seam when needed for zero-guess execution;
+- blockers and native dependency links;
+- behavior proof or exact non-TDD proof;
+- AFK/HITL final state, which never authorizes implementation.
+
+Do not copy the Parent's product authority into each ticket. Keep shared product
+rules in the Parent, make a contract-owning ticket block its consumers, and
+merge slices that cannot stand or be proved independently. A material execution
+gap becomes a blocking discovery/HITL ticket or a Decision Delta; never defer it
+to a later planning artifact.
+
+## Publish template
+
+For local files, prefix the body with `# <NN> — <Ticket title>`. For a real
+tracker, use the same title as the issue title and begin the body at `## Parent`.
+The body shape is otherwise identical:
+
+```md
+## Parent
+
+<authoritative Parent link>
+
+## Observable outcome
+
+<one end-to-end behavior>
+
+## Scope
+
+- In scope: <local behavior and owner>
+- Out of scope: <source-authorized boundary>
+
+## Acceptance criteria
+
+- [ ] <observable criterion>
+- [ ] <observable criterion>
+
+## Owner and proof seam
+
+- Owner / public seam: <confirmed owner or bounded discovery>
+- Proof: <behavior-level or exact non-TDD proof>
+- Why false behavior cannot pass: <short explanation>
+
+## Blocked by
+
+<native ticket relationships or None>
+
+## Final state
+
+AFK: `ready-for-agent`; HITL: `ready-for-human`. State does not authorize
+implementation.
+```
+
+## Serialized publication
+
+The single current root publisher performs every tracker effect. Do not create
+a claim, lease, lock service, coordinator record, or other durable publication
+state.
+
+Before writing:
+
+1. Search for an existing source-linked Parent and source-linked children.
+2. Reconcile immutable source identity and any known tracker identities.
+3. If concurrent publication cannot be excluded, multiple matching Parents
+   exist, or a partial packet cannot be identified deterministically, perform no
+   writes and fail closed.
+
+Publish in dependency order and await each create, link, and label effect
+separately, then reread authoritative tracker state before the next write.
+Persist each returned identity through the Parent/source links in issue bodies.
+Apply labels only after identity reconciliation.
+
+Publication records the graph frontier but never works it. A ticket with no
+unresolved blockers is merely eligible for later separately authorized
+delivery; publication does not start that delivery.
+
+After a timeout, transport loss, or unknown write outcome, reread the tracker
+and retry only a proven-missing effect. Continue an identifiable partial packet
+by filling missing issues or relationships; never recreate an identifiable
+issue and never retry an unknown effect blindly.
+
+## Authoritative read-back
+
+After every publication effect, reread the tracker and compare it with the
+approved packet. Verify:
+
+- exact approved Parent and ticket bodies after substituting only approved
+  tracker identifiers, native links, and final state;
+- native Parent, sub-issue, and blocker links in both directions where the
+  tracker exposes them;
+- exact AFK/HITL labels and absence of conflicting planning or delivery state;
+- absence of duplicate or partial packets;
+- every ticket remains executable from its body plus the Parent PRD;
+- the publication event trace contains one semantic review, one approval, and
+  no implementation action.
+
+Post-publication read-back is integrity proof. It does not launch another
+semantic reviewer and does not request another approval.
+
+A proven technical mismatch such as a missing label or native link may be
+repaired deterministically and reread. Ambiguous identity, concurrent writes,
+or duplicate candidates fail closed without writes. A repair that changes
+behavior, scope, ownership, ticket boundaries, blockers, or proof obligations
+is a Decision Delta: invalidate approval, rebuild the complete packet, run one
+new fresh semantic review, and obtain one new explicit user approval.
+
+Successful read-back must stop before implementation. Publication, links, and
+labels do not authorize delivery.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codex-orchestrator",
-  "version": "2.0.11",
+  "version": "2.0.13",
   "description": "Reusable GitHub Issues runner for Codex.",
   "type": "module",
   "license": "MIT",

package/dist/src/v2/proof-store.d.ts

@@ -1,54 +0,0 @@
-import type { ProofReceipt } from './proof-report.js';
-import { type DurableReportInvocationV1 } from './contained-report-operation.js';
-import { type AtomicStateFileOptions } from './atomic-store.js';
-declare const TERMINAL_STATUSES: readonly ["passed", "needs-rework", "external-block", "transport-failed", "cancelled", "internal-error"];
-export type ProofStatus = 'active' | typeof TERMINAL_STATUSES[number];
-export interface ProofIosInputsV1 {
-    helperPath: string;
-    leaseRoot: string;
-    leaseArtifactPath: string;
-    proofId: string;
-    ownerPid: number;
-    xcrunPath: string;
-    runtimeId: string | null;
-    deviceTypeId: string | null;
-}
-export interface ProofStateV1 {
-    schema: 'codex-orchestrator.acceptance-proof-state';
-    version: 1;
-    generation: number;
-    proofId: string;
-    bindingSha256: string;
-    status: ProofStatus;
-    reportRepairs: 0 | 1;
-    repairFindings: string[];
-    repairArtifactSha256?: Record<string, string>;
-    iosProofInputs?: ProofIosInputsV1;
-    invocation?: DurableReportInvocationV1;
-    receipt?: ProofReceipt;
-    startedAt: string;
-    updatedAt: string;
-}
-export type ProofStateBodyV1 = Omit<ProofStateV1, 'generation'>;
-export interface ProofRecordWriter {
-    read(proofId: string): Promise<ProofStateV1 | undefined>;
-    compareAndSwap(proofId: string, expectedBinding: string, expectedGeneration: number, next: ProofStateBodyV1): Promise<ProofStateV1>;
-}
-export declare class InMemoryProofRecordWriter implements ProofRecordWriter {
-    private readonly states;
-    read(proofId: string): Promise<ProofStateV1 | undefined>;
-    compareAndSwap(proofId: string, expectedBinding: string, expectedGeneration: number, next: ProofStateBodyV1): Promise<ProofStateV1>;
-}
-export declare class FileProofRecordWriter implements ProofRecordWriter {
-    private readonly proofsRoot;
-    private readonly options;
-    constructor(proofsRoot: string, options?: AtomicStateFileOptions);
-    read(proofId: string): Promise<ProofStateV1 | undefined>;
-    compareAndSwap(proofId: string, expectedBinding: string, expectedGeneration: number, next: ProofStateBodyV1): Promise<ProofStateV1>;
-    private file;
-}
-export declare function validateProofState(value: unknown): ProofStateV1;
-export declare function validateProofIosInputs(value: unknown, proofId: string): asserts value is ProofIosInputsV1;
-export declare function validateProofArtifactInventory(value: unknown): Record<string, string>;
-export {};
-//# sourceMappingURL=proof-store.d.ts.map

package/dist/src/v2/proof-store.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"proof-store.d.ts","sourceRoot":"","sources":["../../../src/v2/proof-store.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AACtD,OAAO,EAAmC,KAAK,yBAAyB,EAAE,MAAM,iCAAiC,CAAC;AAGlH,OAAO,EAAmB,KAAK,sBAAsB,EAAE,MAAM,mBAAmB,CAAC;AAKjF,QAAA,MAAM,iBAAiB,0GAOb,CAAC;AAEX,MAAM,MAAM,WAAW,GAAG,QAAQ,GAAG,OAAO,iBAAiB,CAAC,MAAM,CAAC,CAAC;AAEtE,MAAM,WAAW,gBAAgB;IAC/B,UAAU,EAAE,MAAM,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,iBAAiB,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,CAAC;IAClF,QAAQ,EAAE,MAAM,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,SAAS,EAAE,MAAM,GAAG,IAAI,CAAC;IAAC,YAAY,EAAE,MAAM,GAAG,IAAI,CAAC;CAC5F;AAED,MAAM,WAAW,YAAY;IAC3B,MAAM,EAAE,2CAA2C,CAAC;IACpD,OAAO,EAAE,CAAC,CAAC;IACX,UAAU,EAAE,MAAM,CAAC;IACnB,OAAO,EAAE,MAAM,CAAC;IAChB,aAAa,EAAE,MAAM,CAAC;IACtB,MAAM,EAAE,WAAW,CAAC;IACpB,aAAa,EAAE,CAAC,GAAG,CAAC,CAAC;IACrB,cAAc,EAAE,MAAM,EAAE,CAAC;IACzB,oBAAoB,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAC9C,cAAc,CAAC,EAAE,gBAAgB,CAAC;IAClC,UAAU,CAAC,EAAE,yBAAyB,CAAC;IACvC,OAAO,CAAC,EAAE,YAAY,CAAC;IACvB,SAAS,EAAE,MAAM,CAAC;IAClB,SAAS,EAAE,MAAM,CAAC;CACnB;AAED,MAAM,MAAM,gBAAgB,GAAG,IAAI,CAAC,YAAY,EAAE,YAAY,CAAC,CAAC;AAEhE,MAAM,WAAW,iBAAiB;IAChC,IAAI,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,YAAY,GAAG,SAAS,CAAC,CAAC;IACzD,cAAc,CACZ,OAAO,EAAE,MAAM,EACf,eAAe,EAAE,MAAM,EACvB,kBAAkB,EAAE,MAAM,EAC1B,IAAI,EAAE,gBAAgB,GACrB,OAAO,CAAC,YAAY,CAAC,CAAC;CAC1B;AAED,qBAAa,yBAA0B,YAAW,iBAAiB;IACjE,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAmC;IAEpD,IAAI,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,YAAY,GAAG,SAAS,CAAC;IAKxD,cAAc,CAClB,OAAO,EAAE,MAAM,EACf,eAAe,EAAE,MAAM,EACvB,kBAAkB,EAAE,MAAM,EAC1B,IAAI,EAAE,gBAAgB,GACrB,OAAO,CAAC,YAAY,CAAC;CAczB;AAED,qBAAa,qBAAsB,YAAW,iBAAiB;IAE3D,OAAO,CAAC,QAAQ,CAAC,UAAU;IAC3B,OAAO,CAAC,QAAQ,CAAC,OAAO;gBADP,UAAU,EAAE,MAAM,EAClB,OAAO,GAAE,sBAA2B;IAGjD,IAAI,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,YAAY,GAAG,SAAS,CAAC;IAmBxD,cAAc,CAClB,OAAO,EAAE,MAAM,EACf,eAAe,EAAE,MAAM,EACvB,kBAAkB,EAAE,MAAM,EAC1B,IAAI,EAAE,gBAAgB,GACrB,OAAO,CAAC,YAAY,CAAC;IAYxB,OAAO,CAAC,IAAI;CAIb;AAED,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,OAAO,GAAG,YAAY,CA2C/D;AAED,wBAAgB,sBAAsB,CAAC,KAAK,EAAE,OAAO,EAAE,OAAO,EAAE,MAAM,GAAG,OAAO,CAAC,KAAK,IAAI,gBAAgB,CAQzG;AAwBD,wBAAgB,8BAA8B,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAWrF"}