Building with mini, Part 3/9: Capturing ideas with todo

In Part 2, pycalc went through its planning interview. A side product you may have noticed: the interview generated ideas we deliberately rejected — Claude itself deferred the ** power operator with the note that right-associativity is "the ideal v2 exercise". Reading from stdin dropped out too. The non-goals now say "Do not add * or % in this version."*

But a non-goal is a rule, not a plan. It says what must not happen now — it doesn't say what should happen someday. So where does "someday" go?

I know all three bad options from my own practice: your head (you forget), an IDEAS.md file growing forever (exactly the documentation pile mini stands against), or creating it as a phase right away (and the project state silts up with a future that may never come).

mini todo is the fourth option: a backlog for things that aren't phases yet.

Zero tokens