3ngram 1.8.2

3ngram v1.8.2

Patch: the v1.8.0 release images failed the release scan on a Debian
package, so this release re-cuts v1.8.0's content on a patched base image.

Neither v1.8.0 nor v1.8.1 was published: Trivy rejected v1.8.0's images on
libpcre2-8-0 10.42-1 (CVE-2026-86145, high) in the pinned
node:24-bookworm-slim digest, and the v1.8.1 tag was pushed against the wrong
commit before its promotion had merged. v* tags are immutable, so both
numbers are burned and this release carries their content, exactly as v1.6.3
did for v1.6.2.

Changes

• Release images move to the current node:24-bookworm-slim digest
  (#243): same Debian 12.15 and Node 24.21.0, with libpcre2-8-0 10.42-1+deb12u1 installed.

• Everything listed under v1.8.0, which never shipped: revise
  inherits filing from the predecessor (#222), the revise move disposition
  (#233, with the hard rule 1 carve-out), get_memories returns
  supersededBy (#223), the agent-session read endpoints (#203, migration
  0037_triage_attempt_log), consolidation that no longer re-proposes settled
  pairs (#220), and the overdue grace window COMMITMENT_EXPIRY_GRACE_DAYS
  (#221).

Known gap

The revise tool's one-line description still reads "never edits in place";
a description refresh needs the tool-selection embeddings regenerated with an
OpenAI key and follows in a later release.

Operations

One migration since v1.6.3: 0037_triage_attempt_log (schema head 0036 to
0037). Run it before the server promote. The worker gains one optional
environment variable, COMMITMENT_EXPIRY_GRACE_DAYS. Both triage mechanisms
(SESSION_CLOSER_ENABLED, THREENGRAM_STOP_NUDGE) remain default-off.

Immutable container reference

ghcr.io/b3dmar/3ngram@sha256:a248eecfd118dec567101495a00f94dbad9d810d59d901775971294c35798eac