Update restructure status: 7 units out, 3 subsystems left

Also records that syncyomi-guard has been red since 00:00 today for
reasons unrelated to this work -- the library collapsed to 8 manga and
the guard is correctly refusing to let it pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJrqKERAo5QUeEHWS5Asgp

NEXT_SESSION_RESTRUCTURE.md

@@ -39,23 +39,19 @@ Depth, tests and pre-commit verified green at every commit; nothing used
 
 ## Remaining, in order
 
-1. `system-maintenance` — no cross-unit source edges.
-2. `android_guardian` (`periodic_background/utils/`) — settle
-   `heavy_job_lock.sh`. The seam is already clean: consumers read the
-   _installed_ `/usr/local/bin/heavy_job_lock.sh` and
-   `meta/scripts/run_with_heavy_lock.sh` documents a "missing lock ⇒ run
-   unserialised" fallback.
-3. `hosts` — owns `/etc/guard-lib/targets/{resolved,nsswitch}.conf` plugin
+1. `hosts` — owns `/etc/guard-lib/targets/{resolved,nsswitch}.conf` plugin
    paths. Confirm `guardctl status` after, not just that files moved.
-4. `phone_focus_mode` + `python_pkg/focus_policy` — must come after `hosts`:
+2. `phone_focus_mode` + `python_pkg/focus_policy` — must come after `hosts`:
    `deploy_phases.sh:73` executes hosts' `generate_hosts_file.sh`.
-5. `digital_wellbeing` **last** — pacman wrapper, `chattr +i`, and the 12
+3. `digital_wellbeing` **last** — pacman wrapper, `chattr +i`, the 12
    hardcoded orchestrator paths in `check_and_enable_services.sh:61-74` /
-   `setup_periodic_system.sh:20-23`.
-6. Step D: flatten the 207 remaining entry-script violations
+   `setup_periodic_system.sh:20-23`, and now `heavy_job_lock.sh`, which moved
+   in with it. It also owns `test_shutdown_timer_monitor.sh`, the pair test
+   left behind here.
+4. Step D: flatten the 207 remaining entry-script violations
    (`single_use/**` is ~130 of them). Deduplicate the two Nextcloud
    implementations first — ~2,780 lines for one capability.
-7. Step E: wire both gates, close the `boot-repair` hole (756 lines, escapes
+5. Step E: wire both gates, close the `boot-repair` hole (756 lines, escapes
    the 250-line cap because `is_source_file()` needs a dot in the filename),
    prune `docs/superpowers/` churn.
 
@@ -74,5 +70,21 @@ Depth, tests and pre-commit verified green at every commit; nothing used
 - **pre-commit's patch restore can silently revert an edit** made before the
   commit — the `app_icons` change had to be applied twice. Re-grep after
   committing.
-- `shell-tests.yml` discovers suites by glob, so a removal shrinks CI coverage
-  with a green build. Record the suite count before and after.
+- `shell-tests.yml` discovers _some_ suites by glob and names others in an
+  explicit list. A removal breaks the list (CI fails on the missing file) and
+  silently shrinks the glob. Check both.
+- **Never let a test fall back to `/usr/local/bin`.** The installed copy can be
+  older than source — `shutdown-timer-monitor.sh` is, on this machine — so the
+  test compares an installer template against a binary it never generated. It
+  hung. Prefer a sibling checkout and SKIP when absent.
+- Extractions keep surfacing pre-existing bugs. `update_android_hosts.sh`
+  pointed `GUARDIAN_MODULE_DIR` at a sibling that never existed. Fix them
+  rather than carrying them forward, and guard at the single funnel.
+
+## Unrelated: syncyomi-guard is red
+
+Failing since 00:00 on 2026-08-23, ~17h before this session — nothing to do
+with the restructure. It is working as designed: the library collapsed from
+2185 manga / 68902 chapters to 8 / 895. See the `syncyomi-restore-silent-partial`
+memory; do NOT checkpoint the WAL before recovering. Newest snapshot in
+`~/syncyomi/snapshots/` is 2026-08-15.