bp-tasklisted

# Working a BP task A task is done when it is merged, documented, cleaned up after, and nobody was asked. Every stage below moves the task on the board. Skipping a stage is not finishing early; it is not finishing. Board comments, commits, PR text and docs are in English. ## 0. Pick - A task named in the request wins. Otherwise pick from `todo`, never from `planned`: assigned to the board's own account first, then highest priority, then oldest. - Before anything else: `git ls-remote --heads origin | grep -i <n>`, `gh pr list --state all --search BP-<n>`, and grep `list_tasks` titles for the same subject. Somebody may be on it, or it may already be fixed. Details in `references/git-github.md`. - `change_task_status` to `in_progress`, `update_task` assignee the board's own account (`references/board.md` says how to read it), `add_comment` with the approach. Every size starts at once; no plan waits for approval. - Own worktree outside the repo, branch `bp-<n>/<slug>`, own Mongo container. Recipe in `references/git-github.md`. ## 1. Build - Commit each part as it works. - Something noticed on the way: if it belongs to the task, fix it now; if it is separate, `create_task` in `todo` with file:line, after grepping `list_tasks` titles for a duplicate. - Tests: an e2e in `e2e/` listed in `e2e/groups.ts`, and a unit test. Both. Each new test goes red with the fix removed, for the stated reason: the red check in `references/e2e.md`. - `npx tsc --noEmit`, `npm test`, `rm -rf .next