worklane was one-shot commands only, so reading the board meant running ls again and again and nothing ever showed the four statuses side by side, which is the one view a kanban flow is for. Four columns, a card per ticket carrying the priority mark, short id, title, owner and due. Arrows or hjkl to move, enter for the detail view, q to quit. Read only: moving a card by keypress is a follow-up, kept out until the watch and render loop were solid. Modelled on frig throughout, same crates and same shape: event poll on a 250ms timeout so the tick runs when nobody is typing, a panic hook that leaves the alternate screen before the backtrace, and the terminal restored on the error path as well as on quit. A bare worklane opens it, as a bare frig does, so Cli::command is now an Option. The watch looks at files, not directories. A directory's mtime only moves on create and rename, so a ticket edited in place would be missed; the digest hashes every ticket and comment file's path, length and mtime. Comment files are in it because a comment added elsewhere has to reach the detail view. It guards the rescan rather than the draw, since ratatui diffs its buffer but reading the tree every frame would not be free. notify is deliberately not a dependency, and the reason is on the ticket. Two orderings are deliberate. The worklane directory is looked for before the terminal, so running outside one gives the usual message rather than a complaint about the tty, and both errors stay testable without a pty. And a missing tty is refused by name, since raw mode on a pipe fails with a bare "No such device or address" that explains nothing. The palette is now a Color enum rather than a string, so the escape the CLI writes and the ratatui colour the board draws come from one definition and a colour missing from either is a compile error. That retires the test which existed only to catch a name with no entry, the failure that once left magenta undefined. Cards come from collect_ticket_items, so there is no second parser; TicketItem gained the path the detail view opens. content_trim and format_comments_with take the colour decision, because ratatui draws spans and would print an escape as literal bytes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2.6 KiB
2.6 KiB
Worklane
Worklane is a local Kanban flow for agentic software development.
Commands
| Command | Description |
|---|---|
worklane or worklane tui |
Opens the board: four status columns, redrawn when the tree changes. Read only. Arrows or hjkl to move, enter for detail, q to quit |
worklane init |
Creates .worklane/ with backlog, committed, reviewing, done directories |
worklane add |
Creates a ticket in backlog with --title, --description, --acceptance, --plan, --tags, --due, --owner, --priority flags |
worklane ls [status] |
Lists tickets, sorted by priority then title. Optional positional status, and --priority <1-5> |
worklane show <id> |
Shows ticket by UUID prefix (4+ chars), title substring, or filename substring |
worklane mv <id> --status <target> [-f] |
Moves ticket between statuses. Default: forward only, one stage at a time. -f bypasses both restrictions |
worklane set <ticket> |
Replaces fields with --title, --description, --acceptance, --plan, --tags, --due, --priority. At least one required. Changing the title renames the file, keeping the UUID |
worklane append <ticket> |
Adds to a section with --description, --acceptance, --plan. At least one required. The description gains a paragraph; list items go on the end, steps numbered on from the last |
worklane check <ticket> [criterion] |
Ticks one acceptance criterion, by number as shown by show or by a substring. Prompts with the numbered list if omitted, or errors with it when there is no terminal |
worklane uncheck <ticket> [criterion] |
Unticks one acceptance criterion, addressed the same way |
worklane comment <ticket> <body> |
Adds a comment to a ticket by UUID or title |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | An error, such as no matching ticket or an ambiguous search |
| 2 | A usage mistake, such as an unknown flag |
| 141 | Output was piped to a reader that stopped early, for example worklane ls | head -3 |
141 is 128 + 13, the shell's way of reporting death by SIGPIPE. Worklane restores
the default signal disposition so a truncated pipe is quiet, the way head and
sort are, rather than printing a panic. A script using set -o pipefail will see
141 for a case that is not a failure, so guard for it there.
Whether a truncated pipe reports 141 or 0 depends on the size of the output, not on the command. A pipe holds 64 KiB, so a listing that fits lands in the buffer whole and the writer never learns the reader left, giving 0. Only output past that gets far enough to be cut off. Either way nothing is printed to stderr.