v0.6.6

Release Notes - v0.6.6

Summary

• AgentPlane v0.6.6 is a patch release focused on the branch PR one-commit contract, PR artifact freshness, and safer upgrade dirty-state handling.
• PR artifacts no longer depend on a tracked self-referential branch head field for normal freshness checks.
• Release and upgrade validation now treat task-local artifact churn more carefully, reducing false stale-state failures.
• No breaking migration is required for existing v0.6 users.

Added

• Added stronger test coverage for PR artifact refresh behavior after task commits so one-commit branch PR flows stay reproducible (f40f689).
• Added task evidence for the branch PR artifact one-commit contract fix so the release can be traced back to the active release task (fed468e).
• Added generated website social images for recently added docs pages so docs-site social image checks remain complete for this patch.

Improved

• Improved PR artifact freshness by comparing rendered PR review state through diffstat digests instead of a tracked live branch head_sha field (9e58fd3).
• Improved branch PR integrate behavior so task-local artifacts and registry updates do not make product-code PR artifacts stale (9e58fd3).
• Improved forward-compatible PR metadata parsing by preserving diffstat freshness fields across unknown future status variants (9e58fd3).
• Improved protected-base integrate routing so GitHub PR handoff remains the primary result instead of being masked by local artifact freshness checks (9e58fd3).
• Improved the branch PR artifact one-commit contract by keeping task README, PR review files, and registry updates out of normal review-diff freshness decisions (77531d8).
• Improved upgrade dirty-state handling by parsing dirty paths more safely before deciding whether an upgrade can proceed (dfa59d5).
• Improved upgrade safety test coverage to match the stricter dirty-state parser behavior (03b4cfa).
• Improved PR metadata recording for the upgrade dirty-state task so the branch PR evidence remains auditable (eca24e3).
• Refreshed task artifacts after upgrade dirty-state changes so task-local evidence matches the reviewed implementation (2c4ff63).
• Hardened the upgrade dirty-state implementation so open upgrade work handles path edge cases more predictably (87c0699).
• Refreshed task artifacts after lint-fix verification for the upgrade and blueprint artifact cleanup path (0970049).
• Recorded verification evidence after closing upgrade and blueprint artifact issues so release audit trails include the accepted check state (dddcfeb).

Fixed

• Fixed PR artifact stale failures caused by self-referential tracked artifacts changing the branch head after the artifacts were rendered (9e58fd3).
• Fixed legacy upgrade dirty-state handling tests so older dirty worktree shapes remain covered by the current safety rules (2c588af).
• Fixed open upgrade and blueprint artifact issues that previously left release validation with stale or incomplete artifact state (8add6e4).
• Fixed targeted lint failures in the upgrade and blueprint artifact cleanup path (b40ef29).
• Fixed upgrade and blueprint artifact issue handling so the remaining checks can pass under the release route (d191d33).

Upgrade Notes

• No breaking changes are expected for v0.6 users.
• Upgrade by installing the v0.6.6 packages after npm publication completes.
• Existing tracked PR metadata that still contains head_sha remains tolerated by compatibility paths, but new normal PR artifact freshness should rely on computed live branch state and diffstat digests.
• Teams using branch PR workflows should rerun ap pr update only when the product/code diff changes, not merely because task-local artifacts were refreshed.

Verification

• Release plan generated from v0.6.5 with agentplane release plan --patch, targeting v0.6.6.
• Local release validation passed with bun run release:prepublish, including format, schemas, policy routing, release parity, docs freshness, build, package tarball policy, local tarball install smoke, all 65 release-ci-base chunks, workflow coverage, significant coverage, and release-critical tests.
• Docs site validation passed with regenerated social images and bun run docs:site:check.
• Final publication requires branch PR candidate merge, hosted Publish to npm, npm package readback, remote tag readback, and GitHub Release readback.