@webappwiz/arbor 0.0.29 → 0.0.31

package/README.md

@@ -105,7 +105,8 @@ configures none.
 
 A merge onto trunk ends by recommending what to do next: the open todo highest
 on the list that came up in the task that landed, since its context is
-freshest, or failing that the open todo highest on the list, plus any todo older than `todoStalenessMs` (30 days) offered for
+freshest, then one sharing a tag with the todos the task settled, the same
+area of work, or failing that the open todo highest on the list, plus any todo older than `todoStalenessMs` (30 days) offered for
 removal instead. The todos the task
 took up, with `--todo` or `todo take`, leave the list, since that work is now
 done; release one first to keep what is left of it.
@@ -148,7 +149,7 @@ down the listing; a record whose worktree vanished shows as `orphaned`.
 
 `--files` adds, under each task, every path it has changed (committed or
 not) and every path its `ARBOR.md` plans under `## Files` that it has not
-touched yet. This is the overlap check an agent runs before starting: its own
+touched yet. This is the overlap check an agent runs once it has planned: its own
 list of files against everyone else's.
 
 ```
@@ -229,24 +230,34 @@ the only thing that remembers a task landed at all. The last 1000 are kept
 The todos and the tasks in a browser, on `http://localhost:4269`, reloading
 themselves as anything changes. Built for a phone first.
 
+One page, tasks above the todos.
+
 Todos are cards in list order: drag one to reorder the list (a short press
 on a phone, or Space on its grip and the arrow keys), or tap it to reword,
 attach files to, or remove. A card shows its subject, two lines of its
-detail rendered as markdown, and badges for its files and staleness, and a green edge with
+detail rendered as markdown, and badges for its files, tags and staleness, and a green edge with
 "Taken by <task>" once a task has taken it; its
 `#7` copies `[ARBOR TODO #7]`, which the agent skill reads as that todo, for
 pasting into a chat. An opened todo shows its detail rendered, with Write and
 Preview to switch between the markdown and how it reads. Typing `@` in a todo offers the files and
 directories in the main tree, tracked or new but not ignored, and writes the
 one picked as `@path/from/root`; picking a directory keeps the list open on
-what is inside.
+what is inside. An opened todo's tags are edited there too, comma separated,
+and its `#7` copies the same reference as the card's.
+
+Tasks lists every task with a bar for its progress through its plan, counted
+from the checkboxes under `## Done` and `## Next` in its `ARBOR.md`, flagging
+only an escalated or broken status; tapping one opens its details and whole
+plan in a dialog.
 
-Tasks lists every task with its progress through its plan, flagging only an
-escalated or broken status; tapping one opens its details and whole plan in a dialog.
+A row of tags over the todos filters them, the way a mail client filters by
+label: All, then every tag a todo has. Tapping one there, or on a card, shows
+only its todos. Dragging a card while filtered moves it to the place in the
+whole list of the card it is dropped on, so the todos hidden between them
+shift around it.
 
-On a phone the tabs sit along the bottom, in reach of a thumb; on anything
-wider they run down a sidebar. If the server stops answering, the header says
-it is offline, since what the page shows may be stale.
+If the server stops answering, the header says it is offline, since what the
+page shows may be stale.
 
 Todo writes are the same functions as `arbor todo add`, `update` and
 `remove`. Questions are answered in the agent's chat, not here. Merging,
@@ -333,7 +344,7 @@ imports, a signature changed on one side and its callers on the other) and
 unreliable when both sides restructured the same logic, because then there is no
 correct merge, only a decision.
 
-### `arbor todo add <subject> [text] [--position <n>] [--file <path>]`, `arbor todo list [--json]`, `arbor todo show <id> [--json]`, `arbor todo update <id> [text] [--subject <subject>] [--position <n>] [--file <path>] [--remove-file <name>]`, `arbor todo take <id...>`, `arbor todo release <id...>`, `arbor todo remove <id>`
+### `arbor todo add <subject> [text] [--position <n>] [--file <path>] [--tag <tag>]`, `arbor todo list [--json] [--open] [--tag <tag>]`, `arbor todo show <id> [--json]`, `arbor todo update <id> [text] [--subject <subject>] [--position <n>] [--file <path>] [--remove-file <name>] [--tag <tag>] [--remove-tag <tag>]`, `arbor todo tags [--json]`, `arbor todo take <id...>`, `arbor todo release <id...>`, `arbor todo remove <id>`
 
 Work deferred for later. When something outside the task comes up (a bug next
 door, a follow-up the reviewer asked for, a question that turns out to be its
@@ -360,6 +371,8 @@ run from a worktree, adds them to the task already under way, all or none.
 A task can hold any number. `release` puts them back on the list, from a
 worktree only its own task's: a task landing with one half done rewords it to
 what is left with `update`, then releases it, so the merge leaves it open.
+`list --open` shows only those no task holds, which is what an agent
+looking for work to pick up wants.
 `update` rewords one, its detail as the argument and its subject with
 `--subject`, and keeps its number; `remove` drops one done some other way or
 no longer wanted.
@@ -369,6 +382,13 @@ no longer wanted.
 one, named by path or by its stored file name (`todo show` lists them). They
 go when the todo does.
 
+`--tag uploads,merge` tags a todo with the areas or goals it belongs to; a
+todo can have several tags and a tag many todos. A tag is a lowercase word,
+or a few joined by hyphens, and anything else is refused, so one area never
+splits into two spellings. `update --tag` adds tags, `--remove-tag` drops them,
+`list --tag` shows only one tag's todos, and `todo tags` lists every tag in
+use with how many todos have it.
+
 ### `arbor retry <task>`
 
 Grants an escalated task another `mergeRetryCount` merge attempts and puts it

package/dev.d.ts

@@ -1,6 +1,6 @@
 import { type AsyncResource } from "webappwiz/disposable";
 import type { Logger } from "webappwiz/log";
-import { type Fs, type PortProvider } from "webappwiz/system";
+import { type Fs, type PortProvider, type Ps } from "webappwiz/system";
 import type { Assets } from "./dev/assets.js";
 import type { Journal } from "./journal.js";
 import type { Todos } from "./todo.js";
@@ -31,9 +31,10 @@ export interface DevServer extends AsyncResource {
  * todos. Anything that moves a task (merge, remove, claim) stays in the CLI,
  * so a page that should not have been reachable can at worst change a todo.
  */
-export declare function dev({ service, fs, journal, todos, log, assets, }: {
+export declare function dev({ service, fs, ps, journal, todos, log, assets, }: {
     service: WorktreeService;
     fs: Fs;
+    ps: Ps;
     journal: Journal;
     todos: Todos;
     log: Logger;