From 2b5367a81a11f15d23318e15f92492ac02cf6534 Mon Sep 17 00:00:00 2001 From: Erik Date: Fri, 7 Aug 2026 11:18:44 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20#345=20retail=20observed=20=E2=80=94=20?= =?UTF-8?q?it=20GLIDES,=20scaling=20with=20angle;=20divergence=20confirmed?= =?UTF-8?q?,=20upstream=20of=20the=20proven-faithful=20response=20path?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The user's side-by-side is the axiom: retail glides laterally along the steep hillside, faster with more approach angle; acdream stops dead. D0's line-by-line faithfulness of the response path relocates the divergence upstream — the request shape reaching the transition, the broadphase question, or state seeding. Next: the cdb live-trace session at the slope, per the workflow's Step -1. Co-Authored-By: Claude Opus 5 --- docs/ISSUES.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) 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