docs(AS): AS4 fix round — oracle corrections (D1), gate carry-note (D2), record fixes (D3); file #442

The AS4 dual-lens review approved the port as exact and required a
docs-only fix round:

- Ground truth §2b row 1: the Society gate is PRESENCE of Int 281
  (AppraisalProfile::InqInt @0x005B3830 returns found/not-found), not
  value!=0; the color rule is same-bit-first (@0x004b49fd/@0x004b4a49/
  @0x004b4a8b) so a multi-bit local player still resolves green on a
  match; the ??? arm precedes the Radiant Blood test.
- Ruling R5 corrected: the row model carries CreatureAppraisalValueStyle
  but ResolveColor is a deliberate no-op until AP-110's FontInfo-list
  residual lands — the Society green/red is model-only and invisible at
  the connected gate; AS6's script must not gate on row colors.
- Ledger: AS4 land 4ade9b04; true full-solution hermetic count is 15,528
  (the AS4 commit body's 15,410 was a mis-report; the review re-ran and
  reconciled 15,483 + 45 new = 15,528).
- #442 filed: pre-existing parallel-load flake in the shadow-caster
  zero-allocation pin, surfaced by the review's full-solution run;
  isolation evidence recorded; unrelated to Campaign AS.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/ISSUES.md

@@ -24,6 +24,24 @@ What does NOT go here:
 - Every session: scan OPEN issues at start; promote/close anything we touched during the session before ending.
 - Promoting to a Phase: mark as `DONE (promoted to Phase X)` + commit SHA where the Phase entry landed.
 
+## #442 — Flake: DirectionalShadowCasterFrameTests.WarmDenseChangedFrames_AllocateZeroAndReadNoSceneRecords fails intermittently under full parallel suite load
+
+**Status:** OPEN.
+**Component:** rendering tests / zero-allocation pins.
+**Filed:** 2026-08-25 (surfaced by the Campaign AS AS4 Opus review's full-solution run; unrelated to AS4 — the slice touches no rendering code).
+
+A `GC.GetAllocatedBytesForCurrentThread()` zero-allocation assertion in
+`tests/AcDream.App.Tests/Rendering/DirectionalShadowCasterFrameTests.cs`
+trips intermittently under parallel load — same class as the known
+`RuntimeCollisionReportingStateTests.WarmedSteadyContactRefreshDoesNotAllocate`
+flake (full-solution parallel load only) and #439's headroom family.
+Review isolation evidence (Release): alone (15-test class) passes; App
+hermetic lane run 1 = 6,252/1 failed, run 2 (same command) = 6,253/0.
+Last touched by `d78ce100` (a render commit). Candidate fixes when picked
+up: the established `Lane=Timing` quarantine per `docs/release-gate.md`
+(do NOT chase individually), or a warmed re-measure loop like other
+zero-alloc pins use. Do not weaken the assertion itself without measuring.
+
 ## #441 — Death return to lifestone: stuck in portal once; arrived once with world not ready (missing doors/portals)
 
 **Status:** OPEN (intermittent — did not reproduce under probes 2026-08-24).