What you'll do: run the coffee-shop demo on a fresh machine following only docs/operator-runbook.md, and file a friction log — every step that was unclear, missing, or broken.
Where: the runbook + README.md quick start; your output is a checklist-style comment or PR on the runbook.
Expected behavior: a numbered list of friction points with OS, step, expected vs. actual.
How to test: each reported item is reproducible from a clean checkout with Docker + Node 24.
Mentor: @DBarr3 — no Go knowledge needed; this is one of the most valuable first contributions.
What you'll do: run the coffee-shop demo on a fresh machine following only
docs/operator-runbook.md, and file a friction log — every step that was unclear, missing, or broken.Where: the runbook +
README.mdquick start; your output is a checklist-style comment or PR on the runbook.Expected behavior: a numbered list of friction points with OS, step, expected vs. actual.
How to test: each reported item is reproducible from a clean checkout with Docker + Node 24.
Mentor: @DBarr3 — no Go knowledge needed; this is one of the most valuable first contributions.