diff --git a/portability.md b/portability.md
index 752f8eb..b2f2093 100644
--- a/portability.md
+++ b/portability.md
@@ -10,6 +10,7 @@
   README.md   how-i-work.md   portability.md   retrofit-playbook.md   subagents-handbook.md
   ROADMAP.md               ← this repo's backlog (future agents, commands, standards)
   INBOX.md                 ← cross-project capture buffer (/capture → here, /triage drains it)
+  STATUS.md                ← cross-project roundup snapshot (overwritten + committed by /roundup)
   guides/                  ← neutral substance (vendor-agnostic): checklists, role knowledge
   adapters/
     claude/
diff --git a/retrofit-playbook.md b/retrofit-playbook.md
index 6d2b175..d49e264 100644
--- a/retrofit-playbook.md
+++ b/retrofit-playbook.md
@@ -145,7 +145,7 @@ Your Mac is now the single point of failure; this removes it. Gitea is just a gi
 
 3. The SSH key is one-time; for each additional project, just create the empty Gitea repo and say "add my Gitea remote at URL and push."
 
-**The one tradeoff:** Claude's cloud Code sessions (web, and the mobile app's cloud mode) can only clone from GitHub, so Gitea-only means no phone-initiated cloud sessions. Your phone can still monitor and steer sessions running on your Mac — type `/mobile` in a session for a QR code. Want both? Add GitHub as a second remote later; git pushes to both happily.
+**The one tradeoff:** Claude's cloud Code sessions (web, and the mobile app's cloud mode) can only clone from GitHub, so Gitea-only means no phone-initiated cloud sessions. Your phone can still monitor and steer sessions running on your Mac — type `/remote-control` (or `/rc`) in a session for a QR code to scan from the Claude app. Want both? Add GitHub as a second remote later; git pushes to both happily.
 
 ---
 
diff --git a/subagents-handbook.md b/subagents-handbook.md
index 8f1ffe7..032f33a 100644
--- a/subagents-handbook.md
+++ b/subagents-handbook.md
@@ -89,6 +89,8 @@ least one.
 | researcher | compression | Multi-source web research → cited brief | ✅ in kit |
 | janitor | compression | Spring-clean docs/artifacts: report stale, orphaned, superseded files | ✅ in kit |
 | doc-auditor | independence | Doc drift: every README/instruction/HTML claim checked against the code | ✅ in kit |
+| design-checker | independence | Design compliance: code checked against the repo's committed design brief + tokens | ✅ in kit |
+| onboarding-tester | independence | Fresh-adopter simulation: reach the goal from published docs alone | ✅ in kit |
 | test-runner | compression | Run the suite, return only failures + causes | build when a repo has a real suite |
 | docs-reader | compression | Read a library's docs, return just the calls you need | build on 3rd manual-trawling task |
 | fresh-debugger | independence | Gets symptoms only (never your theories), hunts the bug | build next time you're stuck >1hr |
@@ -259,7 +261,8 @@ Three real options:
 1. **Slash command (this kit's choice): `/full-eval`.** A command file is just a stored
    prompt for the *main thread* — and the main thread *can* fan out. `/full-eval` makes
    it launch evaluator + security-auditor + exerciser + doc-auditor (+ start9-spec-checker
-   when relevant) in parallel, then synthesize one deduplicated, prioritized report. Zero new
+   when relevant, + reviewer when the tree has uncommitted changes) in parallel, then
+   synthesize one deduplicated, prioritized report. Zero new
    machinery, works in any session.
 2. **`claude --agent <name>` (advanced).** A session launched this way takes the agent's
    system prompt as its main thread — and a main-thread agent *can* spawn subagents,