officerdev/platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mark 5.6 resolved, and stop three docs claiming a channel that has no publisher

Browse Source 
The todo entry said the file-viewer registration was dead; tracing it confirmed that and turned up the
reason it looked alive — the ephemeral file viewer is a different mounting path entirely. Recorded, with
what was checked in the database before deleting anything.

CLAUDE.md, navigation-audit.md and workspace-panels.md all listed FILE_VIEWER_CHANNEL among the
legitimate refresh/signal channels. It never had a publisher, and no longer exists.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
pastilhas
2026-08-07 11:07:36 +00:00
co-authored by Claude Opus 5
parent 9fcc9c278a
commit 30fcab2bd3
4 changed files with 31 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/workspace-panels.md
+4 -3
View File
@@ -131,9 +131,10 @@ library location, so no album is linkable), `soulseek:section` and `soulseek:use
workspace has no URL), `chat:selected-session`, `monitor:scope`. Two are view toggles where a channel is
genuinely fine (`music:favorites`, `music:lyrics`).
Three are wired to nobody: `preview:refresh` and `chat:active-session` have publishers and no
subscribers; `file-viewer:<panelId>` has a subscriber and no publisher, which is why the registry-mounted
`officerdev/file-viewer` app renders "No file selected" forever.
Two are wired to nobody: `preview:refresh` and `chat:active-session` have publishers and no subscribers.
A third, `file-viewer:<panelId>`, had a subscriber and no publisher — it is gone, along with the
`officerdev/file-viewer` registration it fed, which would have rendered "No file selected" forever. The
file viewer users actually see is an *ephemeral* panel from `useFileViewerPanels` and reads the URL.
Four channel names are **bare string literals with no shared constant**, repeated across up to four
files. A typo does not error — you silently get a fresh channel stuck on its initial value. And because