docs: clear resolved Framework startup blocker

2026-10-09 05:49:47 -04:00
parent ecc8cc80c0
commit 44a3334f99
1 changed files with 0 additions and 24 deletions
@@ -1,27 +1,3 @@
 # Blocking incident: Framework LND startup and false zero balance
 Before starting or resuming work in this repository, read
 `docs/incident-framework-lnd-startup.md` and check its status.
 The user explicitly required this incident to take priority over later work.
 While its status is OPEN:
 - Surface this blocker at session start, including when the user asks for unrelated work.
 - Prioritize investigation and repair on the actual Framework node. If access is
  unavailable, ask for it and continue useful offline investigation; defer unrelated
  work unless the user explicitly overrides this priority.
 - A manual LND restart, a source patch, passing local tests, or publishing an OTA
  does not resolve the incident. Do not mark it fixed until the Framework's startup,
  Receive flow, and balance behavior are verified on the node, including a controlled
  reboot with access and recovery arrangements in place.
 - Preserve wallet identity, wallet/channel databases, credentials, and backups.
  Never run wallet wipe/recreation as an automatic investigation or recovery step.
 - Record evidence, changes, validation, and remaining work in the incident document.
 This priority comes from the user's explicit instruction on 2026-09-15. It remains
 in effect across sessions until the documented acceptance criteria are met or the
 user explicitly changes it.
 ## Unit tests on a live node
 Run backend unit tests through `scripts/test-backend-isolated.sh`. Do not run