From d68a013e3589703c339fb450a75ea147c2e501fa Mon Sep 17 00:00:00 2001 From: archipelago Date: Tue, 1 Sep 2026 11:43:33 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20tracker=20=E2=80=94=20v1.8.9=20publishe?= =?UTF-8?q?d,=20NPM=20live-healed=20on=20shorty=20via=20the=20signed=20cat?= =?UTF-8?q?alog;=20funding-gate=20fix=20staged=20for=20v1.8.10?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/incident-2026-09-01.md | 26 ++++++++++++++++++++------ 1 file changed, 20 insertions(+), 6 deletions(-) diff --git a/docs/incident-2026-09-01.md b/docs/incident-2026-09-01.md index a8d8bd97..28493bfa 100644 --- a/docs/incident-2026-09-01.md +++ b/docs/incident-2026-09-01.md @@ -52,13 +52,27 @@ built and verified to embed the alias fix. `cargo fmt` applied. | D1 shorty NPM crash-loop stopped cleanly (user-stopped marker; public hosts keep serving via host nginx mirror) | ✅ 12:52Z | | D2 shorty live nginx HSTS patch + reload | ✅ verified: :80 and :443 both answer `max-age=0` | | D3 Regenerate catalog (releases/app-catalog.json + store copies) | ✅ semantic diff = exactly the two NPM fixes | -| D4 **User runs `scripts/sign-catalog.sh`** (signer built at /tmp/archy-sign-bin) | ⬜ waiting on mnemonic | -| D5 Commit + push (origin + gitea-vps2 OTA mirror) | ✅ 6 commits pushed (signed catalog commits after D4) | -| D6 Release v1.8.9-alpha: `scripts/create-release.sh 1.8.9-alpha` (mnemonic) → `scripts/publish-release-assets.sh 1.8.9-alpha gitea-vps2` | ⬜ waiting on mnemonic | -| D7 OTA on shorty-s + framework-pt (Update button; framework-pt has no SSH from here) | ⬜ | -| D8 shorty: clear the NPM user-stopped marker + Start (or it starts via the fixed catalog) | ⬜ | +| D4 **User runs `scripts/sign-catalog.sh`** (signer built at /tmp/archy-sign-bin) | ✅ catalog signed + committed + pushed | +| D5 Commit + push (origin + gitea-vps2 OTA mirror) | ✅ 9 commits pushed | +| D6 Release v1.8.9-alpha: `scripts/create-release.sh 1.8.9-alpha` (mnemonic) → `scripts/publish-release-assets.sh 1.8.9-alpha gitea-vps2` | ✅ PUBLISHED (tag v1.8.9-alpha, releases/manifest.json live, backend+frontend assets verified by the script) | +| D7 OTA on shorty-s + framework-pt (Update button; shorty is on 1.8.8-alpha, daily check — hit Update now) | ⬜ user action | +| D8 shorty: clear the NPM user-stopped marker + Start (or it starts via the fixed catalog) | ✅ NPM LIVE-HEALED via the signed catalog: unit regenerated with both fixes, container up, admin UI HTTP 200 on :8081 (verified 15:42Z) | | D9 framework-pt: Start Mempool — its containers are confirmed stopped (port 4080 refuses; gate answers on 7778/8334/50002/18083 so those apps will embed over https immediately) | ⬜ | -| D10 Post-deploy live checks: LND send+receive; mempool/IndeeHub/bitcoin-UI frames over https; NPM healthy + admin :8081; portainer token card on fresh DB; zero CORS errors | ⬜ | +| D10 Post-deploy live checks: LND send+receive; mempool/IndeeHub/bitcoin-UI frames over https; NPM healthy + admin :8081 ✅; portainer token card on fresh DB; zero CORS errors | ⬜ after nodes update | + +## E. Follow-ups discovered during the incident (ride the NEXT release, v1.8.10+) + +- **Funding-modal honesty fix landed after the v1.8.9 tag** (1464b1b2): the + Lightning "no channel" modal now states the node's real state — pending + channel confirming / balance on the far side / payment couldn't route / + genuinely no channels. Ships in the next release; needs its own + create-release run (one more mnemonic paste). The CHANGELOG entry for + v1.8.10 should carry it. +- Nodes poll for OTA updates on `daily_check` — after publishing, tell the + user to hit Update rather than wait for the next check. +- `origin` remote had a stale pushurl with a dead token (pushes failed); + fixed to the canonical repo URL, stale `~/.git-credentials` entry with an + encoded port removed. framework-pt immediate workaround until its OTA lands: open the dashboard by IP (`http://192.168.x.x`) instead of `framework-pt.local`, and/or clear the