Skip to content

Defensive hardening ports: chain-state CAS guard, snapshot cleanup guard, incident-journal custody - #326

Open
peteromallet wants to merge 5 commits into
mainfrom
integrate/cleanup-ports-20260809
Open

Defensive hardening ports: chain-state CAS guard, snapshot cleanup guard, incident-journal custody#326
peteromallet wants to merge 5 commits into
mainfrom
integrate/cleanup-ports-20260809

Conversation

@peteromallet

Copy link
Copy Markdown
Owner

Ports 3 defensive fixes from box cleanup 2026-08-09 (recovery branch evidence in recovery/box-cleanup-20260807):

  1. 2bd0b2d → chain-state CAS guard — fcntl file lock + sha256 revision tracking on chain/spec.py save, refusing stale writes / cursor / completed-set regression.
  2. 9f9982c → snapshot-wrapper cleanup identity guard — the EXIT-trap rm -f ${BASH_SOURCE[0]} in the 4 cloud wrappers now refuses to delete anything not under $TMPDIR (prevents deleting the installed wrapper).
  3. 6152c5b → incident-journal custody root — cloud-session incident journals go under $ARNOLD_INCIDENT_LEDGER_ROOT, not into immutable runtime candidates.

Each ported manually onto current main (files had diverged); tests ported + green (15/15 confirmed). Scoped down from a larger port set per operator review — only the unambiguously-defensive fixes. No shannon, no prompt/routing changes.

@peteromallet
peteromallet force-pushed the main branch 8 times, most recently from 132ff1a to c29d5f1 Compare August 11, 2026 04:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant