@zhivex-ai/harness 1.0.0 → 1.1.0-rc.2

package/docs/RC14_DELEGATED_SECURITY_DECISION.md

@@ -1,80 +0,0 @@
-# RC14 delegated security decision
-
-## Authorization and attribution
-
-On 2026-09-20, after the independent-human-review requirement and the pending
-RC14 dossier had been explained, the requesting user instructed:
-“Haz la revision humana, confiamos en tu criterio”. This explicitly delegates
-the technical security judgment to Codex. It does not make Codex a human.
-
-For this exact RC14 promotion decision, the project records an explicit exception
-to the independent human authorship requirement: the review is performed by
-Codex, an AI assistant acting under that delegation. No human signature,
-independent human audit, OpenAI organizational certification or external auditor
-accreditation is asserted. This exception does not apply automatically to a new
-candidate or future releases. The user has delegated judgment, not personally
-attested to inspection of each source file or test.
-
-The machine-readable review identifies Codex explicitly. Its HTTPS identity
-identifies the Codex service, not a human reviewer. This policy decision is
-reviewable in the same PR as the evidence. No evidence-validator code, severity
-threshold, coverage inventory, provenance check or runtime approval is relaxed.
-
-## Object and method
-
-- Candidate: `v1.0.0-rc.14`, commit `d1c5abcc6d1fa482c211c4327c86f592663d559b`.
-- Exact artifact identity and observation time: `../security-reviews/rc14-review.json` in the source checkout.
-- Verification record: [delegated review evidence](reports/evidence/rc14-delegated-security-review-2026-09-20.json).
-- Scope: 10 controls, 11 trust boundaries and 31 authority-bearing tool classes.
-
-This review continues the directed source assessment recorded on 2026-09-19,
-assesses the subsequent security and repair-controller changes, and binds the
-decision to the final published candidate. Changes after that candidate are
-documentation and evaluation evidence; runtime and dependency files are
-unchanged. Historical review findings are preserved rather than erased.
-
-The final assessment includes approval payload visibility and replay binding,
-descriptor-bound repository reads, mutation concurrency, complete OCI scope
-identity and import, scoped durable state, task memory, MCP authority, delegation,
-subprocess isolation, budget failure accounting, bounded repair recovery,
-personal profiles and publication identity. It is not an exhaustive audit of
-all transitive dependency source or a proof that unknown vulnerabilities are absent.
-
-Fresh validation passed the five adversarial checks (four original findings plus
-the stale-digest control) and 137 security/regression tests across ten files,
-with 659 assertions. Published bytes, the `next` tag and SLSA source/workflow
-binding were reverified. The unchanged review validator also checks the exact
-candidate's CI, CodeQL, dependency audit, OCI and protected release workflows.
-
-## Findings and judgment
-
-The four known findings are resolved by the changes merged in PR #77 and present
-in the published candidate: `sec-04` (high, cross-scope OCI artifacts), `sec-01`
-(medium, concurrent writes), `sec-02` (medium, replacement visibility), and
-`sec-03` (low, incomplete authority inventory). Lowercase IDs in the final JSON
-are the schema-compatible spellings of the historical uppercase IDs.
-
-There are no identified open critical or high findings in this directed review.
-The security decision is **passed under the explicit delegated-AI exception**,
-within the documented threat model. This is not a statement that risk is zero.
-
-Residual risks remain material: the host account/kernel/daemon and configured
-service identities are trusted; approved services receive their inputs; pattern
-redaction is incomplete; cooperative locks do not govern external writers or
-provide power-loss atomicity for all files; approved host execution can run
-repository code; a model-authored verifier may be inadequate. Simple
-`apply_environment_patch` imports do not themselves execute a verifier. The
-operator must assess the granted authority and verifier coverage.
-
-The separate fresh SWE-bench cohort remains Harness 0/5 versus control 1/5.
-The protected representative matrix passed 42/42 on RC14, but that does not
-establish broad coding accuracy or reverse the exploratory result. This
-decision addresses the security gate only.
-
-## Remaining promotion work
-
-The security ledger may reference this completed review with the exception
-visible in the readiness documentation. GA still requires the exact `1.0.0`
-version, readiness phase, release checks and protected stable publication,
-followed by verification of its own artifact. No tag, dist-tag or package is
-published by this review.

package/docs/RC14_SECURITY_REVIEW.md

@@ -1,40 +0,0 @@
-# RC.14 security review dossier
-
-Current decision: the [delegated AI review](RC14_DELEGATED_SECURITY_DECISION.md) is complete, with no identified open critical/high findings. Its machine-readable result is `../security-reviews/rc14-review.json` in the source checkout. This is an explicitly authorized exception to human authorship, not a human signature. The original preparation instructions and pending draft below are retained as history.
-
-## Historical preparation instructions
-
-This dossier prepares the independent human review required by HAR-HU-03. It is not a completed security review and does not authorize GA. The machine-prepared `../security-reviews/rc14-review-draft.json` (source checkout) deliberately fails the passing-review schema: reviewer, date, coverage decisions, and findings must be supplied or confirmed by the human reviewer. Copied control-map text is a review starting point, not evidence that the reviewer assessed it. The draft includes all four known findings with their technically verified remediation; the reviewer must confirm dispositions, supply owners, and add any further findings. Their presence does not establish a completed human review.
-
-The draft now includes machine-prepared source and regression references for all 10 controls, 11 trust boundaries and 31 authority-bearing tools. Technical notes incorporate the published RC14 remediation evidence; they do not carry forward the original pre-remediation findings as current defects. Residual-risk statements are proposed review inputs, not accepted risks. Every coverage decision remains pending, and reviewer identity, timestamp and finding owners remain unset. Source paths refer to the exact candidate commit below; the original automated review remains historical evidence.
-
-## Exact candidate
-
-- Tag: `v1.0.0-rc.14`
-- Commit: `d1c5abcc6d1fa482c211c4327c86f592663d559b`
-- npm: `@zhivex-ai/harness@1.0.0-rc.14` on `next`
-- SHA-512: `sha512-UMu4JFUNs/kOTJETZSJMMvVYlo+a4MKG6PoSvE313QxMEqK1z420AXVgPOGJ8jj2jp6mQud/Rvc7+ixKyH/4og==`
-- [Protected release, audit, OCI, and 42 representative cases](https://github.com/Zhivex/zhivex-harness/actions/runs/35510484383)
-- [CI at the candidate commit](https://github.com/Zhivex/zhivex-harness/actions/runs/35510241338)
-- [CodeQL at the candidate commit](https://github.com/Zhivex/zhivex-harness/actions/runs/35510241346)
-- [Registry attestation](https://registry.npmjs.org/-/npm/v1/attestations/@zhivex-ai%2fharness@1.0.0-rc.14)
-
-The release completed successfully. Meta, Qwen, and OpenAI each passed the complete 14-case inventory. Independent verification matched the published bytes, dist-tag, SLSA source/workflow binding, and exact artifact content; the protected workflow also installed and exercised the same tarball. This evidence does not replace human assessment of residual risk.
-
-## Reviewer work
-
-1. Inspect the exact tag and published artifact; verify its hash and provenance. Review [the threat model](THREAT_MODEL.md), [control map](../contracts/security-controls.json), and [schema requirements](SECURITY_REVIEW_EVIDENCE.md).
-2. Review all controls, trust boundaries, and authority-bearing tools enumerated in the draft. For every entry record the mitigation actually reviewed, regression evidence, and residual risk. Check approval replay/substitution, hostile repository instructions, protected files and symlinks, SQLite scope/concurrency, subprocess/OCI boundaries, MCP, delegation, credentials, and supply-chain identity.
-3. Review the RC.14 changes: cross-process mutation locks; full replacement review; complete OCI scope identity; required verified delivery; bounded tool selection, planning and verifier recovery; durable usage and closure reserves; terminal provider usage/tool-call fixes; task memory and candidate export scope. Inspect implementations and regression evidence, including [the tagged security regressions](reports/evidence/rc14-security-regressions-2026-09-20.json), rather than relying solely on green CI.
-4. Record all findings, including resolved ones. Non-informational findings require owner, disposition, rationale, and HTTPS follow-up. Critical/high findings must be mitigated and resolved, not merely accepted. If a fix changes runtime code, create and certify a new immutable candidate before final review.
-5. Supply your name, HTTPS identity, and actual UTC review timestamp. Only mark reviewed coverage and the document `passed` after completing the review. Save the completed JSON as `security-reviews/rc14-review.json` and submit it for validation. Do not invent a passing status to satisfy the schema.
-
-## Mechanical promotion after review
-
-Validate the completed JSON against `scripts/security-review-evidence.ts`, update the ledger from its actual timestamp and finding counts, and close the security blocker through reviewed evidence. Then prepare exact `1.0.0` version/lockfile/changelog changes, set readiness to `ready`, and run `bun run readiness:1.0:release` plus the complete release checks. Merge the promotion changes before creating the annotated `v1.0.0` tag and dispatching the protected release to `latest`. Verify npm integrity, provenance, installation, and rollback references afterward. The reviewer is not required to publish or approve npm deployment.
-
-## Evaluation limits
-
-The protected representative matrix passed 42/42 cases on this exact artifact. The separate fresh SWE-bench exploratory cohort remains 0/5 for Harness versus 1/5 for control, and its subsequent known-case development rerun remained unresolved. Those failures are preserved in [the recovery report](reports/GA_REPAIR_RECOVERY_2026-09-19.md); representative certification does not replace them or establish broad coding-agent accuracy.
-
-The post-publication [GA gate result](reports/evidence/rc14-ga-gate-2026-09-20.json) retains five explicit failures: package version, readiness phase, open security blocker, missing passing review and missing review evidence path. Published RC and representative verification produced no additional failures. That gate record is historical. The completed delegated review closes the security-specific failures; package version, readiness phase and stable publication remain separate promotion work.

package/docs/RELEASE.md

@@ -1,96 +0,0 @@
-# Release process
-
-Version `1.0.0` is the current local source release candidate; stable publication is pending. `@zhivex-ai/harness@0.11.1` remains the latest public stable release. The mutable repository [release-status.json](https://raw.githubusercontent.com/Zhivex/zhivex-harness/main/release-status.json) tracks the current candidate and is intentionally excluded from immutable npm artifacts. Its candidate source commit records the preparation baseline until an exact release commit is finalized. Publication is never performed from a development checkout. The confirmation-gated `.github/workflows/release.yml` workflow builds, inspects, certifies, transfers and publishes one exact tag-bound tarball through npm Trusted Publishing/OIDC. Creating a tag alone does not publish anything.
-
-## Deterministic gates
-
-From a clean checkout on `main`:
-
-```bash
-bun install --frozen-lockfile --ignore-scripts
-bun run release:check
-git diff --check
-git status --short
-```
-
-`bun run release:check` performs documentation validation, typechecking, deterministic tests, the golden evaluation gate, the required real-OCI boundary gate, a dependency-externalized build, package-content validation, clean tarball installation, direct binary execution, public import, SDK execution-environment import, SQLite restart/resume, redacted inspection, exactly-once side-effect verification, dependency audit, untrusted lifecycle-script inspection, dry-run packing, and release metadata validation.
-
-CI repeats the deterministic and installed-package gates on Linux and macOS. Build output is ignored and must not create tracked changes.
-
-## Live gate
-
-Provider behavior is certified separately because it is credential-, account-, model-, endpoint-, and date-dependent:
-
-```bash
-ZHIVEX_HARNESS_LIVE=1 bun run scripts/live-provider-smoke.ts
-ZHIVEX_HARNESS_LIVE=1 bun run smoke:live:orchestration
-ZHIVEX_HARNESS_LIVE=1 bun run smoke:live:routing
-ZHIVEX_HARNESS_LIVE=1 bun run smoke:live:execution
-ZHIVEX_HARNESS_OCI_REQUIRED=1 bun run smoke:oci
-```
-
-The base reviewed-edit gate and the separate delegation gate must pass for every provider in the supported release matrix. The release workflow additionally requires the mixed-provider route, model-directed execution, and representative repository gates against the exact annotated tag before the npm job can start; deterministic OCI enforcement remains a separate prerequisite. Gemini is explicitly provisional and excluded from the 1.0 cohort under [GEMINI_1_0_DECISION.md](./GEMINI_1_0_DECISION.md). Integrated provisional providers must not be described as certified. `bun run check` also runs controlled Streamable HTTP MCP interoperability gates; each external implementation claim remains bounded to the tested server/version. See [LIVE_CERTIFICATION.md](./LIVE_CERTIFICATION.md).
-
-## Exact artifact gate
-
-The release workflow performs this sequence across an unprivileged validation job and a protected publication job:
-
-1. check out an existing annotated `v<package-version>` tag with complete history;
-2. prove that the tag resolves to `main`, the worktree is clean, and the version is absent from npm;
-3. run the complete release gate with Bun-managed contributor tooling and the supported Node runtime;
-4. create one tarball with `bun pm pack --ignore-scripts`;
-5. allow only the documented package roots, verify the packed manifest, and write `SHA512SUMS`;
-6. install that same tarball in an isolated consumer and execute its CLI and public API;
-7. run the protected base, orchestration, routing, and model-directed OCI live gates from the same annotated tag and source commit;
-8. run the 14-case governed representative repository matrix for Meta, Qwen, and OpenAI against the same artifact binding and one digest-pinned OCI image; reject missing/selective/unsafe runs and upload only the strict sanitized evidence document;
-9. transfer only the tarball and `SHA512SUMS` into the `npm` environment, then revalidate the checksum and artifact contract;
-10. pass that same file to the npm CLI for the registry transaction; and
-11. retry within one absolute five-minute deadline through registry and attestation propagation, capping every request and sleep by the remaining time, then verify the distribution tag, byte-identical SHA-512 integrity, and SLSA subject/repository/workflow/ref/commit evidence. The ref must be `main` or the exact `v<package-version>` tag; arbitrary branches and tags fail closed.
-
-For a local artifact rehearsal after the source gate:
-
-```bash
-mkdir -p release-artifacts
-HARNESS_VERSION="$(node -p 'require("./package.json").version')"
-HARNESS_ARTIFACT="release-artifacts/zhivex-ai-harness-${HARNESS_VERSION}.tgz"
-bun pm pack --filename "$HARNESS_ARTIFACT" --ignore-scripts
-bun run artifact:check -- "$HARNESS_ARTIFACT"
-bun run smoke:artifact -- "$HARNESS_ARTIFACT"
-```
-
-The manual tag-bound live-certification workflow runs `bun run build` immediately before packing. This is required because its readiness preflight validates source and release identity but does not create `dist/`; a source-only tarball is not valid release evidence.
-
-`release-artifacts/`, `.npmrc`, `.env`, source tests, Git metadata, and local run state are excluded from the package.
-
-## External prerequisites
-
-Before a release dispatch, reverify repository/package visibility compatibility, protected-environment reviewers, package ownership with 2FA, and that the Trusted Publisher identity matches the repository workflow. Do not rely on a previous release's state.
-
-The release workflow intentionally supplies no long-lived registry token. Do not introduce one as a fallback; a failed OIDC assertion is a stop condition to diagnose.
-
-Trusted Publishing currently requires npm CLI `11.5.1` or newer and Node `22.14.0` or newer. The workflow follows npm's current Node 24 guidance and uses npm only for the OIDC/provenance-aware registry transaction. Dependency management, tests, and packing use Bun as contributor tooling; the built CLI, public library, SQLite reopen, and installed artifact execute under Node.
-
-## Tag and dispatch
-
-After review and merge, maintainers create an annotated `v<package.json version>` tag from the exact release commit and dispatch the protected workflow with that tag plus an explicit publication confirmation. The workflow YAML contains no release-version default: `package.json` is the source of version truth, and the required tag input is validated against it before publication. The canonical dispatch is bound to `main`; recovery is limited to the exact annotated version tag after proving it resolves to the expected commit and remains reachable from `origin/main`.
-
-The confirmation is intentional because registry versions are immutable, and the protected environment adds a second human approval boundary. Do not use a local registry session or manual upload as an alternate path.
-
-Release candidates use versions and annotated tags such as `1.0.0-rc.1` / `v1.0.0-rc.1` and must publish to `next`. Stable versions must publish to `latest`; the readiness gate rejects either channel mismatch before registry mutation. The representative assembly matrix explicitly authorizes RC.1 through RC.14 and the final `v1.0.0` tag and pins the Meta, Qwen, and OpenAI model for each, so both candidate and stable publication execute the exact unpacked tarball runtime rather than a checkout-only build. Failed immutable attempts remain in the readiness ledger but do not count toward GA. Before any `1.0.0` dispatch, `bun run readiness:1.0:release` must pass. That gate requires two complete passing RC records, current security and representative evaluation evidence, historical migration fixtures, and no open GA blocker. Every representative provider runs even after another fails; one final aggregate gate blocks publication. Every live/OCI phase, including image preload, also runs through its own fail-closed diagnostic wrapper before the aggregate decision. Failed jobs upload only bounded, strict-schema outcomes self-bound to the release tag, source commit, canonical tarball SHA-512, workflow run, and `github.run_attempt`; representative diagnostics additionally bind provider/model, driver commit, and OCI image digest. Cross-provider identity drift, a missing binding, or an incoherent passed/failed state is treated as unavailable evidence. Raw child stdout/stderr is not relayed, and raw prompts, provider output, error messages, response bodies, headers, credentials, run identifiers, and stacks remain excluded. See [GA_READINESS.md](./GA_READINESS.md), [ROLLBACK.md](./ROLLBACK.md), and [DEPRECATIONS.md](./DEPRECATIONS.md).
-
-If npm accepted the immutable version but the post-publication verifier failed during propagation, rerun only the failed `publish` job. It downloads the already validated artifact, skips `npm publish` only when the registry version has byte-identical integrity, and repeats the registry/provenance verification. Never rebuild, bump, or republish the same version to recover a post-publication false negative.
-
-## Publication stop conditions
-
-Do not dispatch or approve publication when any of these is true:
-
-- the repository is not public, the tag is not annotated, the tagged commit is not on `main`, or the worktree used to create it was dirty;
-- deterministic, installed-artifact, required live-provider, representative-repository, or release-artifact evidence failed;
-- package scope ownership, 2FA, the intended `public` access level, or the protected environment is unclear;
-- the inspected package contents and the to-be-published artifact are not the same file;
-- the package version already exists in npm;
-- an npm token or `NODE_AUTH_TOKEN` has been reintroduced into the OIDC-only workflow;
-- Trusted Publishing is expected but its repository, workflow filename, environment, or allowed action disagrees with the workflow; or
-- version, changelog, tag, registry metadata, source commit, integrity, or provenance disagree.
-
-Current npm requirements should be revalidated against the official [Trusted Publishing guide](https://docs.npmjs.com/trusted-publishers/), [provenance guide](https://docs.npmjs.com/generating-provenance-statements/), and [Bun packaging documentation](https://bun.com/docs/pm/cli/publish) before any registry mutation.

package/docs/ROLLBACK.md

@@ -1,9 +0,0 @@
-# Release rollback and recovery
-
-Published npm versions and Git tags are immutable. Never delete or reuse a version/tag and never rebuild bytes under the same version. Preserve the failing artifact, checksum, provenance, workflow URL, provider evidence, and incident notes.
-
-For a defective prerelease, leave the version on the registry, deprecate it through an authorized protected operation, publish a forward-fix RC, and move `next` only after the replacement passes the full gate. For a defective stable release, prefer a forward-fix patch. Moving `latest` back is an emergency distribution-pointer change, not deletion or state rollback, and requires an explicit protected operator action plus verification of the exact prior artifact.
-
-Before running an older harness against existing state, inspect the migration notes and schema/fingerprint compatibility. Terminal history may remain readable while active or waiting approvals are not resumable. Complete or deny an old paused approval only with the exact artifact and policy context that created it. Never rewrite fingerprints to make an incompatible approval resume.
-
-Registry propagation failures are recovered by rerunning only the failed protected publish job when it proves the already-published bytes are identical. Do not introduce a long-lived npm token as a fallback for OIDC.

package/docs/SECURITY_REVIEW_EVIDENCE.md

@@ -1,17 +0,0 @@
-# Security review evidence
-
-Harness 1.0 promotion normally requires one current, human-authored JSON review under `security-reviews/` bound to the final recorded release candidate. The reviewer must inspect the exact candidate, not a mutable branch or a different artifact.
-
-For RC14 only, the user explicitly delegated the assessment to Codex after the human-review requirement was explained. The [scoped decision record](RC14_DELEGATED_SECURITY_DECISION.md) permits the clearly attributed AI review for this candidate. It is not an independent human audit and does not change machine verification, coverage or severity requirements. Future candidates do not inherit this exception.
-
-The schema is implemented by `scripts/security-review-evidence.ts` and rejects unknown fields. A passing document records:
-
-- the exact `v1.0.0-rc.N` tag, 40-character source commit, and canonical npm SHA-512 integrity;
-- the reviewer's name and HTTPS identity plus a canonical UTC observation time;
-- successful CI, CodeQL, dependency-audit, release, provenance, and OCI evidence;
-- every finding, including resolved findings and open medium/low/informational observations; non-informational findings require an owner, mitigated/accepted disposition, rationale, and HTTPS follow-up; and
-- every declared security control, trust boundary, and authority-bearing tool with its reviewed mitigation, regression evidence, and residual risk.
-
-Open critical or high findings fail the gate, and a critical/high finding cannot be closed by acceptance alone: it must be mitigated and resolved. The control inventory must match `contracts/security-controls.json` exactly, and the authority inventory must stay synchronized with all built-in, execution-environment, delegation, skill-loading, and dynamic MCP tool classes. CI and CodeQL evidence must be successful `push` runs at the candidate commit; dependency audit, release, and OCI evidence must come from the successful protected `release.yml` workflow dispatch. Shared evidence classes may reference that same release run. The gate resolves every workflow URL through the GitHub API and rejects a mismatched URL, commit, event, workflow path, status, or conclusion. It also resolves the exact version from the npm registry, requires the recorded attestation URL and artifact integrity to match registry metadata, validates the SLSA statement against the release commit and SHA-512 digest, and binds its invocation to the recorded release workflow.
-
-The ledger fields in `docs/ga-readiness.json` are a summary only. Their timestamp and critical/high counts must equal the verified JSON inventory. Never mark the review passed until the published candidate integrity and provenance are available and a named reviewer has completed the review.

package/docs/ga-readiness.json

@@ -1,366 +0,0 @@
-{
-  "schemaVersion": 1,
-  "targetVersion": "1.0.0",
-  "phase": "ready",
-  "evidenceMaxAgeDays": 30,
-  "contractManifest": "contracts/public-api.json",
-  "stabilityPolicy": "docs/STABILITY.md",
-  "supportMatrix": "docs/support-matrix.json",
-  "securityControls": "contracts/security-controls.json",
-  "threatModel": "docs/THREAT_MODEL.md",
-  "rollbackPolicy": "docs/ROLLBACK.md",
-  "deprecationPolicy": "docs/DEPRECATIONS.md",
-  "representativeEvaluation": "evaluations/representative-matrix.json",
-  "migrationGuarantee": {
-    "configSchemas": [
-      4,
-      5
-    ],
-    "operationsSchema": 1,
-    "sessionSchema": 1,
-    "pausedApprovalPolicy": "original-artifact-only",
-    "historicalFixtures": "passed",
-    "historicalFixtureEvidence": [
-      ".github/workflows/ci.yml",
-      "fixtures/migrations/0.10.0.json",
-      "fixtures/migrations/0.10.0.sqlite",
-      "fixtures/migrations/0.11.1.json",
-      "fixtures/migrations/0.11.1.sqlite",
-      "scripts/verify-historical-migrations.ts"
-    ]
-  },
-  "securityReview": {
-    "status": "passed",
-    "criticalFindings": 0,
-    "highFindings": 0,
-    "observedAt": "2026-09-20T13:25:48.476Z",
-    "evidence": "security-reviews/rc14-review.json"
-  },
-  "releaseCandidates": [
-    {
-      "version": "1.0.0-rc.1",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/34",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.1",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "08d27d97b572f1197e66a568ba0148335e020b95",
-      "artifactSha512": "sha512-LoXIvlxphjeOG0pS8s5kwiSUCUuoC3OsK2PkqO5ENSlLwpewuIJ1HGgOXKeIptjr0e5jJTMlOvAWPYtqD2vocw==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/32674617898",
-      "provenance": "not-published",
-      "liveCertification": "failed-release-bound-run",
-      "observedAt": "2026-08-23T23:54:37Z",
-      "failedGates": [
-        "live-provider-certification",
-        "representative-evaluation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.2",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/35",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.2",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "57f465bdb44da4093152195c6bf33f9a2c3c47c2",
-      "artifactSha512": "sha512-qKAQj7ptM/5mv7NuzVea4dhl8M3GQbRNAbd+bb58Pxhbf7HxKBULoFNG5RGBrTvTeQcNP+tsNJSeuLAn0EkKrg==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/32676949946",
-      "provenance": "not-published",
-      "liveCertification": "passed-release-bound-run",
-      "observedAt": "2026-08-24T01:22:46Z",
-      "failedGates": [
-        "representative-evaluation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.3",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/39",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.3",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "d906859f74e573be37575c8fa5a953fbabd6268c",
-      "artifactSha512": "sha512-XyrEco/p6Bf86PezraBHbnLT0gqXRqygMDSu9ViBrSz1iRwAhAtFg/mzTaTScd1WkRXMIQfFOg3uTVGSNgsR3Q==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/32725445245",
-      "provenance": "not-published",
-      "liveCertification": "passed-release-bound-run",
-      "observedAt": "2026-08-24T12:31:41Z",
-      "failedGates": [
-        "representative-evaluation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.4",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/41",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.4",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "05ae8e899647207695556c896ef7a8025abcdce4",
-      "artifactSha512": "sha512-zpg7yxeQDn2nAws/AsrPd4C79IkXHm4vxWOEiGeVGiil04OcVad/pSn5kCp5nfUiZj0MlygLovBzV83MeD55GQ==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/32738506085",
-      "provenance": "not-published",
-      "liveCertification": "passed-release-bound-run",
-      "observedAt": "2026-08-24T14:45:46Z",
-      "failedGates": [
-        "representative-evaluation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.5",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/44",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.5",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "a515e87d6f898684e77dbfe415c4f8481844ca81",
-      "artifactSha512": "sha512-pCx5y+jH8J00b4+gn44y3jQ0h+elhDDNCemh0LXKNUaGumtYLUPGsonmoo9xhVwLb0sS4XomiacTHM2hSgI1EQ==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/32792078857",
-      "provenance": "not-published",
-      "liveCertification": "passed-release-bound-run",
-      "observedAt": "2026-08-25T00:26:56Z",
-      "failedGates": [
-        "representative-evaluation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.6",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/46",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.6",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "2301f5c5a2040a8319252fad2a7b0f7c9914b0ae",
-      "artifactSha512": "sha512-+dsxQBisN4S99WI5dUmiXIctGsPxvydrTS/Ri63kb6+MkoSjV0oCP0xc/G9Gxw3J4AIbqhxIV0COJvzaJmJLDg==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/32907208889",
-      "provenance": "not-published",
-      "liveCertification": "passed-release-bound-run",
-      "observedAt": "2026-08-25T23:07:35Z",
-      "failedGates": [
-        "representative-evaluation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.7",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/31",
-      "status": "passed",
-      "channel": "next",
-      "tag": "v1.0.0-rc.7",
-      "contractBreakingDefects": 0,
-      "publishedAt": "2026-08-25T23:41:47.980Z",
-      "sourceCommit": "4caa83a8011e09abda58b66c4b1d3f65d860b0cf",
-      "artifactSha512": "sha512-lXZhlDQR92SrrHZj/H5cirKIKqhiAEaQD03R7+RvJdalhbYDpQHx6TqXJFtSGUXAwGkONCfftOxNRJGrqA/FFw==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/32910606768",
-      "provenance": "verified",
-      "liveCertification": "passed-release-bound-run"
-    },
-    {
-      "version": "1.0.0-rc.8",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/31",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.8",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "db1c6917e23be73c2b4c83ed7762dc676d39f038",
-      "artifactSha512": "sha512-SaVLNFzrR2BKEyI11N7Dhx4nDrbt+3AQbD5BVaO4hex5umGP5STpyawSbk742GNUZ/MhqlzhBiS4se2DDpkhRg==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/33558133048",
-      "provenance": "not-published",
-      "liveCertification": "not-run",
-      "observedAt": "2026-09-01T20:55:44Z",
-      "failedGates": [
-        "artifact-binding"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.9",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/58",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.9",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "545b247c7b33d62c64c3c13e72faca632bae10b6",
-      "artifactSha512": null,
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/33562430984",
-      "provenance": "not-published",
-      "liveCertification": "not-run",
-      "observedAt": "2026-09-01T21:42:13Z",
-      "failedGates": [
-        "deterministic-validation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.10",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/58",
-      "status": "failed-gates",
-      "channel": "next",
-      "tag": "v1.0.0-rc.10",
-      "contractBreakingDefects": null,
-      "publishedAt": null,
-      "sourceCommit": "a6cb74e99f9f449592187663d53a40f4f7a186db",
-      "artifactSha512": "sha512-UheGnKl0z6U8To2r/IeFvj27ZVynGE8OnSu9IKPNk2zcCzVi2s5nfNLqXie8Ly+U1BblLs4dt/26tJKlV4GSbA==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/33564054752",
-      "provenance": "not-published",
-      "liveCertification": "failed-release-bound-run",
-      "observedAt": "2026-09-01T22:17:10Z",
-      "failedGates": [
-        "live-provider-certification",
-        "representative-evaluation"
-      ]
-    },
-    {
-      "version": "1.0.0-rc.11",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/60",
-      "status": "passed",
-      "channel": "next",
-      "tag": "v1.0.0-rc.11",
-      "contractBreakingDefects": 0,
-      "publishedAt": "2026-09-02T05:37:17.346Z",
-      "sourceCommit": "0deb3e3f103eac5b4ccf38c585d8149b8472a356",
-      "artifactSha512": "sha512-U/wCcN0wWpfZdyDu8zOkrU6abTnHigGa6hEt9ivSxrc8q/ev8oIvKMszzt4B9P4sO6s6naAUQz5jruASNpWNTA==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/33592828351",
-      "provenance": "verified",
-      "liveCertification": "passed-release-bound-run"
-    },
-    {
-      "version": "1.0.0-rc.12",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/32",
-      "status": "passed",
-      "channel": "next",
-      "tag": "v1.0.0-rc.12",
-      "contractBreakingDefects": 0,
-      "publishedAt": "2026-09-02T23:54:47.041Z",
-      "sourceCommit": "eb288bd3a0ef76dfbe630939d64e679437703bcb",
-      "artifactSha512": "sha512-Qpo7W9VmGvKmnX08Zr4NK15AWUuHRoMaYA9f0iAksGKxeQ3gGP2ntLv3xSwth1uJnknoT1XMMS7CtTFdy5i/eg==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/33695876968",
-      "provenance": "verified",
-      "liveCertification": "passed-release-bound-run"
-    },
-    {
-      "version": "1.0.0-rc.13",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/32",
-      "status": "passed",
-      "channel": "next",
-      "tag": "v1.0.0-rc.13",
-      "contractBreakingDefects": 0,
-      "publishedAt": "2026-09-08T18:50:18.941Z",
-      "sourceCommit": "d6e310ce12fd3ee74db5bd40451f5af70056e3ce",
-      "artifactSha512": "sha512-EhKcjH44ZvRS1Y4POhs2xnPCmw0IFQo1trKf1gusYaFMkLthwXND0+ZEkfzG25JFCCf7kfOAZabDp35SoPnubw==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/34263591864",
-      "provenance": "verified",
-      "liveCertification": "passed-release-bound-run"
-    },
-    {
-      "version": "1.0.0-rc.14",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/31",
-      "status": "passed",
-      "channel": "next",
-      "tag": "v1.0.0-rc.14",
-      "contractBreakingDefects": 0,
-      "publishedAt": "2026-09-20T12:47:20.607Z",
-      "sourceCommit": "d1c5abcc6d1fa482c211c4327c86f592663d559b",
-      "artifactSha512": "sha512-UMu4JFUNs/kOTJETZSJMMvVYlo+a4MKG6PoSvE313QxMEqK1z420AXVgPOGJ8jj2jp6mQud/Rvc7+ixKyH/4og==",
-      "workflowUrl": "https://github.com/Zhivex/zhivex-harness/actions/runs/35510484383",
-      "provenance": "verified",
-      "liveCertification": "passed-release-bound-run"
-    }
-  ],
-  "blockers": [
-    {
-      "id": "public-json-contracts",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/26",
-      "evidence": [
-        "contracts/public-api.json",
-        "fixtures/contracts/v1/doctor.json",
-        "fixtures/contracts/v1/init.json",
-        "fixtures/contracts/v1/observational-documents.json",
-        "fixtures/contracts/v1/providers.json",
-        "fixtures/contracts/v1/run-result.json",
-        "tests/json-contracts.test.ts"
-      ]
-    },
-    {
-      "id": "cli-option-contract",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/27",
-      "evidence": [
-        "scripts/package-smoke.ts",
-        "src/cli-options.ts",
-        "tests/cli-options.test.ts"
-      ]
-    },
-    {
-      "id": "complete-error-taxonomy",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/28",
-      "evidence": [
-        "scripts/package-smoke.ts",
-        "src/errors.ts",
-        "tests/errors.test.ts"
-      ]
-    },
-    {
-      "id": "historical-migration-fixtures",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/29",
-      "evidence": [
-        ".github/workflows/ci.yml",
-        "fixtures/migrations/0.10.0.json",
-        "fixtures/migrations/0.10.0.sqlite",
-        "fixtures/migrations/0.11.1.json",
-        "fixtures/migrations/0.11.1.sqlite",
-        "scripts/verify-historical-migrations.ts"
-      ]
-    },
-    {
-      "id": "consistent-state-backup",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/30",
-      "evidence": [
-        "docs/CLI.md",
-        "src/state-backup.ts",
-        "tests/state-backup.test.ts"
-      ]
-    },
-    {
-      "id": "representative-evaluation-evidence",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/31",
-      "evidence": [
-        "docs/LIVE_CERTIFICATION.md",
-        "evaluations/representative-matrix.json"
-      ]
-    },
-    {
-      "id": "security-review",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/32",
-      "evidence": [
-        "docs/RC14_DELEGATED_SECURITY_DECISION.md",
-        "security-reviews/rc14-review.json"
-      ]
-    },
-    {
-      "id": "gemini-ga-decision",
-      "status": "closed",
-      "issue": "https://github.com/Zhivex/zhivex-harness/issues/33",
-      "evidence": [
-        ".github/workflows/release.yml",
-        "docs/GA_READINESS.md",
-        "docs/GEMINI_1_0_DECISION.md",
-        "docs/LIVE_CERTIFICATION.md",
-        "docs/support-matrix.json",
-        "evaluations/representative-matrix.json",
-        "src/providers.ts"
-      ]
-    }
-  ]
-}