diff --git a/CLAUDE.md b/CLAUDE.md
index bf1d98d3..78b11433 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -1,13 +1,18 @@
 # Archipelago — agent guide
 
-## 🚩 TOP PRIORITY (until production testing passes)
+## ✅ Single-node production gate is GREEN (2026-06-23)
 
-**Read `docs/PRODUCTION-MASTER-PLAN.md` first.** It is the authoritative plan and
-overrides ad-hoc direction until the production test gate is green. Goal: a
-world-class, **developer-ready app platform** where every app is manifest-driven,
-manifests ship via the **signed registry** (not OTA disk files), and **third-party
-developers publish apps via an external/decentralized registry** — all rootless,
-secure, robust, and 100%-uptime-capable.
+`tests/lifecycle/run-gate.sh` is **5/5 on .228, 0 failures** — the single-node exit
+criterion is met and the priority banner is demoted. Next exit-criteria: the
+**multinode pass** (`docs/multinode-testing-plan.md`) and workstreams B/C/D.
+
+**Read `docs/PRODUCTION-MASTER-PLAN.md` first** — it is still the authoritative plan
+for the north star: a world-class, **developer-ready app platform** where every app
+is manifest-driven, manifests ship via the **signed registry** (not OTA disk files),
+and **third-party developers publish apps via an external/decentralized registry** —
+all rootless, secure, robust, and 100%-uptime-capable. It no longer overrides all
+ad-hoc direction now that the gate is green, but it remains the source of truth for
+sequencing the remaining workstreams.
 
 Detailed sub-plans (all linked from the master):
 - App platform / packaging phases + security model → `docs/APP-PACKAGING-MIGRATION-PLAN.md`
@@ -45,6 +50,8 @@ Detailed sub-plans (all linked from the master):
 `tests/lifecycle/run-gate.sh` green across install / UI / stop / start / restart /
 reinstall / reboot-survive / archipelago-restart-survive / uninstall — **5× on
 .228** (`ARCHY_ITERATIONS=5`). **Run the gate ON the node** (it uses local podman/systemctl/bitcoin
-probes), not via RPC from another host. Until green, the master plan is the priority.
+probes), not via RPC from another host. **✅ GREEN 2026-06-23 (5/5, 0 not-ok)** — keep it
+green (re-run after orchestrator/lifecycle changes); regressions are top priority again.
 **Multinode testing (.198 + the rest of the fleet) is a SEPARATE plan** —
-`docs/multinode-testing-plan.md` — not part of this single-node gate criterion.
+`docs/multinode-testing-plan.md` — not part of this single-node gate criterion, and is
+the next exit criterion now that single-node is green.