T

istosandClaude Fable 5 e1b9a8f662 Let kanban columns flex down to a token floor on small laptops

Five fixed 296px columns overflowed 13" MacBooks (~1556px footprint vs
~1440 viewport), clipping the Done column. Columns now grow/shrink from
a zero basis, capped at --col (pixel-identical at >=1556px) and floored
at a new --col-min token (240px: five columns + gaps + board padding =
1276px, fitting 1280px viewports). Below the floor the existing
overflow-x:auto fallback is unchanged.

Sessions, Focus and the header are already fluid at 1280px — checked,
nothing to fix there.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-30 07:31:41 +02:00

.claude

Task board state, MultiEdit launch fix, and repo hygiene

2026-07-30 07:02:25 +02:00

manager

Let kanban columns flex down to a token floor on small laptops

2026-07-30 07:31:41 +02:00

plans

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

reference

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

tasks

Merge branch 'task/03-focus-checks-come-from-the-project'

2026-07-30 07:21:18 +02:00

tests

Let kanban columns flex down to a token floor on small laptops

2026-07-30 07:31:41 +02:00

.gitignore

Task board state, MultiEdit launch fix, and repo hygiene

2026-07-30 07:02:25 +02:00

CLAUDE.md

Describe the definition of done generically in the distributed docs

2026-07-30 07:15:59 +02:00

install.py

Address PR review: symlink-safe removal, guard-gated stamp, hermetic tests

2026-07-30 07:22:33 +02:00

README.md

Ship a pristine board on install: first boot clears distribution cards

2026-07-30 07:09:46 +02:00

start.sh

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

stop.sh

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

update.sh

Bench 1: the task board extracted as its own distribution

2026-07-29 17:57:07 +02:00

README.md

Bench

A live kanban for coding-agent work: task files in stage directories are the only source of truth; a stdlib-only board narrates everything that happens to them — agents working in git worktrees, PRs opening on review, CI and Copilot state on the cards, drives of the app from a task's own branch, and an archive that is never a delete.

Install into a repo

git clone <this repo> .task-manager && rm -rf .task-manager/.git
./.task-manager/start.sh        # wires the project (idempotent) and serves

The first start.sh clears the distribution's own cards from tasks/, plans/ and reference/ (printing each removal), so a fresh install starts with an empty board.

Commit .task-manager/ into the host repo — core is vendored on purpose, so clones work offline and updates show up in the host's own diffs.

Update

# in manager/local/.env:  BENCH_SOURCE=<this repo's git url>
./.task-manager/update.sh              # latest
BENCH_REF=v1 ./.task-manager/update.sh # a specific release tag

Updates replace manager/core/ and the top-level scripts wholesale and touch nothing else — tasks, plans, reference, and everything under manager/local/ (your driver, commands, prompt overrides, settings, state) survive every update. Then python3 .task-manager/install.py and restart the board.

The three-layer law

Core knows about tasks, worktrees, PRs and events. It knows nothing about any particular app (drivers do: local/driver/start), agent vendor (adapters do: core/adapters/), or project (local/ does). Full docs in CLAUDE.md; the adapter contract in manager/core/adapters/README.md.