docs: record the late operator asks and the deploy state of tonight's fixes

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

.planning/MEDIA-AND-INDEEHUB-SCOPE.md

@@ -96,3 +96,32 @@ would address B-2, the app-auth half of C, and Phase C's zaps at once. Media ide
 distribution over Nostr (NIP-94/NIP-71 style events, Blossom for blobs) is the obvious
 frame for "all the media types" and should be evaluated against the current
 `content.*` RPC model before more sources are bolted onto it.
+
+## F. Added by operator 2026-08-06, late — not yet started
+
+- **Cmd/Ctrl+K search → AIUI.** Choosing "search with AIUI" from the command palette must
+  open the EXPANDED chat with the typed query actually sent to AIUI and answered — today it
+  does not carry the words through. Wire the palette's query into the chat open path.
+- **Mock data types.** Add more mock content types for dev/preview, and make the whole
+  content path performant (the grid, the fan-out, the panel).
+- **Node questions — full coverage.** Every "ask the node about itself" question class should
+  be answerable: apps, system, network, wallet, bitcoin, files, media, search, ai-local,
+  notes are the declared `AIContextCategory` set in contextBroker's `fetchAndSanitize`.
+  Audit each for real coverage rather than a stub.
+- **AIUI seed/history as design input.** The operator asked that the solution be researched
+  from AIUI's own seed/history and the project's Nostr-first ethos, not invented fresh.
+
+## G. Status of the fixes made 2026-08-06
+
+Shipped + deployed to archi-dev-box: content-grid sequence guard (`aac81503`), owned/peer
+scopes wired (`11b9cb50`), per-scope permission logging (`7c23505d`), warm-up app status
+(`c65ee03a`), scheme-following app frames (`f09ff102`), per-node CA + Settings flow
+(`aab74127`), app-port TLS with HTTP on the same socket (`7515166a`), key perms for the
+daemon (`1dfd9e72`).
+
+Shipped, NOT yet deployed: the credential-less allowlist that fixes the IndeeHub
+regression — release build was in flight at end of session. Deploy is:
+`install -m 755 core/target/release/archipelago /usr/local/bin/archipelago` then
+`systemctl restart archipelago` (containers are unaffected — verified, they live in
+/user.slice, not the service cgroup), then re-test `curl -o /dev/null -w "%{http_code}"
+http://<node>:7778/manifest.json` — expect 200, not 401.