LocalDevEnv
Getting a new contributor (or a fresh worktree) running quickly — env setup, seed data, docs.
Why we need this / what value this brings
A slow or fragile local setup is a tax every contributor (or every fresh worktree) pays repeatedly.
When to use this
Whenever setup friction shows up more than once — that's the signal it's worth documenting/automating.
How to use or implement this
Keep a single documented path to a working local environment (already partially captured in LocalzTodos/NOTES.md), and automate what can be scripted.
Research questions
- This is literally documented per-round in LocalzTodos/NOTES.md — worth distilling into a canonical setup doc here eventually.
Empty folder — drop notes, links, and findings here as you research.