commit 9a0daa6ce88dd3f26bc29ea48740b50ff768c19c
parent 484f066b2bb9947d61a122f19570fa11689327bb
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Thu, 17 Sep 2026 20:38:11 -0400
plans: storage locations — S0 merged, S4 in flight
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Diffstat:
1 file changed, 1 insertion(+), 0 deletions(-)
diff --git a/plans/storage-locations.md b/plans/storage-locations.md
@@ -191,3 +191,4 @@ shas, gate outputs, divergences.
- 2026-09-17 — plan committed on `main`.
- 2026-09-17 — S1 (`storage/locations-s1`, `578867f`→`68d082d`) and S2 (`storage/locations-s2`, `c078e1f`→`79c0071`) reviewed and merged as `d146c51`. Real-host probe matched the plan (available + uuid + fstab warning; mounted-elsewhere with the automount candidate). Follow-up recorded: rename/delete channel actions still check the registry alone (`channels/actions.ts` `renameChannelAction`) — `channelMediaBusyReason` is a drop-in there.
- 2026-09-17 — S3 (`storage/locations-s3`, `8824f5b`→`aed94d9`) reviewed and fast-forwarded onto main: `/storage`, controller + views, `repoint-storage-location` job, nav at twelve, boot pass, fake findmnt/udisksctl, `storage-locations.spec.ts`; common 1314/1314, e2e 6/6. Declined: a `spec` on the re-point job record (it is the Retry switch and the kind is not replayable).
+- 2026-09-17 — S0 (`storage/locations-s0`, `c13c5a8`→`d4ebf1d`) merged as `093e436`: the row dim is per cell, the Tier cell hosts the popover; `channel-priority.spec.ts` proves it with two adjacent paused rows and an `elementFromPoint` owner check (passes with the fix, fails without). Main now holds S0–S3; S4 in flight.
