Lessons learned

A short retrospective from Trazo's first published release, v0.1.0.

• Keep one source of truth. A single home for framework rules makes updates easier to review and keeps each install consistent.
• Plan around a release goal. Milestones show what belongs in a release and what remains before it ships.
• Keep each project's own memory. Plans and decisions should stay with the project, even when its framework is upgraded.
• Check what people install. Verify the published version, not just the copy on a developer's machine.
• Separate building from reviewing. A fresh reviewer can spot gaps the builder may miss; leave the review where the team can find it.

These are retrospective notes, not a process for automatically collecting lessons. Durable guidance belongs in the project's rules or decision records.