feat: capture real IBM i programs and validate independent recovery #45
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/deterministic-recovery-tool"
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?
Missing IBM i source can now be captured as reusable Git text through declared application scopes and checked executable extraction. Native editors remain in use. The tool records source, SQL definitions, object metadata, loaded memory, instructions, and explicit recovery limits.
The offline path validates the observed V7R5 uncompressed save-file container, restores the displaced tail bytes, checks program segments and entry points, and runs pinned Ghidra/PowerAS with verified tool-file hashes. It rejects corrupt evidence, changed inputs, metadata filename collisions, incomplete analysis, and timeouts. Permission denials remain visible as skips. Application-specific rules live in the fixtures.
The controlled pricing retry removed one implementation member and runtime observability after verified source and executable backups. A fresh agent received only the captured executable text, two surviving members, and 96 observed calls. Its first frozen RPG candidate compiled in SOMEARA2 and passed all 13,166 native cases, including 13,070 cases not supplied to the agent. The parent did not change its business logic. A later native source capture matched the frozen candidate byte for byte.
Validation:
The supported extractor format is limited to the observed uncompressed V7R5 QSYS and ILE layouts. The Python reader checks each record but does not yet check the separate whole-file checksum. Ghidra misses part of the calculation body; the agent used captured memory and a small documented decoder as an analysis aid. This is useful reconstruction evidence, not proof of complete semantic equivalence or original source recovery. The evidence boundary is procedural on a shared filesystem.
See recovery/RETRY.md, recovery/NATIVE-WORKFLOW.md, and recovery/evidence/reusable-capture-20260910/summary.json. The current Binjovi recipe checks and releases the recovery tool. This retry validates staging; automatic promotion for arbitrary application scopes and off-host save-file restoration remain separate work.
Binjovi Build
105aa21b3b37bb8f38688aa4392f3911caee10a599cc8e24359c2cf858544fb4succeeded for exact feature revision06f1e9c502fe77c617348885a470d4825f07e37a. Its native executor log confirms all 143 offline tests passed.feat: add deterministic IBM i recovery text bundlesto feat: capture real IBM i programs and validate independent recovery