SpecPi 0.11.2

SpecPi 0.11.2 keeps the task, its checks, and the final review connected. Your improvement records stay local, and you still decide which changes to make.

This is the first npm release of the 0.11 update. Two release-workflow issues were caught before publication and are fixed here. The earlier 0.11.0 and 0.11.1 source tags remain available for reference.

What’s new

• Optional task cards. Use /task set to capture requirements, expected files, acceptance checks, and rollback steps. The specification view and completion review use the same card, and /task handoff prepares a packet you can share for review.
• A clearer record of each improvement. Verification receipts show which checks ran against which source. Changing tasks or switching session branches no longer lets an old selection or unfinished review carry over.
• Feedback after the work is done. /wishlist outcome lets you record whether a retired improvement helped, needs another look, or should be revisited. You can correct that assessment later without losing its history.
• A cleaner introduction to SpecPi. The README, homepage, and wiki have clearer installation guidance, better layouts on smaller screens, and a diagram showing how SpecPi fits into Pi.

There are also a few practical fixes: your chosen theme survives updates, scope checks handle aliased project directories correctly on Windows and macOS, and the test harness keeps its temporary state out of shared directories.

Task cards are optional, so your existing workflow still works. If you selected a harness improvement before upgrading, select it again through /harness-improvement before verifying it. That gives the selection a fresh source baseline.

Upgrade

npm install --global specpi@0.11.2
specpi update
specpi doctor

Then run /reload in Pi. For a first installation, run specpi plan and specpi install instead of specpi update.

The release passed 183 local tests and the GitHub checks on Linux, Windows, and macOS.

Full changelog · Changes since 0.10.0