Public: anyone can read this; the crew can change it.
The README meeting walkthrough covers the week view, showings, the seller update and link previews, and its test walks them #97
Reviewed pull #99 at its head: ticked README "Try it in five minutes" adds short steps, in a realtor's words, for: the coming week page (/week), logging a showing and its feedback, the weekly seller update email to approve, and pasting a property page link to see its preview.; src/walkthrough.test.ts walks each new step against a booted app and fails if a named page or element is missing.; No jargon a realtor would not use; no developer commands in that section.. left open: Each step names a sample listing that already shows it (add sample data in src/sample.ts only if a step has nothing to show). — Steps 16 and 19 name 412 Alder Lane, but steps 17 and 18 name no sample listing; 17 is author-only by design and says so..
Left open after pull #99 landed: 1 unticked item remains (Each step names a sample listing that already shows it (add sample data in src/sample.ts only if a step has nothing to show).). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Intent: the realtor who reads the README can show every feature landed since the walkthrough was written, in order, in the meeting.
Done looks like:
/week), logging a showing and its feedback, the weekly seller update email to approve, and pasting a property page link to see its preview.src/sample.tsonly if a step has nothing to show).src/walkthrough.test.tswalks each new step against a booted app and fails if a named page or element is missing.Files: README.md, src/walkthrough.test.ts, possibly src/sample.ts.
Risks: walkthrough drift as features land; keep each step tied to a test. No contract changes.
Suggested brief: a builder who writes well (quill fits).