release: v1.1.2 — pi 0.79.3 → 0.79.4

Patch release per AGENTS.md versioning scheme (pi version bump + smaller
fixes). Cut Unreleased → v1.1.2 (2026-06-15): pi 0.79.3→0.79.4
(CI-auto-resolved), the mempalace-toolkit SHA-resolution build fix,
recreate-sanity-check.sh maintainer tooling, and the AGENTS/README docs.
Bumped the README sanity-check version example to 0.79.4.

CHANGELOG.md

@@ -13,6 +13,11 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
 
 ## Unreleased
 
+## v1.1.2 — 2026-06-15
+
+Patch release: pi `0.79.3` → `0.79.4` (auto-resolved at build), plus the
+build-plumbing fix, maintainer tooling, and docs accumulated since v1.1.1.
+
 ### Changed
 
 - **`mempalace-toolkit` is now CI-resolved to a commit SHA**, closing a
@@ -65,6 +70,11 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
   is still 3.4.0 (== our pin), so the workaround stays. Removal trigger is now
   a PyPI release > 3.4.0 that actually strips the root-level anyOf.
 
+- Document the post-recreate sanity check: AGENTS.md release-day checklist
+  (step 3) now runs `scripts/recreate-sanity-check.sh` inside the recreated
+  container, and README gains a "Post-recreate sanity check" subsection
+  alongside the build-time smoke-test note.
+
 ---
 
 ## v1.1.1 — 2026-06-13

README.md

@@ -551,7 +551,7 @@ persisted volumes survived, and pi runtime wiring is intact:
 
 ```bash
 ./scripts/recreate-sanity-check.sh                       # auto-detects variant
-./scripts/recreate-sanity-check.sh --expected-version 0.79.3   # assert pi version
+./scripts/recreate-sanity-check.sh --expected-version 0.79.4   # assert pi version
 ```
 
 If `cli_utils` is on your PATH, the `pi-devbox-sanity` wrapper runs the same