changelog: name pi-obsmem 3.1.4 (e7d77dc) as the next rebuild's implicit adoption

check-doc-drift.sh was rc=1: pi-observational-memory moved cba0334 (3.1.3) ->
e7d77dc (3.1.4) upstream on 2026-09-20, the day after the v1.9.3 tag, and
nothing named it above the v1.9.3 heading.

No code change is needed or wanted here. PI_OBSMEM_REF defaults to master in
Dockerfile.variant and CI's resolve-versions turns that into a SHA at build
time, so the next rebuild adopts this whether or not anyone acts -- which is
precisely why it has to be written down. There is no pin in this repo to bump,
so the CHANGELOG is the only record a reader of the next tag would have.

v1.9.3 itself has no defect: its manifest, image labels and baked
/opt/pi-observational-memory clone all agree on cba0334. The drift is
post-tag, so a green drift reading taken on 2026-09-19 was correct when taken.

Measured, not assumed: the range cba0334...e7d77dc is 4 commits whose only
substance is one line in src/agents/worker-stream.ts (preserve registry
receiver when resolving stream, PR #78 / issue #77) plus a 19-line regression
test; the rest is the version bump and release merge. peerDependencies are
unchanged (all four @earendil-works/* peers still *) and there is no engines
block, so no pi or node floor to clear.

Gate now rc=0: "OK pi-obsmem cba0334 -> e7d77dc since v1.9.3, named above the
v1.9.3 heading".

CHANGELOG.md

@@ -11,6 +11,39 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
 
 ---
 
+## Unreleased
+
+### pi-observational-memory 3.1.3 → 3.1.4 (`cba0334` → `e7d77dc`)
+
+No change in this repo. `PI_OBSMEM_REF` defaults to `master`
+(`Dockerfile.variant`) and CI resolves it to a SHA at build time
+(`docker-publish.yml`, `resolve-versions`), so the next rebuild bakes this
+whether or not anyone acts — which is exactly why it is written down here. The
+floating ref means this CHANGELOG is the only place a reader of the next tag can
+learn that the component moved.
+
+v1.9.3 shipped `cba0334` (3.1.3) and was internally consistent: its manifest,
+its image labels and the baked `/opt/pi-observational-memory` clone all agree on
+that SHA. Upstream `master` then moved to `e7d77dc` (3.1.4) on **2026-09-20**,
+the day *after* the v1.9.3 tag — so the drift is real but v1.9.3 has no defect,
+and a green `check-doc-drift.sh` reading taken before that date was correct when
+it was taken.
+
+| | |
+|---|---|
+| Upstream range | [`cba0334...e7d77dc`](https://github.com/elpapi42/pi-observational-memory/compare/cba03347a60af8b8afbb35677ade4d6bb05d4c5a...e7d77dc9a8305acb8054124e47662b3c766c2321) — 4 commits |
+| Substance | one line in `src/agents/worker-stream.ts` — *preserve registry receiver when resolving stream* (PR #78, upstream issue #77) — plus a 19-line regression test |
+| Remainder | `chore(release): prepare 3.1.4` (version bump) and the release merge (PR #79) |
+| `peerDependencies` | unchanged — all four `@earendil-works/*` peers still `*`, so no pi floor to clear |
+| `engines` | absent in both — no node floor |
+
+Because the ref floats, the SHA this repo actually bakes is whatever `master`
+resolves to **at build time**. If upstream moves again before the next tag, the
+value above is stale and `check-doc-drift.sh` will say so; re-run it immediately
+before tagging rather than trusting this row.
+
+---
+
 ## v1.9.3 — 2026-09-19
 
 ### Dependency audit (2026-09-19)