Files
platform/todo/plugin-infrastructure/a-plugin-cannot-claim-a-websocket-provider.md
T
pastilhasandClaude Fable 5 6071ded175 todo: one file per item, grouped by theme, with a generated index
TODO.md had reached 1050 lines and 72 open items across 28 sections, read mostly
on a phone. It is now a directory: todo/<theme>/<item>.md, one card per file, with
frontmatter carrying id, status, created date and order, and the prose body copied
across verbatim. TODO.md becomes a generated index (bun run todo:index).

Dates: where an item's prose stated one it is used; otherwise its old section's;
otherwise 2026-08-20, floored at the day before the split rather than invented.
date_source records which.

Shaped for a two-way Kanban board, filed as todo/tooling — a card is a file, id is
the identity, frontmatter is the machine's half and the body is the owner's.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-21 05:42:39 +00:00

631 B

id, title, theme, status, created, date_source, order
id title theme status created date_source order
plugin-infrastructure/a-plugin-cannot-claim-a-websocket-provider A plugin cannot claim a WebSocket provider plugin-infrastructure open 2026-08-21 stated 1

A plugin cannot claim a WebSocket provider. pluginPermissions in mount.ts sets api and routes and never ws, and server.tsx's handler map is a literal — so a plugin's socket has no door. The desktop plugin ships one that cannot be mounted (plugins/desktop/BLOCKERS.md §2), and it will not be the last: agreed 2026-08-21 that this is real infrastructure to build, not a per-plugin workaround.