Dispose the wave-6 class-1-window observations (release-contract-window-close)

The pre-release pass's last contract-text dispositions, each dated
in-place citing the 2026-10-11 close-out pass (ADR-017 §2's terminal
window):

- Publish→wake ordering tolerance: documented tolerance (decided with
  the user) — core-contract.md streams paragraph + delivery-obligations
  bullet, ADR-015 §4 companion annotation; the wake = offset-order
  ADR amendment declined (commit-ordered pg visibility; hint-shaped
  wake posture).
- ADR-023 §2: heartbeat(extend) and save_offset(offset) join the
  boundary/offset row (total — negatives well-defined), with the
  home rationale annotated; core-contract's domain paragraph
  mirrors; the backlog numeric-domain row registers the suite-duty
  follow-up.
- ADR-021 §5: EventReceiver::try_recv's closed shape pinned
  (Err(Closed), mirroring ADR-008 §3); core-contract subscribe arms
  sentence extended.
- get_job prose: core-contract queues section + queues.md's reads
  sentence now say the uniform id-global / get_job_tx-filtered split.
- Mem-arithmetic observation: no-action disposition recorded in the
  task Notes (byte-level transplants; equivalence suite-pinned
  three-way).

Suite stamps checked — no accumulation required (no cited § text
changed meaning). Docs-only; gates green: build, workspace tests,
clippy -D warnings, fmt, fuzz replay, rustdoc -D warnings,
taskgraph validate (79 tasks).

docs/architecture/decisions/015-streams-depth.md

@@ -201,6 +201,19 @@ never compared.)* It is deliberately *not* stronger than both engines can
 implement by a shared SQL shape (`ORDER BY offset ASC` is already
 both engines' claim path) and not weaker than the mechanism's purpose
 (replay demands monotone positions).
+*(Annotation, 2026-10-11 — the pre-release class-1 close-out pass
+([ADR-017](017-contract-versioning.md) §2), disposing the wave-6
+review gate's recorded ordering observation with the user's
+documented-tolerance call: this row pins *read* order — `offset ASC`
+over the committed log — and pins nothing about **wake-fire order**;
+wake-fire order need not match offset order, and a wake-driven
+subscriber's drain can checkpoint past an event whose publish
+completed out of offset order (the event stays in the log; a fresh
+subscribe whose checkpoint is below it sees it). The tolerance's full
+text and the consumer recipe live in
+[core-contract.md](../../architecture/core-contract.md)'s streams
+section — the delivery-guarantee obligations bullet carries it too.
+The heavier wake = offset-order amendment was weighed and declined.)*
 
 ### 5. Retention: `trim_to` on the stream handle — a consumer-invoked bounded-growth op