file-a-tasklisted

# File a task in the tracker You are working inside cowork-deck. If you notice a problem along the way that is **not part** of the current task, do not widen your scope and do not let it drop. File a card and carry on with what you were doing. ## When to use this - You found a bug in code you are not touching. - You saw a TODO or a hack worth fixing separately. - You thought of an improvement nobody asked you for. ## When NOT to use this - The problem **is** part of your task — just fix it. - You are not sure it is a problem — check first, then file. - A card already exists: look at `ls "$COWORK_TASKS_DIR"` first. ## How ```bash "$COWORK_TASK_BIN" new --kind bug --title "A short title" <<'EOF' What is wrong, how to reproduce it, where to look. EOF ``` `--kind` must be one of the kinds this project's `board.json` configures — the default board has `bug`, `task` and `idea`, but that is one project's configuration, not a fixed list. An unconfigured `--kind` is rejected. The body is read from stdin and is optional, but a card without a repro is close to useless. If the environment variables are missing, no tracker is configured for this workspace — say so to the human rather than guessing at a path. ## Moving a card through its steps The steps a card can be in are configured **per project** in that project's `board.json` — they are not fixed by the tool. One project might have `backlog / todo / doing / shipped`, another just `open / done`. Never assume a step name; rea