v0.9.1

A small patch with one real fix.

The fix — your approved capabilities are no longer lost during setup

When you add cladding to a project that already has code, part of setup is approving the project's list of capabilities (its high-level features). That approved list now gets saved to your spec exactly as you approved it.

Before this release it was quietly discarded — replaced by your README's section headings, or left empty if the project had no README. So if you set cladding up on an existing codebase and your capabilities came out wrong or empty, this is why, and it's fixed.

Also in 0.9.1

• Better handling of non-JavaScript projects. Formatting problems now list every affected file (not just the first), Python test suites run once per check instead of twice (faster), and the style check recognizes more comment styles.
• New gentle reminders — they never block a check. cladding now nudges you when code is written with no matching spec, when your checks aren't set to run automatically, and when setup should steer you to writing your first spec instead of jumping straight into code.
• Plainer wording in more messages.