v0.15.2 post-publication: record digests, flip state, sweep pointers

.ai/handoff/CURRENT_STATE.md

@@ -2,10 +2,10 @@
 
 ## Snapshot
 
-- `v0.15.1` is the latest published release. It is available from PyPI and
+- `v0.15.2` is the latest published release. It is available from PyPI and
   its record is immutable. `v0.13.1` is the prior published release, and
   GitHub; exact artifact digests are in
-  `docs/release/v0.15.1-checksums.txt`. `v0.13.1` shipped the Phase 4
+  `docs/release/v0.15.2-checksums.txt`. `v0.13.1` shipped the Phase 4
   core-roadmap work with the exact release headline **Replicated
   benchmark, faster SQLite at scale, reference integrations.** The
   `v0.13.0` tag exists but was never published (superseded; see the
@@ -83,10 +83,10 @@ authoritative description; Phase 3 does not rewrite that history.
 
 ## Release Boundary
 
-`v0.15.1` is tagged, published, and immutable. Its authoritative records are:
+`v0.15.2` is tagged, published, and immutable. Its authoritative records are:
 
-- `docs/release/v0.15.1-release-notes.md`
-- `docs/release/v0.15.1-checksums.txt`
+- `docs/release/v0.15.2-release-notes.md`
+- `docs/release/v0.15.2-checksums.txt`
 
 `v0.13.1` remains published and immutable; its records are
 `docs/release/v0.13.1-release-notes.md` and `docs/release/v0.13.1-checksums.txt`.
@@ -143,17 +143,13 @@ the `v0.14.0` release notes.
   update graph; it does not undo accepted project state or erase shared source
   evidence, upstream systems, exports, backups, or external logs.
 
-## What `v0.15.1` Shipped
+## What `v0.15.2` Shipped
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
 
 The `v0.15.0` tag exists but was never published. The commit it points at
 carried a release-gate step that could not run on a CI runner, so the gate
 could never pass from that tag, and repository rules correctly refuse both
 deletion and update of stable tags. No GitHub Release or PyPI artifact was
 ever created for it.
-
-## What `v0.15.2` Targets
-
-`v0.15.2` is the current release candidate. It is not published.

ARCHITECTURE.md

@@ -3,11 +3,11 @@
 ## Scope Boundary
 
 
-- **Published boundary:** `v0.15.1` is the latest published release,
+- **Published boundary:** `v0.15.2` is the latest published release,
   carrying the Phase 4 core-roadmap work (replicated benchmark evidence,
   SQLite vector scale, reference integrations, trace-only count
   diagnostics); artifact digests are in
-  `docs/release/v0.15.1-checksums.txt`.
+  `docs/release/v0.15.2-checksums.txt`.
 - **Prior published:** `v0.12.0` is the prior published release. It is
   tagged and immutable, passed the exact-SHA CI, semantic, and
   repository-control gates, and is published on PyPI with Trusted Publishing
@@ -223,7 +223,7 @@ usage justifies a separately reviewed boundary.
 
 ## Current Architectural Posture
 
-- `v0.15.1` is the latest published release and reconciles runtime and product
+- `v0.15.2` is the latest published release and reconciles runtime and product
   identity around the agent interface, retrieval/memory quality, and a
   real-host-proven single-tenant deployment contract.
 - Phase 3 reduces `main.py` to app assembly and shared middleware,
@@ -247,7 +247,5 @@ usage justifies a separately reviewed boundary.
   `docs/handoff/`; it does not constrain legitimate future production trees or
   approve them automatically.
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
-
-`v0.15.2` is the current release candidate. It is not published.

CURRENT_STATE.md

@@ -2,10 +2,10 @@
 
 ## Snapshot
 
-- `v0.15.1` is the latest published release. It is available from PyPI and
+- `v0.15.2` is the latest published release. It is available from PyPI and
   its record is immutable. `v0.13.1` is the prior published release, and
   GitHub; exact artifact digests are in
-  `docs/release/v0.15.1-checksums.txt`. `v0.13.1` shipped the Phase 4
+  `docs/release/v0.15.2-checksums.txt`. `v0.13.1` shipped the Phase 4
   core-roadmap work with the exact release headline **Replicated
   benchmark, faster SQLite at scale, reference integrations.** The
   `v0.13.0` tag exists but was never published (superseded; see the
@@ -83,10 +83,10 @@ authoritative description; Phase 3 does not rewrite that history.
 
 ## Release Boundary
 
-`v0.15.1` is tagged, published, and immutable. Its authoritative records are:
+`v0.15.2` is tagged, published, and immutable. Its authoritative records are:
 
-- `docs/release/v0.15.1-release-notes.md`
-- `docs/release/v0.15.1-checksums.txt`
+- `docs/release/v0.15.2-release-notes.md`
+- `docs/release/v0.15.2-checksums.txt`
 
 `v0.13.1` remains published and immutable; its records are
 `docs/release/v0.13.1-release-notes.md` and `docs/release/v0.13.1-checksums.txt`.
@@ -143,17 +143,13 @@ the `v0.14.0` release notes.
   update graph; it does not undo accepted project state or erase shared source
   evidence, upstream systems, exports, backups, or external logs.
 
-## What `v0.15.1` Shipped
+## What `v0.15.2` Shipped
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
 
 The `v0.15.0` tag exists but was never published. The commit it points at
 carried a release-gate step that could not run on a CI runner, so the gate
 could never pass from that tag, and repository rules correctly refuse both
 deletion and update of stable tags. No GitHub Release or PyPI artifact was
 ever created for it.
-
-## What `v0.15.2` Targets
-
-`v0.15.2` is the current release candidate. It is not published.

PRODUCT_BRIEF.md

@@ -15,13 +15,13 @@ Agent developers — people building or operating AI agents who need durable, ex
 - Local-first: your data stays on your machine; models and embeddings are pluggable via OpenAI-compatible endpoints.
 
 ## Current Posture
-- `v0.15.1` is the latest published release and immutable baseline (Phase 5
+- `v0.15.2` is the latest published release and immutable baseline (Phase 5
   enterprise track: real-host single-tenant deployment contract and
   least-privilege operations). `v0.13.1` is the prior published release. It
   carries the Phase 4 core-roadmap work (replicated benchmark, SQLite
   scale, reference integrations). Its PyPI wheel and source distribution
   have Trusted Publishing provenance, with exact digests in
-  `docs/release/v0.15.1-checksums.txt`.
+  `docs/release/v0.15.2-checksums.txt`.
 - `v0.11.0` shipped the Phase 1 periphery cut. It removes the Telegram,
   hosted/control-plane, public chat/response, chief-of-staff, and model-pack
   periphery so the default runtime matches the product described here. The
@@ -63,7 +63,5 @@ Agent developers — people building or operating AI agents who need durable, ex
 - The MCP surface is small enough to learn in one sitting.
 - Every claim in the docs matches shipped behavior.
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
-
-`v0.15.2` is the current release candidate. It is not published.

README.md

@@ -141,7 +141,7 @@ search degrades to full-text only and says so explicitly in the retrieval trace.
 
 ## Status
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and release-note baseline (the `v0.13.0` tag was never published;
 superseded). Its tag, release record, and published artifacts
 are immutable.
@@ -183,7 +183,7 @@ What that means in practice:
 - [v0.11.0 release notes](https://github.com/samrusani/AliceBot/blob/main/docs/release/v0.11.0-release-notes.md)
 - [v0.11.1 release notes](https://github.com/samrusani/AliceBot/blob/main/docs/release/v0.11.1-release-notes.md)
 - [v0.12.0 release notes](https://github.com/samrusani/AliceBot/blob/main/docs/release/v0.12.0-release-notes.md)
-- [v0.15.1 release notes](https://github.com/samrusani/AliceBot/blob/main/docs/release/v0.15.1-release-notes.md)
+- [v0.15.2 release notes](https://github.com/samrusani/AliceBot/blob/main/docs/release/v0.15.2-release-notes.md)
 - [Release procedure](https://github.com/samrusani/AliceBot/blob/main/RELEASING.md)
 - [Architecture](https://github.com/samrusani/AliceBot/blob/main/ARCHITECTURE.md)
 - [Roadmap](https://github.com/samrusani/AliceBot/blob/main/ROADMAP.md)
@@ -201,7 +201,5 @@ If you discover a security issue, follow the process in [SECURITY.md](https://gi
 
 MIT — see [LICENSE](https://github.com/samrusani/AliceBot/blob/main/LICENSE).
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
-
-`v0.15.2` is the current release candidate. It is not published.

RELEASING.md

@@ -2,7 +2,7 @@
 
 
 
-`v0.15.1` is the latest published release and remains the checksum/install
+`v0.15.2` is the latest published release and remains the checksum/install
 baseline.
 Preparing candidate documents does not authorize a tag, PyPI upload, or GitHub
 Release.
@@ -405,7 +405,5 @@ the tag and must not have claimed publication early.
 Verify checksum files on Linux with `sha256sum -c SHA256SUMS` and on stock
 macOS with `shasum -a 256 -c SHA256SUMS`.
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
-
-`v0.15.2` is the current release candidate. It is not published.

ROADMAP.md

@@ -2,9 +2,9 @@
 
 ## Baseline (Not Roadmap Work)
 
-- `v0.15.1` is the latest published release. Its immutable release record is
-  `docs/release/v0.15.1-release-notes.md`, with artifact digests in
-  `docs/release/v0.15.1-checksums.txt`. (The `v0.13.0` tag was never
+- `v0.15.2` is the latest published release. Its immutable release record is
+  `docs/release/v0.15.2-release-notes.md`, with artifact digests in
+  `docs/release/v0.15.2-checksums.txt`. (The `v0.13.0` tag was never
   published; superseded.)
 - `v0.11.0` shipped the Phase 1 periphery cut; `v0.11.1` shipped the Phase 2
   debt sweep. Their tags, release records, and published artifacts are not
@@ -85,7 +85,5 @@ restore, recorded security disposition) shipped in Phases 4 and 5.
 - OCR or transcription execution; Alice accepts text extracted elsewhere.
 - Re-expanding the default MCP surface beyond the eleven core tools.
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
-
-`v0.15.2` is the current release candidate. It is not published.

docs/alpha/headless-ubuntu-install.md

@@ -12,7 +12,7 @@ Supported assumptions for this alpha:
 
 This is the current headless install path for Alice. Install unreleased
 development code from `--branch main` or use the latest published release tag
-(`v0.15.1`) for an immutable deployment.
+(`v0.15.2`) for an immutable deployment.
 
 Historical note: `v0.5.1-vnext-preview` and `v0.6.0-alpha-rc.2` are older milestones kept for audit trail and rollback evidence. Do not install them for new setups; they predate the v0.6.0 overhaul (hybrid retrieval, consolidated core MCP surface, per-agent API keys).
 
@@ -55,7 +55,7 @@ less install-alice.sh
 bash install-alice.sh --branch main --install-dir ~/alicebot
 ```
 
-For an immutable install after a release tag is published, replace `--branch main` with the latest published release tag (`v0.15.1`): `--tag v0.15.1`.
+For an immutable install after a release tag is published, replace `--branch main` with the latest published release tag (`v0.15.2`): `--tag v0.15.2`.
 
 Use `--non-interactive` only after you have chosen a safe install directory and know whether the host should install local Postgres.
 

docs/integrations/reference-paths.md

@@ -1,7 +1,7 @@
 # Reference Integration Paths
 
 This page is the path-selection guide for external builders adopting Alice on
-top of the latest published `v0.15.1` baseline. Later changes on `main` are
+top of the latest published `v0.15.2` baseline. Later changes on `main` are
 unreleased until they receive a release
 identity and publication evidence.
 

docs/release/v0.15.2-checksums.txt

@@ -0,0 +1,14 @@
+# Alice v0.15.2 — published artifact SHA-256 digests
+#
+# These are the exact digests of the wheel and source distribution published
+# to PyPI for v0.15.2 through GitHub Trusted Publishing. They also appear on the
+# project's PyPI page and on the v0.15.2 GitHub Release assets, and are bound to
+# this repository, the v0.15.2 tag, the publishing workflow, the exact commit,
+# and the protected pypi environment by PyPI's integrity attestations (the
+# /provenance endpoints).
+# Linux verify:  sha256sum -c v0.15.2-checksums.txt
+# macOS verify:  shasum -a 256 -c v0.15.2-checksums.txt
+# Run either command beside the downloaded files.
+#
+b68d9dd80cd08b954a70414fee2b195ebad75d93849194e88ad66b356aea2b16  alice_memory-0.15.2-py3-none-any.whl
+644af5829c05d746d476bb7f1b2b3e0731c397ceea95e0210137f1e0e9c91ed7  alice_memory-0.15.2.tar.gz

docs/release/v0.15.2-release-notes.md

@@ -1,5 +1,5 @@
 # Alice v0.15.2 Release Notes
-<!-- alice-release-state: {"schema_version":"alice_release_document_state_v1","version":"0.15.2","publication_status":"pending","checksums_status":"pending"} -->
+<!-- alice-release-state: {"schema_version":"alice_release_document_state_v1","version":"0.15.2","publication_status":"published","checksums_status":"recorded"} -->
 
 **The `/v1` API now requires an agent key, keyless callers are refused off
 loopback, and importers stop following links out of the directory you chose.**

docs/vnext/README.md

@@ -8,7 +8,7 @@ capture, hardened connector settings/state/secrets, agent-facing context packs
 and context trees, governed agent proposals, and a local scheduler runtime.
 
 The vNext architecture is now the active Alice product line.
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and latest-release-notes baseline. Its tag, release record, and published
 artifacts are immutable.
 `v0.12.0` shipped the Phase 3 structural refactor with **Structure only. Zero
@@ -68,7 +68,7 @@ Alice vNext has three functional layers:
 10. Use the current [release runbook](../../RELEASING.md) before publishing or
     tagging. The older [vNext preview checklist](../release/vnext-public-release-checklist.md)
     is retained only as historical evidence.
-11. Review the [latest published release notes](../release/v0.15.1-release-notes.md)
+11. Review the [latest published release notes](../release/v0.15.2-release-notes.md)
     and [known limitations](../alpha/known-limitations.md).
 12. Review the [dogfood daily checklist](../runbooks/vnext-dogfood-daily-checklist.md) before daily local preview use.
 13. Historical build-process summaries are archived under [docs/archive/process/](../archive/process/README.md).
@@ -82,7 +82,5 @@ connector OAuth, packaged browser extensions, hosted connector polling, cloud
 sync, channel transport, OCR/transcription execution, a hosted SLA, or automatic
 promotion of generated artifacts into trusted memory.
 
-`v0.15.1` is the latest published release and remains the install, checksum,
+`v0.15.2` is the latest published release and remains the install, checksum,
 and baseline reference.
-
-`v0.15.2` is the current release candidate. It is not published.