fix: harden evidence publication and offline buyer auditing

[afelin]

Changing evaluated inputs without changing findings could leave identical evidence, and interrupted or escaped writes could produce a misleading review pack. This change binds exact inputs and time, publishes a verifiable completed artifact set, and extends the existing offline review engine to check it.

This successor preserves the commits from #57 and adds the takeover repairs. Review this PR for the combined change; #57 has not been merged or discarded.

• Fix cooperative writer ownership/recovery, resolved .git and symlink escapes, VEX/SBOM/share output containment, and preparation errors hidden by share.
• Add versioned evaluation/receipt contracts with explicit --as-of, exact pack/input/method identity, immutable digest-addressed objects, verified cache reads and historical adapters. Freshness uses the selected instant; operational metadata stays in receipts.
• Stage all release artifacts before replacement and publish a full-hash manifest last. Ship canonical evaluation and receipt objects; verify artifact sizes/hashes, schemas and legacy adapter bindings offline.
• Keep integrity, authenticity, completeness and applicability separate. Offline subject commits remain claimed; unsigned hashes never establish signer trust. Preserve historical report/result digests, use unique failed-gate tallies and suppress incompatible trends.
• Capture custom-home redaction context for derived crossings and refuse leaking canonical evidence before publication. Keep current Action and CLI release pins unchanged.

Validation: fresh go test ./... -count=1, build, vet, affected race tests including review/CLI, gauntlet, claim safety, focused behavioral regressions and actual Action resolver all passed. Public assets passed 17 tests including real Chrome checks; versioned schemas/goldens passed Draft 2020-12 validation. Windows CLI cross-compilation passed. All five published v0.5.5 binaries matched downloaded release checksums; its macOS amd64 installer, installed version and scan were tested separately.

Tester instructions and the remaining acceptance boundary are in docs/production-hardening-audit.md. Test this branch explicitly: the default installer still installs published v0.5.5. Native Linux/Windows installation, broader interruption/fault injection and remaining crossing-format coverage are not claimed complete. Human merge, release, attestation, outreach and pin promotion remain separate; this PR does not assert broad production readiness.

Prior-report integrity follow-up at fb194fe4dcda8b436f0230f7080d2a4613e76552: the shared review engine rejects unsupported schemas and missing or mismatched prior record digests before deriving a trend or linking a child report. Six CLI mutation cases reproduced success before the fix in pack and repository modes; they now exit 2 without JSON output. Historical baselines and existing verify-chain behavior remain supported. Local review/CLI/export suites, review race tests, affected vet, build, repository check and an actual-binary valid/tampered baseline probe passed. All nine GitHub checks passed on this commit: Ubuntu/macOS suites, Linux and Windows smoke, red-team, gauntlet, Action dogfood, pin guard and required-context drift. CI run.

Pre-beta acceptance review at bf61c02: recommend merge for a small, explicitly selected source-build trial after final checks pass. The actual doctor → scan → check → demo → share --bundle → relocated offline review journey passed with custom HOME/TMPDIR and spaced paths. This uncovered a bundle published after the manifest; the repair now stages and hashes it with the current one-pager. Its regression reproduced red before the fix and now verifies complete coverage plus tamper detection. Controlled process interruption also passed: second writer refused, live recovery refused, killed-owner recovery succeeded, re-emission verified. Fresh full uncached tests, affected races, vet, build, browser tests, real OpenSSH fixture and separate macOS v0.5.5 install smoke passed. All nine final GitHub checks passed on bf61c02cfcf16c3ca68dbbc1c34aabc618785a0d: CI run.

The friendly-user handoff records scope, commands and deferred acceptance. Corrected stale v0.5.4 human-runbook instructions. Live social metadata and PNG were checked; Slack/LinkedIn unfurls and independent human comprehension were not claimed. No A2/A3 human pass, merge, release, attestation, outreach or pin promotion was performed.

The additional blank-repository trial passed: write-free scan, redirected init --bare, expected failing check/share on draft scaffolds, and successful integrity review of the remediation pack. The in-app browser security policy blocked opening the temporary local HTML bundle, so its visual cold-read remains unverified; no workaround was attempted.

[github-actions]

Curbpack check

✅ Gates green — readiness 100%

Prepares evidence for human review — not a conformity assessment or certification.