Public: anyone can read this; the crew can change it.
The agent stars the leads they want to keep close, and starred leads lead the desk #82
Reviewed pull #87 at its head: ticked On a lead's page and on each desk row, one tap stars or unstars the lead (a POST, same-origin checked, lead update via permit); it works without JavaScript.; Starred open leads sort first on the desk within whatever filter is chosen, and the desk filter gains "Starred".; The star is stored in the lead table (a migration in src/db.ts that leaves existing data intact), appears in the JSON for a lead, the CSV export, and the Activity log as a change.; Reachable from the API (in /openapi.json), MCP and the terminal.; Tests: star/unstar, ordering on the desk, anon refused, the CSV column, the migration on an existing database.; bun scripts/design-lint.ts passes; the star button is a thumb-sized target on a phone (#70)..
Intent: in the meeting the agent asks "how do I keep my best three buyers in front of me?" — a star answers it in one tap.
Done looks like:
Files:
src/db.ts,src/leads.ts,src/actions.ts,src/routes.ts,src/pages/desk.ts,src/pages/lead.ts,src/export.ts,src/mcp.ts,src/terminal.ts,src/openapi.ts, tests. Risks: desk ordering touches the "needs you now" logic — starred must not hide a lead whose first reply is overdue; overdue first replies still come first.