docs(13-11): require content to actually render, not merely be fetchable

13-06 delivered the content pipeline and unit-tested it, but nothing in the
live UI invokes it, and 13-11 as written only added an equally-uncalled
sibling. No plan in the phase triggers the fetch from a UI event. Without this
AIUI-03 ships green-tested and visibly broken — empty grids. Wiring belongs
here, where useArchy.ts and ChatPage.vue's render tree are already in scope.

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

.planning/phases/13-aiui-functional-conversational-node-control-and-content-surf/13-11-PLAN.md

@@ -14,6 +14,7 @@ requirements: [AIUI-03]
 
 must_haves:
   truths:
+    - "Content actually APPEARS in the running app without anyone typing a magic phrase — the fetch is triggered by a live UI event (panel/tab open or equivalent in `ChatPage.vue`'s render tree), not merely callable. GAP FOUND 2026-08-03 by the orchestrator after 13-06 completed: 13-06 built `requestArchyContent` + `content:request`/`content:push` + `setArchyContent` and unit-tested all of it, but NOTHING in the live UI calls it, and this plan as originally written only adds `requestArchyLibrary` as a SIBLING — also uncalled. Grep across every phase-13 plan found no onMounted/tab-open/panel-open trigger anywhere. Left alone, AIUI-03 ships with complete, green-tested machinery and empty grids: every unit test passes and the feature visibly does not work. Wire both `requestArchyContent` and `requestArchyLibrary` to a real trigger here."
     - "AIUI's SongGrid shows the node's real music library — albums, artists and tracks from the index, not a MIME-filtered folder listing (D-13, D-12)"
     - "An .m4a, .aac, .opus or .wma file shared from the cloud view gets a real audio MIME type, routes to the global bottom-bar player, and auto-files to Music instead of Documents"
     - "Audio opens in the global bottom-bar player and never in the lightbox — the rule enforced across five existing call sites is not broken by the new path"