Ansho ReiandClaude Opus 5 ce32b42ae4 (dbf7b61) Guard the overlay's relation colours, and bump to 0.15.0
The mechanism arrived with 6ce2c47, as this ticket said it would: the block is
laid out once as cells, the id carries the red the guideline gives a uuid, and
the board turns the same cells into spans. So the id is red in the overlay
without anything here asking the terminal for a decision, and the three
criteria about what is drawn were true the moment ece201e landed.

What was left is the test the ticket was really about. The naive version of
this, passing true to the body renderers, puts escapes in the paragraph and
draws them as literal bytes, which is 6d327df, and the tests that pin that
assert on content_trim rather than on what detail_of builds.

the_relation_id_is_red_in_the_overlay_and_no_escape_reached_the_body asserts
the id span is red, that something on the row is coloured at all, and that the
body holds no escape byte. The middle one is the pair the Color and Output rule
demands: without it a version that dropped every colour to stay safe would
satisfy the absence. The one character version now fails this test and two
others, checked by making the change and running the suite.

a_missing_target_still_reads_as_missing_in_the_overlay is the same question
asked of a gap: _missing_ in grey, the id still red, and the mark ? in grey
rather than the status orange, so a target the board no longer holds cannot be
dressed up as one it does.

And the decision the ticket asked for, in AGENTS.md: the relations block is the
only coloured part of the overlay body, on purpose. The block earned it by
being where a reader compares several references at once, and by arriving as
rows rather than prose. The rest of the body is e4d0bb7, which is a larger
change than it looks, since every run content_parts paints has to become a cell
while show's output stays byte for byte what it prints today. One coloured
section reads as a decision; two would read as a bug.

The minor is 6ce2c47's, taken here because the pair is one body of work: show
now prints a status mark before each relation id.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-22 15:23:55 +02:00
2026-05-14 20:41:40 +02:00

Worklane

Worklane is a local Kanban flow for agentic software development.

Commands

Command Description
worklane or worklane tui [path...] Opens the board: four status columns, redrawn when the tree changes. Read only. Opens on backlog, committed and reviewing; d shows or hides done, whose count stays in the footer either way. Arrows or hjkl to move, enter for detail, pgup/pgdn to scroll an open ticket, / to jump to the first ticket whose id or title matches, y to copy the selected ticket's short id to the clipboard, q to quit. Each path opens the first .worklane at or above it, the working directory by default. Several paths are monitored together, as a tab per project plus an all tab that merges them, with tab and shift+tab between them
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. --due takes YYYY-MM-DD and refuses anything else at parse time
worklane ls [status] Lists tickets, sorted by priority then title. Optional positional status, and --priority <1-5>, --tag <tag> and --campaign <campaign>, which compose in any combination. --tag matches a whole value of the comma-separated Tags field, case sensitively, so --tag bug does not list a ticket tagged bugfix or one tagged Bug
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 relate <ticket> Records an edge to another ticket with --blocked-by, --regression-of or --relates-to, each repeatable. At least one required. Only the ticket named is written; show derives the other end by scanning. mv refuses to move a ticket blocked by one that is not done, unless -f
worklane chown <user> <ticket> Sets the Owner field, the only command that writes it. Free text, checked against nothing. User first and ticket second, after Unix chown
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
worklane install-skill [skill] Writes the embedded agent skills to ~/.claude/skills/<skill>/SKILL.md, which Claude Code and opencode both read. Three ship: worklane teaches the CLI, worklane-review reviews a finished ticket against the code that claims to close it, worklane-plan grooms the board as a whole, its priorities, due dates, tags and campaigns. Every document unless one is named. Leaves a modified copy alone unless --force; --print writes one to stdout instead and needs the name

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.

S
Description
No description provided
Readme
3.7 MiB
Languages
Rust 97.8%
TypeScript 1.9%
Makefile 0.3%