v0.33.0-beta — eight corpora moved; every shape is now scored

Cut for AgentMemory's C-D full-family run. It carries the two fixes named as blocking, neither
of which was in any published package before now.

	0.32.0-beta	this release
forgetting	7fe6e166dbf1	be14b81ae4e2
prospective	a570b890a5b9	39f205b72294 — due-window answer key

Breaking — eight of nine corpora changed bytes

Only bitemporal is unchanged (abf2f3f43219). question_id sets are stable across the move, so
compare on corpus_sha256, never on the question id. revision now carries the sha
(v5+<sha12>) and is gated by a test, so the metadata is load-bearing.

Two are retrieval-control changes rather than content changes: Conjunction grows 50 → 65
(ADR-029's declared cost for the new conditional-branch shape) and WorkingMemory holds H
constant at 60 non-gold sessions on every rung.

Every shape is now scored by something

32 shapes — 29 on retrieval headroom, 3 on a declared other axis with its own bar. Three shapes
were previously skipped in silence, one of them 30% of its vertical.

• V10/V11 abstention arms for questions with no gold. forgetting/never-known: 15/15 and 15/15.
• paired_arms at vertical level — forgetting 0.4667 @ 3.68 sd and prospective 0.6316 @
  5.878 sd had never been published.
• conjunction/conditional-branch — across the 470 prior questions, not one required resolving
  a conditional. V1 15/15, V9 0/15, headroom 1.00 fully reachable.
• chance_floor / v9_above_chance — 71 questions across 6 shapes name their own candidates
  and none had published a floor beside their accuracy arms.

Fixed — including a defect that shipped in 0.32.0-beta

72 distractors that answer any question asked. Forgetting's parity filler stated a value with no
setup naming the noun, so "I settled on Marloe Basic." is about nothing NAMED. 29 of 50 questions,
including 13 of the 15 haystacks whose premise is that no answer exists. No existing arm could
see it — they all ask whether the model produced THE GOLD, and this produces something else. 72 → 0.

WorkingMemory's ladder measured context volume and called it distance. H = distance + 1, and
BM25 is position-blind. 2 of 5 rungs discriminated; now 5 of 5.

V6 read 20/35 on Forgetting where it is 20/20, and its scope was a hardcoded two-vertical list —
now a per-question and per-component declaration, 85 → 200 questions, family 164/165.

prospective/due-window's answer key was wrong, not merely misleading: V8 4/18 → 16/18.

Known defects and declared residuals

arithmetic V6 49/50 (one miscount, explained rather than tuned away); two V6 results that are
undecidable rather than passing; prospective/seed-carry-over mixes two populations (0.60 and
0.1429) and publishes the split; closed_choice_k has two pinned limits; WorkingMemory gave up
volume sensitivity to isolate distance.

Full disclosure in CHANGELOG.md, derived by diffing the previous tag rather than written from
memory. ADR-028 §§13–20, ADR-029 §9.

Verification

1153/1153 on net8.0, net9.0 and net10.0; 9447/9449 on AgentEval.Tests; all nine corpora reproduce
byte-for-byte from their committed generators, in CI.