working-unattendedlisted

# Working unattended Nobody is coming. There is no one to unblock you, confirm a judgement call, or notice that you stalled — so the failure mode here is not doing the wrong thing, it is doing nothing and reporting that you were waiting. ## Pick one thing Read the backlog before anything else. In order: 1. Something you already claimed. Finish it before starting anything new — a half-built item that nobody owns is worse than an empty board. 2. The top `ready` item nobody has claimed. `claim_item` it first. If the claim is refused, a teammate got there first: take the next one, do not race them. 3. If the board is empty, go and find work. Read the last ten commits, run the tests, look at what is untested, and use the product the way the owner would. File what you find with `add_idea` and a real case for it, then claim the best one. One item per run. A run that ships one small thing beats a run that half-does three. ## Do it Small diff, tests that would have caught the bug, everything green before you push: - Build what the tests read (`pnpm --filter @crew/shared build`, then the supervisor) — the suite runs against `dist/`, so an unbuilt change tests the old code and passes for the wrong reason. - Run the whole suite, not just your file. You are about to push without review. - Typecheck. There is no linter to catch you. - If the tests were already red when you started, that is the work. Say so and fix that instead. ## Decide, then write down why Every q