Merge pull request #710 from git-stunts/release/18.2.1-metadata

Release 18.2.1

Author: flyingrobots

.github/workflows/release.yml

@@ -6,7 +6,7 @@ on:
   workflow_dispatch:
     inputs:
       tag:
-        description: 'Release tag to publish, for example v17.0.0'
+        description: 'Release tag to publish, for example v18.2.1'
         required: true
         type: string
 

ARCHITECTURE.md

@@ -10,13 +10,13 @@ If you are learning the product for the first time, start with:
 
 ## Release posture
 
-`v18.1.2` is the current release target. Architecturally, it carries the v18
-read-model closeout from the current `main` release state: `Optic` is a
-runtime noun, observer reading envelopes are explicit, bounded support planning
-is named, the public learning shelf is consolidated under `docs/topics/`, and
-operator workflows live outside that shelf under `docs/operations/`. This patch
-adds a generated source-backed reference gate; it does not add a new runtime
-boundary.
+`v18.2.1` is the current release target. Architecturally, it keeps the v18
+read-model closeout from the current `main` release state while correcting the
+state-cache materialization path: `git-warp` owns frontier coordinates,
+snapshot eligibility, replay, and publication policy; `git-cas` remains the
+storage substrate. This patch reduces redundant live replay through
+coordinate-addressed snapshots, but it does not make full materialization a
+bounded optic read.
 
 The longer release notes live in [CHANGELOG.md](CHANGELOG.md). The runtime
 architecture below describes current implementation boundaries, not aspirational

CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [18.2.1] - 2026-06-30
+
+### Release notes
+
+`v18.2.1` corrects the state-cache materialization path introduced by
+`v18.2.0`. Live materialization now uses WARP-owned frontier coordinates for
+snapshot lookup and publication, while receipt-producing and diff-producing
+reads stay replay-backed so callers receive complete provenance and diff data.
+
+This release also documents the actual boundary: `git-cas` remains storage, and
+`git-warp` owns materialization cache policy, replay coordinates, and snapshot
+eligibility.
+
 ### Fixed
 
 - Live materialization now derives the current writer frontier, checks

README.md

@@ -42,10 +42,11 @@ It lets you:
 
 ## Latest release
 
-`v18.1.2` publishes the source-backed reference shelf for package entrypoints,
-root API exports, CLI commands, structured CLI errors, and public error classes.
-It also locks the release path so release-prep PRs tag the exact merged `main`
-commit, then publish npm and JSR from a maintainer-dispatched workflow.
+`v18.2.1` corrects the WARP-owned state-cache materialization path introduced
+in `v18.2.0`. Live materialization now uses current writer-frontier coordinates
+for exact and compatible predecessor snapshot reuse, publishes replay results
+under their real coordinate, and keeps diff-producing or receipt-producing reads
+replay-backed so callers receive complete diff and provenance data.
 
 See [CHANGELOG.md](CHANGELOG.md) for the full in-repository release notes.