lane-statuslisted

# Lane status Answers "is there anything for me to do on this project today?" without anyone having to ask the other developer. Everything comes from files git already carries between machines. ## How to run it **1. Run the status script.** It is the only source — never parse the register by hand, and never guess who owns what: ```bash bash scripts/lane-status.sh ``` The lane comes from `SPEC_OWNER` in `.claude/settings.local.json` (gitignored, per machine). If it is unset on a multi-lane project the output says so, and setting it is the first fix — without a lane there is no way to tell "my row" from "theirs". On a single-lane project the report still works and simply has no other lane to describe. **2. If the output says upstream is ahead: pull first, then answer.** An answer computed on a stale base can hand out a row the other lane already claimed. `git pull --rebase`, re-run. **3. Read the diagnosis before recommending a row.** A register row is a pointer; the reasoning is in `specs/INDEX.pending.md` under the same heading. A row that looks small on the register line can be three pieces of work. **4. Answer in this order**, as briefly as it can be said: 1. **What to start now** — a recommendation, not a menu. If the developer has a row assigned, that is the answer, full stop. If they have none: the top unclaimed row whose dependencies are all ticked, with one sentence on why that one. 2. **What is waiting on somebody else** — the other lane's row, and whic