From 1cfb974377880c93075c3567e85f8491b768b722 Mon Sep 17 00:00:00 2001
From: Niroj33 <86530493+professor3333@users.noreply.github.com>
Date: Sun, 15 Nov 2026 09:30:46 +0545
Subject: [PATCH] Record the v0.2.0 release checks and rollback drill

release.yml passed on the v0.2.0 tag and pushed ghcr.io/professor3333/triggermap@sha256:cc1578f9...76ce (publicly pullable); the attached CRF bundle is byte-identical to v0.1.0's. The local rollback drill v0.1.0 -> v0.2.0 -> v0.1.0 verified every step and kept reviews (51 s).
---
 docs/deployment.md           |  8 +++++---
 docs/release_notes/v0.2.0.md | 10 ++++++++++
 2 files changed, 15 insertions(+), 3 deletions(-)

diff --git a/docs/deployment.md b/docs/deployment.md
index 13acda7..eedec08 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -134,9 +134,11 @@ each step, including that reviews saved along the way survive:
 TRIGGERMAP_HOST_PORT=8000 deploy/rollback_drill.sh <release-a> <release-b>
 ```
 
-Last run (2026-11-06, local Docker): rules release `r1`, then the v0.1.0 CRF release
-(`crf-batches-01-02`, a different image, bundle and policy), then rollback to `r1`. Every
-step verified, in 15 seconds total. The previous run was on 2026-10-20 (`r1` → `r2` → `r1`).
+Last run (2026-11-15, local Docker): v0.1.0, then v0.2.0 (a different image from the same CRF
+bundle and policy), then rollback to v0.1.0. Every step verified: ready check against the release
+manifest, extraction, idempotent review save, retrieval and export. Reviews were kept, and the
+run took 51 seconds. Earlier runs: 2026-11-06 (`r1` → v0.1.0 → `r1`, 15 s) and 2026-10-20
+(`r1` → `r2` → `r1`).
 
 The release image (`release.yml`) is built with `EXTRAS="serve baselines"`, so it serves both
 rules and CRF releases.
diff --git a/docs/release_notes/v0.2.0.md b/docs/release_notes/v0.2.0.md
index a838390..b73b324 100644
--- a/docs/release_notes/v0.2.0.md
+++ b/docs/release_notes/v0.2.0.md
@@ -73,6 +73,16 @@ evaluation, reproducibility, demo and documentation work since v0.1.0 ships with
   so the measured scores may not carry over to current advisories.
 - No usability study has been run.
 
+## Release checks (2026-11-15)
+
+- `release.yml` on the tag passed lint, types and tests, then built the image, passed the
+  container smoke test and pushed it: `ghcr.io/professor3333/triggermap@sha256:cc1578f9a488a09da717a298db5f0018350272fb5b540157f3d1016b04f376ce`
+  (from commit `1c2d0cc`). The image can be pulled without logging in.
+- The attached `crf-batches-01-02.tgz` is byte-identical to the v0.1.0 asset (SHA-256 above).
+- Rollback drill on local Docker: v0.1.0 → v0.2.0 → v0.1.0. Every step was verified (ready check,
+  extraction, idempotent review save, retrieval, export), reviews were kept, and the run took
+  51 seconds.
+
 ## Deploying it
 
 Follow [`docs/deployment.md`](../deployment.md) with the image digest from