6 Commits

Include renames

Author	SHA1	Message	Date
archipelago	169bf77de6	Add headless Angor services and shared-index install guard	2026-09-30 11:52:19 -04:00
archipelago	77d0768a21	fix(nginx): stop pinning HSTS — actively clear it instead ... The HTTPS server block sent Strict-Transport-Security: max-age=31536000; includeSubDomains. Browsers that visited HTTPS once cached the policy and then silently upgraded the still-open HTTP dashboard's fetches and frames to https — a scheme change is cross-origin, so every /rpc/v1 call died 'No Access-Control-Allow- Origin header' while the node was perfectly healthy (framework-pt 2026-09-01: the 'Failed to fetch' storm, dashboard 'not responding', every app frame mixed-content-blocked). Plain HTTP is a supported access mode BY DESIGN on this platform: the node's certificate is optional and self-signed (Settings → Node certificate, /ca.crt flow), and setup-node-ca.sh deliberately keeps port 80 serving for devices that haven't installed the CA. So: - port 80 sends no HSTS at all (with the rationale inline) - port 443 sends max-age=0, which ACTIVELY DELETES the policy already cached by affected browsers — leaving it absent would have kept every stranded browser broken for a year tests/lifecycle/bats/nginx-hsts.bats pins all three properties at the gate: no live policy on :80, max-age=0 (never 31536000) on :443, and no long-lived pin anywhere in the deployed config.	2026-09-01 10:28:57 -04:00
archipelago	cbd5314dd9	fix(lnd): pay through Router.SendPaymentV2 — LND 0.21 removed the old route ... LND 0.21.2 removed the deprecated Lightning.SendPaymentSync REST route (/v1/channels/transactions). The backend still called it, so every Lightning send answered literal HTTP 404 and the wallet UI reported 'Payment failed: Not Found' fleet-wide right after the pin bump — receive worked, which made it look intermittent. Pay through the supported Router.SendPaymentV2 route (/v2/router/send) instead, keeping the existing contract with the UI: - single-record responses (no_inflight_updates) unwrapped from the grpc-gateway result envelope, transport errors from the nested error - a slow multi-hop payment still resolves as pending + payment hash (only LND may declare failure), never a false 'Payment failed' - LND's failure_reason codes translated to the same plain-language advice, invoice-expiry still says 'ask for a fresh invoice' Guard it at the gate: tests/lifecycle/bats/lnd-api-compat.bats POSTs a deliberately-invalid invoice to /v2/router/send on the RUNNING LND and fails if the route answers 404 — the image/backend skew that shipped silently last time because no test ever spoke the payment endpoint. Also bumps the stale lnd image expectation in remote-lifecycle.sh.	2026-09-01 10:28:49 -04:00
archipelago	54431fc856	fix(host): enforce the full kdump crash reservation	2026-08-31 09:16:18 -04:00
archipelago	cbd463e980	feat(host): crash/hardware-error capture, delivered by a new host-fixup OTA channel (#144) ... kdump + rasdaemon on every node, per docs/kdump-rasdaemon-design.md with the approved decisions: hang capture ON (a wedged kiosk dumps and reboots itself instead of sitting dead), crashkernel=256M, backfill ships with this release, phase-2 UI surfacing deferred. Host fixups (docs/system-level-ota-design.md) are the general answer to 'deliver system-level updates OTA': curated OS packages, sysctl drop-ins, service enablement and the GRUB crashkernel line, carried by the signed binary and applied idempotently at startup — non-fatal by construction (offline/locked-dpkg nodes converge on a later boot), skipped on dev boxes and non-Debian hosts. This formalizes the polkit/audio repair precedents into a channel with a stated policy: pinned packages and parameter intent only, never dist-upgrade automation; the ISO bakes the identical end state into fresh installs (next commit). The one runtime limitation is honest: crashkernel memory can only be reserved at boot, so the fixup writes GRUB, runs update-grub, and logs that it takes effect on the next reboot. tests/lifecycle/os-audit.sh gains section D — a graded baseline check: FAIL if capture never landed, WARN if written but awaiting reboot, PASS when reserved, policy live and rasdaemon recording. Section D runs independently of RPC health: a wedged backend must not mask that the node also stopped capturing evidence. Verification: host_fixups unit tests 4/4; cargo fmt clean; full suite runs in the release gate (create-release) and the archi-dev-box lifecycle gate before the tag.	2026-08-31 07:23:44 -04:00
Archipelago	b67e1527a2	Archipelago — open-source initial import	2026-08-12 10:55:50 +00:00