Agentplane 0.3.1 is a recovery release in the most literal sense. It exists because the 0.3.0 npm path was already burned, and pretending otherwise would have made the release story worse, not better.
Why 0.3.1 had to happen
The problem was not subtle. 0.3.0 had already been burned in npm history, so trying to ram the same version through again would have been the wrong fix.
0.3.1 takes the practical path instead:
- move the release line forward to the next valid version,
- repair the publish and release notes flow,
- clean up the public docs and website surfaces around that release.
That is what release discipline looks like in real life. Not just writing better code, but refusing to fake a clean publish path when the registry has already said no.
The release pipeline was recovered, not papered over
The best thing about 0.3.1 is that it stays honest.
Instead of trying to reuse 0.3.0, the release process moved to 0.3.1 and documented the situation clearly. That is a better model for teams because it preserves traceability:
- which version was attempted,
- which one actually shipped,
- which recovery steps were required to get back to a clean release path.
This sounds procedural until you are the person debugging upgrades later. Clean release metadata saves a lot of guesswork.
Task-doc updates became less awkward
0.3.1 also cleaned up a smaller but real annoyance: batched task-doc updates.
The written guidance now explicitly allows agents to update task-doc sections in one grouped turn before approval starts. The sequencing rule still stays strict where it matters: approval and start-ready must still happen in order.
So the guidance got easier to use without turning the lifecycle into mush.
The website got quieter again
Part of 0.3.1 was also admitting that the website had drifted in a bad direction.
The release tightened the docs shell, improved spacing and left-aligned reading flow, simplified the blog index, and then intentionally restored the homepage to a quieter placeholder-style landing.
I think that was the right decision. This product does not need a loud marketing front page if the real value is operational clarity.
Practical outcome
For users, 0.3.1 means three things:
- the
0.3.xline is publishable again on a clean version path, - task-doc guidance is clearer for normal use,
- the docs and blog surfaces are less noisy and easier to scan.
It is not a big release. It is a useful one. It removes confusion in exactly the places where confusion tends to multiply.
Upgrade note
There are no breaking API or workflow-mode changes in 0.3.1.
If your repository consumes framework policy templates, it is still worth syncing or upgrading them so the clarified batched task-doc guidance lands locally as well.
The formal source record remains the release notes at /docs/releases/v0.3.1.