From 44a3334f994c4589fe55fb0a78f2aa51381ef592 Mon Sep 17 00:00:00 2001 From: archipelago Date: Fri, 9 Oct 2026 05:49:47 -0400 Subject: [PATCH] docs: clear resolved Framework startup blocker --- AGENTS.md | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index d7ce1f8e..6a971618 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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