docs(todos): capture two operator-reported AIUI issues

Mobile load speed and the 'how to use AIUI' brief not opening. Both noted with
the caveat that the deployed AIUI bundle is stale (pre-D-14), so they must be
reproduced against a fresh in-repo build before being chased.

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

.planning/todos/pending/2026-08-04-aiui-mobile-loads-slowly.md

@@ -0,0 +1,30 @@
+---
+created: 2026-08-04T03:20:00.000Z
+title: AIUI loads slowly on mobile
+area: ui
+severity: major
+resolves_phase: 13
+files:
+  - aiui/packages/app/src/pages/ChatPage.vue
+  - neode-ui/src/views/Chat.vue
+---
+
+## Problem
+
+Operator-reported 2026-08-04: AIUI "loads a bit slow" on mobile.
+
+Not yet root-caused. Note before investigating: the currently-deployed AIUI bundle
+predates the D-14 work (node bundle dated Aug 3 12:37, no `chatExpanded` string in
+it), so any measurement taken against a node today is measuring a stale build. Re-measure
+against a freshly built in-repo AIUI before chasing a cause — the fix for the D-14
+symptoms may move this number too.
+
+Phase 02 established the tooling for this class of work: `neode-ui/e2e/perf/` holds a
+re-runnable KeepAlive/remount probe, and 02-11 found that the real culprit for several
+"slow" surfaces was leaked background pollers armed in `onMounted` and never disarmed,
+not compute-bound render cost. Check that pattern first.
+
+## Acceptance
+
+Mobile AIUI first paint and interaction-ready measured on a real device against a
+current build, with a before/after number rather than an impression.

.planning/todos/pending/2026-08-04-how-to-use-aiui-brief-does-not-open.md

@@ -0,0 +1,22 @@
+---
+created: 2026-08-04T03:20:00.000Z
+title: "\"How to use AIUI\" does not open the brief when tabbed to"
+area: ui
+severity: major
+resolves_phase: 13
+files:
+  - aiui/packages/app/src/pages/ChatPage.vue
+---
+
+## Problem
+
+Operator-reported 2026-08-04: the "how to use AIUI" entry does not open its brief when
+tabbed to. Reported alongside the D-14 start-state symptoms, so confirm first whether this
+is also an artefact of the stale deployed bundle (node AIUI is from Aug 3 12:37 and predates
+the D-14 embed work) rather than a live code defect.
+
+Reproduce against a freshly built in-repo AIUI before investigating.
+
+## Acceptance
+
+Tabbing to the "how to use AIUI" entry opens its brief.