diff --git a/docs/ISSUES.md b/docs/ISSUES.md
index 9a9dee1b..591a5a93 100644
--- a/docs/ISSUES.md
+++ b/docs/ISSUES.md
@@ -99,7 +99,9 @@ Copy this block when adding a new issue:
 
 ## #255 — Two RetailDatLoader concurrency tests measured the thread pool, not the loader
 
-**Status:** DONE — 2026-07-28; the pair now runs on dedicated threads
+**Status:** REOPENED — 2026-07-29; `AnimationCache_Coalesces…` still fails under
+full-suite load on Windows despite the `LongRunning` fix (see the reopening note
+at the end of this issue)
 **Severity:** LOW (test infrastructure only; no production defect)
 **Filed:** 2026-07-28
 **Component:** tests / xUnit parallelism, content loaders
@@ -134,6 +136,32 @@ afterwards.
 
 **Files:** `tests/AcDream.Content.Tests/Vfx/RetailDatLoaderTests.cs`.
 
+**Reopening note — 2026-07-29 (wire-stack audit session).**
+`AnimationCache_CoalescesSameDidAndAllowsUnrelatedReadsInParallel` still fails
+intermittently on Windows under full-solution load, on a tree that already
+contains the `LongRunning` fix (`c7861020`, in the base lineage of this
+session's `b70b9832`). Observed **2 failures in 4 full-suite runs**; the
+project passes **124/124 every time it is run alone**. The two failures were
+both `--no-build` runs, which start the projects faster and so apply more
+parallel pressure — consistent with the original diagnosis rather than a new
+cause.
+
+`TaskCreationOptions.LongRunning` is a *hint*. It asks for a dedicated thread;
+it does not guarantee one, and it does not stop the rest of the solution's test
+host from saturating the machine while these two 40 ms sleeps overlap. So the
+assertion on `RawDatabase.MaxConcurrentReads` is still measuring the host.
+`PhysicsScriptLoader_AllowsConcurrentFirstReads` was not observed failing in
+this session, but it shares the helper and should be treated as the same risk.
+
+Suggested next step: stop asserting on observed parallelism. Gate the two
+threads on a `Barrier`/`CountdownEvent` so both are provably inside the read
+before either is released — then `MaxConcurrentReads == 2` is a property of the
+loader, not of the scheduler, and the test cannot flake no matter how loaded
+the box is.
+
+This session changed nothing under `AcDream.Content`; its diff is confined to
+`src/AcDream.Core.Net`, that project's tests, and `docs/`.
+
 ---
 
 ## #254 — Logout confirmation wait overran its timeout on a starved thread pool