PR B: Add durable execution records for pilot workflows

[chenmingtang830]

Summary

Implements the focused PR B execution envelope for the existing hosted pilot workflows: evidence.submit, experiment.ingest, and claim.evaluate when the caller supplies an idempotency key.

• Inventories existing operation idempotency and automatic Judge jobs in docs/DURABLE_EXECUTION.md before adding records for uncovered workflows.
• Adds versioned, content-minimizing execution and attempt rows with explicit success, retryable failure, terminal failure, and interrupted states. Service startup marks interrupted calls for explicit resubmission.
• Reuses the kernel's atomic event/idempotency transaction. A retry after a crash between the kernel write and execution bookkeeping replays the result without duplicating governed events.
• Defines a stable, bounded external trigger key helper and rejects conflicting keys, concurrent execution, or changed execution versions.
• Provides Owner-only /owner/api/executions inspection and failed-attempt activity rows, linking output evidence or evaluations to later claim review and admission authority.

Verification

• Full Python suite: 388 tests passed.
• Final targeted execution and Owner HTTP tests: 9 passed.
• Ruff and git diff --check passed.
• Sdist and wheel built with both new modules included.

Scope and limits

Existing unkeyed calls keep their behavior. This slice records current deterministic intake and verification operations; it does not persist customer payloads for unattended replay or add a general-purpose background queue. Judge retains its existing policy-bound job path. An execution record never grants admission.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
proofpress	Ready	Preview	Sep 28, 2026 5:04pm UTC