sandbox: move STATUS files into status/

Tidy the directory: the 29 per-phase + per-plan landing records
(STATUS-phase-*.md, STATUS-plan-*.md) move out of the sandbox/ root into
sandbox/status/ (git mv, blame preserved). Live current-state docs
(CLAUDE.md, README.md, OVERVIEW.md, FOLLOWUPS.md, architecture.html, the
docker-compose harness comment) now point at status/. Historical records
(the STATUS bodies themselves, plans/*.md, plan.md) keep their original
text by convention.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

sandbox/CLAUDE.md

@@ -26,8 +26,9 @@ second condition), as a deliberate call relying on git history for rollback.
   ([`docs/design-share-states.md`](docs/design-share-states.md))
   rather than dead-flag carrying. See
   [`docs/FOLLOWUPS.md`](docs/FOLLOWUPS.md) for the narrative.
-- [`STATUS-phase-N.md`](.) — the authoritative landing notes for each
-  phase. **Always check the latest STATUS file before assuming
+- [`status/`](status/) — per-phase (`STATUS-phase-N.md`) and per-plan
+  (`STATUS-plan-*.md`) landing notes, the authoritative record of what each
+  phase/plan shipped. **Always check the relevant STATUS file before assuming
   something is wired up the way the plan describes** — phases
   deliberately defer or simplify items and note exactly what
   changed.

sandbox/OVERVIEW.md

@@ -17,8 +17,9 @@
 > (Phase 20). v1 (`../sandbox/`) was removed 2026-05-28 — recover from
 > git history if needed. See [`plan.md`](plan.md) for
 > the phase-by-phase task list, [`docs/FOLLOWUPS.md`](docs/FOLLOWUPS.md)
-> for the narrative history of Phases 12+, and the per-phase
-> `STATUS-phase-N.md` files for what each phase shipped, what it
+> for the narrative history of Phases 12+, and the
+> [`status/`](status/) landing notes (`STATUS-phase-N.md` +
+> `STATUS-plan-*.md`) for what each phase/plan shipped, what it
 > deferred, and what it flagged forward.
 
 ## Goal
@@ -594,9 +595,9 @@ the phase that resolved each one.
 
 ## Where to look in the code
 
-The per-phase `STATUS-phase-N.md` files in this directory are the
-authoritative record of what each phase actually built, what it
-deferred, and what it flagged for the next phase. For a quick map:
+The landing notes under [`status/`](status/) (`STATUS-phase-N.md` +
+`STATUS-plan-*.md`) are the authoritative record of what each phase/plan
+actually built, what it deferred, and what it flagged forward. For a quick map:
 
 | Concern | HA Core side | Sandbox side |
 |---|---|---|

sandbox/README.md

@@ -23,8 +23,9 @@ numbers and shipped at least one stable release. See
     enforces it (Phase 7).
 - `plan.md` — the implementation plan that drives this work.
 - `OVERVIEW.md` — architecture document.
-- `STATUS-phase-N.md` — per-phase landing notes: what each phase
-  built, what it deferred, what it flagged forward.
+- `status/` — per-phase (`STATUS-phase-N.md`) and per-plan
+  (`STATUS-plan-*.md`) landing notes: what each phase/plan built, what it
+  deferred, what it flagged forward.
 - `run_compat.py` + `COMPAT.md` — compat-lane runner and report.
 
 The HA Core side of the integration lives at
@@ -122,8 +123,8 @@ Phases 0–17 landed:
   pass rate from 98.07 % to **99.67 %** (above the 99.5 %
   v1-removal threshold).
 
-The per-phase `STATUS-phase-N.md` files are the authoritative record
-of what each phase actually built, what it deferred, and what it
-flagged forward; [`docs/FOLLOWUPS.md`](docs/FOLLOWUPS.md) tells the
+The `status/` landing notes (`STATUS-phase-N.md` + `STATUS-plan-*.md`) are
+the authoritative record of what each phase/plan actually built, what it
+deferred, and what it flagged forward; [`docs/FOLLOWUPS.md`](docs/FOLLOWUPS.md) tells the
 narrative story of Phases 12–17 (what each one's predecessor
 flagged, what landed, the outcome).

sandbox/architecture.html

@@ -2309,9 +2309,9 @@
       <p>
         The bridge landed in 17 phases over several months. Each phase had a
         single concrete deliverable, a status doc
-        (<code>STATUS-phase-N.md</code>) explaining what it actually shipped,
-        and explicit notes on what it deferred forward. The status files are the
-        authoritative record &mdash; this is the abridged tour.
+        (<code>status/STATUS-phase-N.md</code>) explaining what it actually
+        shipped, and explicit notes on what it deferred forward. The status
+        files are the authoritative record &mdash; this is the abridged tour.
       </p>
 
       <div class="timeline">
@@ -2632,9 +2632,9 @@
       <h2 id="code-map">14. Where to look in the code</h2>
 
       <p>
-        Per-phase <code>STATUS-phase-N.md</code> files are the authoritative
-        record of what each phase actually built. For a quick map of the
-        codebase:
+        Per-phase <code>status/STATUS-phase-N.md</code> files are the
+        authoritative record of what each phase actually built. For a quick map
+        of the codebase:
       </p>
 
       <table>
@@ -2772,7 +2772,7 @@ cd sandbox && python run_compat.py
         0&ndash;17 landed &middot; Source of truth:
         <span class="kbd">sandbox/OVERVIEW.md</span>,
         <span class="kbd">sandbox/plan.md</span>,
-        <span class="kbd">sandbox/STATUS-phase-N.md</span>,
+        <span class="kbd">sandbox/status/STATUS-phase-N.md</span>,
         <span class="kbd">sandbox/docs/*.md</span>.
       </footer>
     </div>

sandbox/docs/FOLLOWUPS.md

@@ -8,9 +8,9 @@ follow-ups that closed those forward-flags in turn. This file is the
 phase's landing.
 
 Per-failure remediation entries live in [`BACKLOG.md`](../BACKLOG.md);
-deep landing notes live in the per-phase `STATUS-phase-N.md` files in
-the parent directory. FOLLOWUPS.md is the connective tissue between
-them.
+deep landing notes live in the [`status/`](../status/) files
+(`STATUS-phase-N.md` + `STATUS-plan-*.md`). FOLLOWUPS.md is the connective
+tissue between them.
 
 ---
 

sandbox/hass_client/docker-compose.test.yml

@@ -5,7 +5,7 @@
 # │ INTENDED two-container shape so it is ready when the manager grows the  │
 # │ capabilities below. It is valid YAML (`docker compose config` parses    │
 # │ it), but `docker compose up` will not produce a working sandbox today.  │
-# │ See docs/docker.md → "Compose harness gap" and STATUS-plan-docker.md.   │
+# │ See docs/docker.md "Compose harness gap" + status/STATUS-plan-docker.md │
 # └───────────────────────────────────────────────────────────────────────┘
 #
 # Why it can't run yet (two manager gaps, neither hacked here):