pastilhasandClaude Fable 5
6071ded175
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>
1.1 KiB
id, title, theme, status, created, date_source, order
| id | title | theme | status | created | date_source | order |
|---|---|---|---|---|---|---|
| workspaces-panels/a-deep-read-of-the-whole-framework-to | A deep read of the whole framework, to understand it and then improve it | workspaces-panels | open | 2026-08-20 | assumed | 1 |
A deep read of the whole framework, to understand it and then improve it. Low priority and
explicitly not pain-driven — it works, and it works well. But it was built fast and then added to,
repeatedly, and nobody has since sat down and read the whole thing at once.
Three questions to answer rather than assume: can the query strings come out of the flow; is there
a better shape for panel-to-panel communication than the current channel/URL split; and what does
the layout tree cost that a simpler one would not.
Fold the existing panel items into this — the silent key/appType mismatch, the destructive
layout migration on a renamed key, and docs/workspace-panel-todo.md. They are symptoms of the
same unexamined design, and fixing them one at a time is how it stays unexamined.
Also a teaching exercise: the owner wants to understand it end to end, which is a reason to do it
properly rather than quickly.