Files
platform/todo/files-app/the-acts-that-clear-the-overlay-have-no-owner.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

707 B

id, title, theme, status, created, date_source, order
id title theme status created date_source order
files-app/the-acts-that-clear-the-overlay-have-no-owner The acts that clear the overlay have no owner, only the list does files-app open 2026-08-20 assumed 2

The acts that clear the overlay have no owner, only the list does. VIEWER_PARAMS and withoutViewerParams live in files-route.ts and are shared. But every site still decides FOR ITSELF whether to call them, which is precisely how the breadcrumb shipped wrong an hour after the rule was written. Three bugs in a row came from this. A single navigateToFolder() that every caller must go through — rather than a helper they may remember — is the fix if a fourth appears.