/todos: a kanban board over the todo/ tree, owner-only
The filesystem is the database: GET reads the tree through the same module the index generator now imports, PATCH splices frontmatter (status, priority, due, order) and never touches a body byte, and every write regenerates TODO.md. Columns open/doing/blocked/done, native drag between them, selection and theme filter in the URL. Registry entry 'todos' (kind admin, 22 entries, docs:check green), isSuperAdmin double-gate on the router. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
---
|
||||
id: tooling/a-kanban-board-over-todo-synchronised-both
|
||||
title: "A Kanban board over `todo/`, synchronised both ways"
|
||||
title: 'A Kanban board over `todo/`, synchronised both ways'
|
||||
theme: tooling
|
||||
status: open
|
||||
status: done
|
||||
created: 2026-08-21
|
||||
date_source: stated
|
||||
order: 1
|
||||
@@ -26,3 +26,24 @@ Open, and deliberately not decided here: which columns (`status` today holds onl
|
||||
`doing` and `blocked` are new values whenever the board wants them); whether it is an Officer screen, a
|
||||
panel app or a plugin; and how it notices a change made on disk while the board is open — a watcher, a
|
||||
poll, or a refresh button, which is the cheapest thing that works.
|
||||
|
||||
---
|
||||
|
||||
**Built 2026-08-24 — `/todos`, a core screen, deliberately not a plugin.** The tree lives in the
|
||||
platform's own repo, and dev tooling about the platform's backlog has nothing to gain from being
|
||||
installable elsewhere.
|
||||
|
||||
What v1 is: `GET /api/todos` reads the tree (shared module `api/todos/todo-tree.ts`, which
|
||||
`scripts/todo-index.ts` now also imports, so the board and the generated index cannot disagree);
|
||||
`PATCH /api/todos/item` splices frontmatter — status, priority, due, order — and never touches a body
|
||||
byte, with tests asserting exactly that. Columns are open / doing / blocked / done; drag a card to move
|
||||
it, and every write regenerates `TODO.md`. Selection and theme filter are `?selected=` / `?theme=`, so
|
||||
cards are real links and a filtered board is an addressable page. Owner-only: `todos` is `kind: 'admin'`
|
||||
in the registry (now 22 entries, docs:check green) with an `isSuperAdmin` gate on the router as the
|
||||
second lock.
|
||||
|
||||
Answers to this item's open questions: the columns are those four statuses, new values are one edit to
|
||||
`TODO_STATUSES`; it is a screen, not a plugin; change detection is a 30s refetch — the cheapest thing
|
||||
that works, as predicted. Not done: creating or editing items from the board (the body is the owner's
|
||||
half, written in an editor), and drag does not reorder within a column — `order` is PATCHable but no
|
||||
gesture drives it yet.
|
||||
|
||||
Reference in New Issue
Block a user