fix(audit): match export ownership and inventory receipts in browser

This commit is contained in:
2026-10-20 21:42:34 +01:00
parent bb32383bbe
commit dce2d759d7
7 changed files with 75 additions and 9 deletions
+35
View File
@@ -43,3 +43,38 @@ handoff files. Historical public repair paths remain verifiable for compatibilit
Only unowned injected test executors are exempt from native-session enforcement.
An original computation failure routed directly to failure stays a failure even
when its best-effort diagnostic export cannot be recovered.
## Verification (2026-10-20)
Integrated changes use authenticated direct V2 API exports, tracked text-only
model prompts, and native settled Pi JSONL export. V1 retains its native CLI
export path. Native messages are retained as escaped JSON alongside the readable
HTML projection so provider metadata and inline tool content are not dropped.
The original run #19 sessions were read without running any stage or changing
production evidence. Complete, nontruncated HTML exports in the approved
OpenCode temporary `run19-export-proof/` directory contained:
| Stage | Messages | HTML bytes |
| --- | ---: | ---: |
| Survey | 14 | 1,253,234 |
| Code | 11 | 325,930 |
| Review | 10 | 308,622 |
| UIReview | 16 | 1,358,507 |
| Land | 11 | 320,557 |
The old CLI silently cut exports at 262,144 bytes. These readbacks verify recovery
is possible for these exact original sessions; they are not production repair
records. Historical message-less `/generate` sessions cannot be reconstructed.
Checks passed after integration: full Go suite, build/vet, focused gate/recovery
race tests, and browser audit fixtures. The browser fixture verifies export-only
retry and refresh of an already-open Session tab. Large (>256 KiB) API fixtures,
wrong identity, partial/empty exports, restart, cancellation, workspace reservation,
and exactly-once successor admission have focused regressions. A full ordinary
artifact inventory no longer blocks versioned audit repair.
No shared service was restarted or redeployed. Production run #19's original
evidence remains unchanged. A new real multi-stage run against the installed
gate and native Linux execution remain unverified; source tests and read-only
native readbacks do not substitute for those deployment checks.