docs: file #269 - slope-stop slide residual; byte-verify friction + jump chain (refutes jump-height hypothesis)

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

docs/ISSUES.md

@@ -98,6 +98,39 @@ Copy this block when adding a new issue:
 
 ---
 
+## #269 — Slope-stop slide runs too far (post-bounce-rework residual)
+
+**Status:** OPEN (user live gate 2026-07-30 — "almost pass with merits")
+**Severity:** LOW-MEDIUM (feel residual; bounce family otherwise accepted)
+**Component:** physics / landing slide decay
+
+**Symptom:** after the #265 landing-bounce rework (accepted: downhill
+bounce chain, flat pop, uphill clean landing), the user reports the
+character SOMETIMES slides too far when stopping on slopes vs retail.
+
+**Byte-verified NOT the cause (all decoded from the PDB-paired binary this
+session — do not re-audit):** `calc_friction` 0x0050ee70 is byte-identical
+to our port in BOTH branches (0.25 dot gate, into-plane removal,
+`(1-friction)^dt` decay, DEFAULT_FRICTION 0.95, sled bands 1.5625/6.25 +
+cos(10°) with base 0.2); the jump chain end-to-end (`GetJumpHeight`
+0x006b09b0 exact incl. 1300/22.2/0.05/0.35, `InqJumpVelocity` 0x00592980
+`vz=sqrt(h*19.6)`, powerbar charge 1.0 s / 0.8 s dual-wield) — the user's
+"we jump too high" hypothesis is REFUTED, jump height is retail-parity
+(our eff skill is 5 lower pending #268's augmentation port). Retail has no
+Sledding auto-toggle (P2 finding re-confirmed; no `state |= 0x800000`
+writer exists).
+
+**Next step (behavior question, not code):** live A/B per the cdb
+workflow — breakpoints on `calc_friction`/`handle_all_collisions` dumping
+velocity per tick while the retail client lands + slides on a slope, vs an
+`ACDREAM_CAPTURE_RESOLVE` capture of the same maneuver on the same slope.
+Compare the decay curves; the first diverging tick names the mechanism.
+Candidates the trace discriminates: hop-chain cadence (friction skips
+airborne micro-hop ticks), gravity-tangential rebuild timing, quantum
+alignment.
+
+---
+
 ## #268 — Character panel: vitae color, buff coloring, and augmentation bonuses
 
 **Status:** OPEN (user direction 2026-07-30, follow-up to #267)