fix(physics): S4/AD-65 — the away-from-plane response snaps to the surface, as retail does

Campaign S slice S4, the half that landed. Retail's CTransition::
adjust_offset @0x0050a370 branches on dot(offset, contactPlane.N) at
0x0050a4fa: moving INTO the plane subtracts the normal component
(0x0050a529), moving AWAY calls Plane::snap_to_plane @0x00509c50 —
which preserves X and Y and re-solves ONLY Z so the offset lies in the
plane (the d terms cancel algebraically), no-op under the
0.000199999995f |N.z| epsilon. acdream ran the orthogonal projection in
BOTH directions, shrinking downhill XY travel by cos^2(theta): 25% at
30 degrees, 50% at 45 — AD-65's recorded shortfall, now retired.

The combined Opus review independently re-derived the algebra, the
branch polarity, the epsilon's bit-identity (17b75139), and the
sabotage magnitude (the re-instated projection yields X = 0.75 =
cos^2 30 exactly), and verified the delta is 4 non-comment lines with
the into-plane arm, the crease arm, and both no-plane arms untouched.
Its blast-radius sweep found the away arm exercised but NOT
discriminated by any pre-existing test — every one asserts lower
bounds the snap over-satisfies — so the two new exact-value tests are
the only discriminating coverage, recorded in the test's class doc,
and the felt 33-100% downhill speed-up is the morning gate's one row.

AD-66 (the push-out's bare radius) is WITHHELD: byte-confirmed twice,
implemented, then pulled after the same clean-room binaries measured
contradictory absorbed-tick outcomes flipping with nothing but test
assert shape — issue #341 carries the observation matrix and the
apparatus plan; its two exact-value tests are [Skip]-ed; the retained
substitution's rationale is restored at the site per review F1, with
the review's remaining findings (F2/F3/F4/F5/F6) applied and F8 filed
as #342. AD-69 filed: the same block omits retail's get_block_offset
seam-frame correction, deferred to the AD-66 relanding for
attributability. #340 filed: a fifth load-sensitive flake.

Review verdict: PASS. AD-65 is provably unable to reach the #341
anomaly's code path (the absorb scenario takes the crease arm).
Clean-room suite: 11,239 passed / 6 skipped / 0 failed.

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

docs/ISSUES.md

@@ -158,6 +158,68 @@ resolution.
 
 ---
 
+## #341 — AD-66's landing is blocked by an unexplained measurement flip on the #331 absorb scenario
+
+**Status:** OPEN — HIGH priority for the next physics session; the fix itself
+is byte-proven, the BLOCKER is that the measurement chain contradicted itself.
+**Filed:** 2026-08-07 (overnight), at the S4 landing split.
+
+Retail's `adjust_offset` safety push-out uses the BARE sphere radius in both
+its trigger and its `zDist` numerator (byte-anchored twice in AD-66's register
+row). Landing that in `Transition.AdjustOffset` made exactly one suite test
+fail — `RuntimeRemoteUphillProgressTests.AnExactlyUpSlopeOffsetIsAbsorbedByThePersistedSlidingNormal`,
+the #331 absorb characterization pin — and the attempt to recalibrate it
+produced OBSERVATIONS THAT FLIP WITH THE SHAPE OF THE TEST'S POST-TICK
+ASSERTS, which is not physically possible for honestly-measured stored state:
+
+| test-code variant (identical code before/during the 5 absorbed ticks) | observed Z after ticks | runs |
+|---|---|---|
+| original exact-latch `Assert.Equal(latched, body.Position)` | latched + 0.0798 (LIFT) | implementer's suite run + 6 consecutive runs + 1 more after restore |
+| recalibrated: compute `restingLift` from `body.ContactPlane` post-tick, then component asserts | latched exactly (NO lift) | 1 run (version A) + 4+ runs (version C) incl. a full bin/obj clean-room |
+
+Both shapes were run against binaries proven to contain the AD-66 fix (the S4
+conformance exact-value tests passed in the same clean-room). 0.0798 m =
+`0.48 * (1/cos31° − 1)`, the delta between the two resting heights, so BOTH
+outcomes are physically coherent stories — the problem is that the same
+binaries told both.
+
+**Hypotheses deliberately NOT chased at 04:00:** a property-read side effect
+(reading `body.ContactPlane` between tick and assert — should be impossible);
+xUnit execution-order/parallelism interacting with harness or engine state;
+JIT/tiering differences by method shape; yet another artifact-staleness vector
+not covered by bin/obj deletion. **Next session: instrument the scenario
+itself** (per-tick position prints inside the test, a matrix of assert-shape ×
+clean-room state), per `feedback_apparatus_for_physics_bugs` — three
+contradictory reads means apparatus, not a fourth guess.
+
+Until resolved: the AD-66 production code is REVERTED to the radius*N.z
+substitution (comment block at the site names this issue), its two exact-value
+conformance tests are `[Skip]`-ed with pointers here, and the register row
+stays ACTIVE. **The byte evidence was never the open question — do not
+"resolve" this by re-deriving it a third time.**
+
+---
+
+## #342 — `Issue265SteepSlopeCaptureBisectTests.cs:920` is a tautology: `Assert.Equal(x.Z > 0.01f, x.Z > 0.01f)`
+
+**Status:** OPEN. LOW — a dead assertion that can never fail, in the
+steep-slope family Campaign S leans on. Found by the S4 review (F8),
+out of that slice's scope. Fix = recover the intended comparison from the
+test's context, not just delete.
+**Filed:** 2026-08-07.
+
+---
+
+## #340 — `StreamingWorkBudgetTests.DestinationAndEmptyUnloadPriorityNeverBypassPublicationBudget` is a FIFTH load-sensitive flake
+
+**Status:** OPEN. LOW.
+**Filed:** 2026-08-07 (overnight), first observed in a clean-room full-suite
+run; passes standalone immediately after. Distinct from #302, #308, #321 and
+#336 per the never-conflate rule. Same class: load-sensitive, deterministic in
+isolation.
+
+---
+
 ## #339 — Stuck in portal space: the destination reveal generation never becomes ready
 
 **Status:** OPEN — observed live 2026-08-07, evidence captured. **Not chased**;