chore: release main (#99)

🤖 I have created a release *beep* *boop*
---


<details><summary>pi-blueprint: 0.2.0</summary>

##
[0.2.0](pi-blueprint-v0.1.0...pi-blueprint-v0.2.0)
(2026-04-11)


### Features

* Add pi-blueprint multi-session planning extension
([#98](#98))
([bbda0d6](bbda0d6))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Author: MattDevy

.release-please-manifest.json

@@ -4,5 +4,5 @@
   "packages/pi-compass": "0.2.0",
   "packages/pi-simplify": "0.2.0",
   "packages/pi-code-review": "0.2.0",
-  "packages/pi-blueprint": "0.1.0"
+  "packages/pi-blueprint": "0.2.0"
 }

package-lock.json

@@ -0,0 +1,8 @@
+# Changelog
+
+## [0.2.0](https://github.com/MattDevy/pi-extensions/compare/pi-blueprint-v0.1.0...pi-blueprint-v0.2.0) (2026-04-11)
+
+
+### Features
+
+* Add pi-blueprint multi-session planning extension ([#98](https://github.com/MattDevy/pi-extensions/issues/98)) ([bbda0d6](https://github.com/MattDevy/pi-extensions/commit/bbda0d6e958917a3479c8ac78ea444a707458db2))

packages/pi-blueprint/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "pi-blueprint",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "A Pi extension that turns high-level objectives into phased, multi-session construction plans with dependency tracking and verification gates.",
   "type": "module",
   "license": "MIT",