T1.2 - log the two backlog entries the commit message referenced

BL-001 updated: its 1440px half was resolved as a side effect of the F2 fix,
not by intent. Left open, scoped to the creator at 390px, so T7.1 still checks
it.

BL-003 added: user-menu links are 16px tap targets. T1.2 made them reachable;
it did not make them comfortable. Deferred to T2.2, which replaces the markup.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/waves/backlog.md

@@ -67,6 +67,12 @@ deliberately deferred.
   rebuilds its layout regardless — fixing it in wave 1 would be thrown away.
 - **Suggested wave or follow-up:** verify it is gone at `T7.1`; if it survives the rebuild,
   it needs its own item in the next revision.
+- **Update, T1.2:** the 1440px half of this is **resolved as a side effect**, not by intent.
+  The unbreakable `#wp-usermenu` run that `T1.2` fixed was the cause of four of the five
+  overflows recorded in wave 0 — launcher, SOP wizard and field view at 390px, and the
+  creator at 1440px. Capture now reports overflow on 1 of 14 shots instead of 5. What
+  remains is the creator at **390px** (485px of content), which is its own layout rather
+  than the shared chrome. Left open so `T7.1` still checks it.
 
 ### BL-002 — `outline: none` appears three times in the wizard sheet, not once
 
@@ -79,3 +85,17 @@ deliberately deferred.
 - **Why not now:** it is in scope for `T3.4`, not a separate item — recorded so the task
   fixes all three rather than the one the review cited.
 - **Suggested wave or follow-up:** fold into `T3.4`.
+
+### BL-003 — User-menu links are 16px tap targets
+
+- **Found during:** T1.2
+- **Where:** `html/auth-guard.js:186-191` (`buildUserMenu`'s `link()`)
+- **What:** every link in the app bar's user menu — including `Sign out` — renders 16px
+  tall, from `font:400 13px/1.2`. `T1.2` made them all reachable at 390px, but reachable is
+  not the same as comfortably tappable on the gloved-hands surface. Well under the usual
+  24–44px guidance.
+- **Why not now:** `T1.2` is explicitly triage and `T2.2` replaces this markup with the
+  drawer, which has its own tap targets. Enlarging them here would change the 1440px layout
+  the task must leave byte-identical, and would be thrown away in wave 2.
+- **Suggested wave or follow-up:** `T2.2` should ship the drawer with adequate targets;
+  `C1`'s audit at `T9.5` confirms it app-wide.