90b313952bccb76d8c0d0cd3398cd16d938ccf5f
The detail view renders with colour off, because ratatui draws styled spans and an escape sequence inside a paragraph is not one. `detail_of` asks for that with `content_trim(&content, false)`. Two paths ignored the argument and asked the terminal instead. `colorize_ordered` took no colour parameter at all and called `color_text`, which is `paint(.., should_use_colors())`, and `content_trim` routes every Implementation Plan line through it. In the TUI stdout is a terminal, so each numbered step arrived as ESC[36m, the number, ESC[0m, then the text: exactly the gap between the number and the step text where the reported artifact showed. `colorize_line` did the same for a hand-written line inside a Metadata section, and `colorize_bold` honoured its `enabled` flag on the early return and then asked `should_use_colors()` again for the bold run, which made the flag a lie in half the function. `colorize_ordered` now takes the decision and is private, `content_trim` being its only caller. `colorize_line` is deleted rather than given the argument: it was a `pub` alias for `colorize_bold` with one caller, and asking the terminal was the only thing it added, so `render_metadata_table` calls `colorize_bold` with the decision it already holds. Why this shipped, and the reason for the shape of the tests. The guard was an assert that the detail view holds no escape byte, and it could not fail: a test binary has no tty, so `should_use_colors()` was false and the leaking branch was never taken. An absence is now asserted alongside a presence, `content_trim(.., false)` carries no escape and `content_trim(.., true)` still colours, which pins the flag as the only thing that decides. A third test scans this file for `color_text` callers and fails on a new one; it also corrected the assumption this commit started from, since the remaining caller is `ambiguous` and not `display_ticket_items`. The visible symptom is a terminal artifact that no test here can see, since TestBackend applies cell updates and parses no escapes. What is proven is that the escapes are gone, and that the CLI still paints its plan numbers cyan in a pty, which is the condition the leak needed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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. 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, 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 |
worklane install-skill |
Writes the embedded agent skill to ~/.claude/skills/worklane/SKILL.md, which Claude Code and opencode both read. Leaves a modified copy alone unless --force; --print writes it to stdout instead |
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.
Languages
Rust
97.8%
TypeScript
1.9%
Makefile
0.3%