Navigator: per-Mind Media row after Desk #96
Loading…
Reference in a new issue
No description provided.
Delete branch "void/mind-media-row"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-ups chat-mind-20261111T134059606Z-t76 and chat-s6448-6451 (same ask).
Mediaright afterDesk, whether or not the room exists or is joined.#<mind>-files:<server>is resolved with getRoomIdForAlias (react-query, 60s). The carried-id shape (media[<mind>]) is provisional: stewardships-carry-room-ids has not defined it yet, so this reader is the consumer's guess and changes with that follow-up. Note an invitee cannot read the root Space state, so for most users the alias path is the live one.Media · not set upand links nowhere; other lookup failure readsMedia · unavailable. No fake data.Limits: a Mind with no project rooms has no foldout, so no Media row; a Mind outside the roster gets none. Tests: pure lookup/state tests with a fake client, plus row markup tests (consumer side).
🤖 Generated with Claude Code