From eec50bbd2417961b7daa77763236646d9d4fcdbf Mon Sep 17 00:00:00 2001 From: Erik Date: Fri, 7 Aug 2026 07:19:20 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20#341=20decision=20=E2=80=94=20user=20di?= =?UTF-8?q?rects=20porting=20the=20retail=20pair=20(tangent=20rest=20+=20b?= =?UTF-8?q?are=20trigger,=20one=20slice)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 5 --- docs/ISSUES.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/ISSUES.md b/docs/ISSUES.md index 2f9189b8..5f3129c0 100644 --- a/docs/ISSUES.md +++ b/docs/ISSUES.md @@ -238,11 +238,13 @@ rests TANGENT to the slope. Two independent decompilers now agree. Consequences, under the bare trigger, a planted start lifts once — which of the two the harness settle leaves is plausibly order-dependent test state. -**Queued decision (user, no urgency): port the retail pair (feet float -slightly on slopes, exactly like retail — a visible feel change gated by -eyes) or keep our pair (planted feet, one register row covering placement + -trigger together, AD-66 re-titled accordingly).** Retail-first says port; it -is deliberately not done silently because the difference is visible. +**DECIDED 2026-08-07 by the user: "port the retail pair."** Tangent resting +placement + bare-radius trigger land TOGETHER as one slice (S4b), gated by +the user's eyes on a slope. The slice must first establish WHERE our planted +rest comes from (the live capture's r*N.z rest was measured on outdoor +TERRAIN — the prime suspect is the outdoor ground placement rather than the +ported BSP walkable solve, which should already be tangent if the port of +@0x00538210 is faithful). AD-69's seam-frame correction rides along. **Hypotheses deliberately NOT chased at 04:00:** a property-read side effect (reading `body.ContactPlane` between tick and assert — should be impossible);