feat(recovery): prove native runtime restore and gate source loss #33
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/native-recovery-workflow"
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?
Capture all 17 native members and the mixed RPG program inventory. Retain 50 object copies and 20 SQL definitions, restore the complete runtime, and verify exact data, source, bindings, constraints, journals, and native business behavior before source loss.
The live restore passed a controlled interruption and restart. It found and fixed unsupported journal receiver rename and copied constraint-name collisions. The published Zelnet v0.10.10 client passed all 13 restored business checks and five screen checks. Audit IDs remain unique and increasing. Saved-file and account-loss restore remain unproven.
Pin and test Ghidra/PowerAS. The processor test passed; the actual save-file import failed and is recorded without claiming recovered RPG. Require explicit import and analysis success even when Ghidra exits zero.
Validation: 60 offline tests; live pub400 restore, native source and object verification, SQL structure and data comparison, and greenscreen business checks. Includes the completed Zelnet v0.10.10 → builder v15 → lemonade v0.1.12 staging/production proof. Source-loss execution is the next gate.
feat(recovery): capture native source and service bindingsto feat(recovery): prove native runtime restore and gate source loss