Capture and verify development recovery inputs in Go #55
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/rpg-recovery-capture"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add native development capture and baseline verification with the existing two-pass source/catalog protocol. Compare complete frozen manifests and reports, and stop later host work when source bytes, scopes, checkpoints or identity change.
Validation: full Go race suite, vet, 150 retained Python tests and actual Linux arm64 subprocess tests passed. Controls cover all eight host requests, late source mutation, report-write failure, timeout, cancellation and credential redaction. Active recovery entrypoints remain unchanged.
Pull request closed