memory: the design arc mid-flight — blur landed, UI pending, and what not to do
A fresh session needs four things that are not derivable from the code: that design-dev is shipping in two merges with blur first, that the booth-blur storage and CLI are already landed so only the control is missing, that the Desk exposes 84 images across 22 booths on the first page (which is WHY blur got re-prioritised), and that the operator explicitly declined to have the sindra-nude-* booths blurred on his behalf. Also records that the hover ruling only looked like it reversed design-dev's argument — he resolved it with @media (hover: hover) rather than anyone being overruled, so it should not be re-raised as a conflict.
This commit is contained in:
@@ -59,6 +59,31 @@ _As of 2026-09-22:_
|
||||
⚠ **Calibration for the next round: his bar is "did anything change when I
|
||||
opened it".** He said the Booth "kind of looks the same" about our own U7
|
||||
navigation work, before ever seeing the design round.
|
||||
- 🔶 **THE DESIGN ARC IS MID-FLIGHT AND design-dev IS BUILDING IN TWO MERGES.**
|
||||
First: **Reveal all + the booth-blur control** (re-sequenced to first because
|
||||
the operator said per-booth blur became important). Second: the Desk row
|
||||
revisions + the theme toggle. Each gets its own bug-hunt; he pings at each
|
||||
handover and **we merge and restart**.
|
||||
- ✅ **BOOTH-LEVEL BLUR: STORAGE AND CLI ARE LANDED; ONLY THE UI IS PENDING.**
|
||||
Marker `<booth>/.blurbooth`, `POST /b/<name>/blurbooth`, and
|
||||
**`booth blur <name>` with NO files fogs the whole booth** (naming files is
|
||||
still per-item). COMPOSES with `.blurred`, never overrides. All 17 handles can
|
||||
self-blur at post time, which is the durable fix.
|
||||
- ⚠ **THE DESK EXPOSES 84 IMAGES ACROSS 22 BOOTHS on the page he opens first**
|
||||
(measured 2026-09-23). The pre-redesign index showed ONE cover per booth, so
|
||||
four-up multiplied exposure by four and **nothing posted before the redesign
|
||||
opted into it.** That is why blur got re-prioritised.
|
||||
⚠ **The operator declined to blur the `sindra-nude-*` booths for now** — he
|
||||
will do it himself once design-dev's control lands. **Do not blur them on his
|
||||
behalf.**
|
||||
- ✅ **RULINGS 2026-09-23:** `×` (wipe) **hides** with the other Desk controls
|
||||
on hover; the theme toggle **reaches** `.bk-ask` chrome inside verbatim pages;
|
||||
global unblur is **reading A** (per-booth, tab-scoped, nothing persisted);
|
||||
**no `1.0.0` yet.**
|
||||
⚠ The hover ruling looked like it reversed design-dev's "nothing hides behind
|
||||
hover" argument; he resolved it WITHOUT an overrule via
|
||||
`@media (hover: hover)` — hidden-until-hover only where hover exists, own line
|
||||
on touch. Do not re-raise it as a conflict.
|
||||
- ✅ **ALL FOUR FLOW RULINGS ARE IN — A+B, compare THIS ARC, plain voice, no
|
||||
emblem** (operator via Miranda D-0016, 2026-09-23 08:07). Every one took
|
||||
design-dev's recommendation; no notes attached. **booth-dev is the SOLE RELAY
|
||||
|
||||
Reference in New Issue
Block a user