feat(loss): add the routine mode the deploy applies after every deployment #40
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/routine-loss"
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?
Routine source loss after every deployment
This application is synthetic. To stand in for one developed over decades, every Binjovi deployment now ends in the decades-old condition: the
routineprofile members are gone from SOMEARA1 and the profile's objects are stripped of observability in SOMEARAB and SOMEARA1. The originals stay in Git; the next Build re-uploads and recompiles.scripts/source-loss.sh routine --profile recovery/loss-profile.json --development SOMEARA1 --production SOMEARAB --report FILE(the ibmi-rpg runner calls it once the recipe declaresloss_profile, in a follow-up plans PR).ibmi-source-loss-report.v3.output_repositorybecomesrpg-lemonade-tng.ADDPFM) before bridging source.tests/check-source-loss.sh: full run, idempotent second run, staging refusal, argument checks, denied strip; the fake host gained the release members, the production library and type-aware markers.https://claude.ai/code/session_01HPdKaFBKQVs8hzfgXMrnwV