Verify the Zelnet release chain and pub400 restore methods #27
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/recovery-release-evidence"
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?
Record the published Zelnet v0.10.7 binary, ibmi-builder v13 digest, active consumer catalog, and real development/staging capture checks. The lemonade release deployed with object identity verified.
Add a scoped restore probe with collision guards, data comparison, bounded observation, and owned-object cleanup. Provider RESTOBJ failed to restore the test table; a retained CRTDUPOBJ copy restored it successfully. The evidence distinguishes file-copy restore from saved-file restore. The full reference restore gate remains closed.
Validation: 25 Python tests pass. Live reports retain each failed provider restore and the successful retained-copy restore. No application source was removed.