Public: anyone can read this; the crew can change it.
A lead who says "not until spring" can be put away until a date: follow-ups stop, and that morning a check-in draft waits on the desk #77
Reviewed pull #80 at its head: ticked An open lead's page has Come back on… with a date (in the agent's time zone from the profile, at least tomorrow, at most 365 days out). Saving it skips every unsent follow-up and the lead leaves "Needs you" and "In follow-up"; the desk row carries a Back on <date> badge and shows under All.; On that date at 8:00 in the agent's time zone, one check-in draft ("you said to get back in touch around now…", by the lead's channel, signed with the profile, never mentioning the private note) waits on the desk in "Needs you" for approval. Nothing is sent without approval.; Bring back now clears the date; a lead writing back ("They wrote back") also clears it.; Same through PATCH /leads/{id} ({"back_on":"YYYY-MM-DD"}, null clears), an MCP tool, and a key on the terminal's lead screen; asked through permit as a lead update; a bad date is a 422 naming the field.; The Activity page says "Put away until <date>" / "Brought back".; One sample lead is already put away, so the meeting sees the badge.; Tests: date validation at the boundary, follow-ups skipped, draft appears on the date and not before, wrote-back clears it. README tour/How it works gains a short paragraph..
Intent: an agent hears "call me in March" every week; today the only choices are keep pestering them or mark them lost (not ready). Let the agent park the lead until a date instead.
Done looks like:
Files: src/leads.ts, src/drafts.ts, src/routes.ts, src/pages/lead.ts, src/pages/desk.ts, src/mcp.ts, src/terminal.ts, src/openapi.ts, src/sample.ts, README.md, tests.
Risks: overlaps the follow-up plan code that #69 (lost after last follow-up) also reads; keep the put-away state a lead field, not a new status, so lost/qualified logic is untouched. Clock and time zone come from src/clock.ts and the profile, never the server's zone.