diff --git a/docs/ISSUES.md b/docs/ISSUES.md
index 3f2d7a06..107fec3d 100644
--- a/docs/ISSUES.md
+++ b/docs/ISSUES.md
@@ -193,7 +193,21 @@ the flat plane, DEFAULTS the collision normal to (0,0,1), reverts CheckPos,
 and forces OK — producing every field of the captured fingerprint from
 retail's own code. **Stopping dead here may simply BE retail.**
 
-**Two open validations before this closes either way:**
+**RETAIL OBSERVED 2026-08-08 — THE AXIOM: "it glides, faster the more angle
+you run towards it."** The user ran the comparison in their retail client:
+angled approaches GLIDE laterally along the steep hillside, scaling with
+approach angle; perpendicular stops. acdream stops dead at every angle. The
+divergence is CONFIRMED — and since D0 proved the RESPONSE path faithful
+line-by-line, the divergence is UPSTREAM of it: the movement request's shape
+when it reaches the transition (retail's sub-step/walk_interp progression?),
+the broadphase/cell question, or state seeding. Next step is the designated
+Step -1 tool: attach cdb to the PDB-paired retail client at that exact slope
+and trace validate_walkable @0x0050d010 / transitional_insert @0x0050b6f0 /
+adjust_sphere_to_plane @0x00538210 WHILE the glide happens — the diff
+between retail's live inputs and ours in the same scenario IS the answer.
+
+**The two prior validations (both now resolved — the user's observation
+answers 1 and mandates 2's runtime session):**
 1. **The cheapest decisive test needs no debugger: the USER walks their
    RETAIL client into a comparable just-too-steep hillside at ~45° and
    reports slide vs dead stop.** Their expectation of sliding is currently