project-next-stepslisted

# NEXT_STEPS.md, the open-work tracker `docs/NEXT_STEPS.md` is the committed tracker for open work only: TODOs, follow-ups, known issues, and product ideas not yet committed to. It is the ONLY sanctioned place for such notes. Never put them in code comments. Gamache's `NoTodosCheck` enforces that side. ## What does not belong An entry that asks nothing of anyone does not belong here. A decision already taken, a finding checked and dismissed, a do-not-fix note, or a runbook for a known-quiet failure is an observation. Observations go in the relevant skill or in `docs/`, where the person who needs them already reads. In the tracker, every future scan re-reads and re-dismisses them, and they bury the work that waits. The test is whether the entry has an addressee. "Someone should do X" is an entry. "We decided X and here is why" is a skill or a doc. A `Status:` that will never change means you write the wrong kind of note. Move it, then cross-reference it from wherever the work would otherwise be rediscovered. ## The repository is public Every entry is published the moment you push it. Write no secrets, no customer names, and no venting about people. A later deletion does not unpublish an entry, because it stays in git history. ## The file is branch content Git tracks the file, so two consequences follow. - Edit it in whatever worktree you work in, like any other file. - Parallel branches that both append land in the same region and conflict. Resolve the conflict by k