# Morning gate — 2026-08-07 (one sitting)

**Status: COMPLETE 2026-08-07 — G1 user-passed ("Slopes feels good").**

Everything below folds the deferred visual gates into one sitting, ordered so
travel between sites doubles as #339 reproduction attempts. Launch is
prepared by the overnight session; **the client is NOT launched until you're
back** (your instruction).

## 0. Launch (the lead runs this when you say go)

Main checkout, absolute path, probes armed. The first `[step-h]` line in the
log must print the assembly path under
`C:\Users\erikn\source\repos\acdream\src\` — that is the wrong-binary guard,
now part of every capture.

## 1. Closed overnight with nothing owed to your eyes

- **#32 local edge-slide** — you passed it at the Rithwic cliff ("Yes works
  now"). Ledger closed, AD-67 filed for the one kept residual.
- **#338 step heights** — headline refuted by full-capture statistics
  (111,248 authored-pair resolves vs 358 placeholder ones); no production
  change, nothing to look at. AD-68 records the benign async-residency
  placeholder.
- **AP-157 (S1A)** — measured, both halves resolved without a code change:
  the CylHeight half is retail's own behaviour (byte-verified), and the
  sorting-sphere half is real vs retail's registration set but PROVEN unable
  to change any collision outcome (flood and test geometry are the same
  spheres). Fix deferred to the next bake-schema revision.
- **AD-55 (S5) — closed, and the fix turned out to be a WEEK OLD.** The
  cos(10°) constant has been live in production since 2026-07-30
  (`252e8068`); you've been playing on it. Tonight's byte-decode is an
  independent confirmation. The register row claiming otherwise was a
  ZOMBIE: an unrelated revert (`a8a7d64b`) resurrected the retired row —
  and, found by auditing that same revert, had also silently DELETED the
  then-active AD-56 row. Both corruptions fixed; the class is now a memory
  rule. No feel gate owed for S5.

## 2. The sitting — ONE row

| # | What | Where / how | Pass looks like |
|---|---|---|---|
| G1 | **S4 / AD-65 — downhill slope feel.** The away-from-plane response now
  snaps to the surface (XY preserved) instead of projecting (XY shrunk by
  cos²θ — 25% at 30°, 50% at 45°). | Run DOWN a long slope (the Rithwic
  descent works), then across it diagonally; jump down-slope and land
  running. | Downhill ground speed feels like retail — no "wading" slowdown
  on descents; no new stutter or floatiness; landings keep momentum
  downhill. |

That is the whole sitting: **one slope run, ~3 minutes.** Everything else
either closed with no gate owed or was deliberately withheld (below).

## 2.5 Withheld / deferred overnight — nothing to test, decisions recorded

- **AD-66 (the push-out's bare radius) — WITHHELD, issue #341.** The port is
  byte-proven twice over, but the landing produced a measurement that
  contradicted itself (same binaries, opposite outcomes flipping with test
  assert shape). Parked behind an instrumentation plan rather than guessed
  at. AD-69 filed alongside: the same block misses retail's seam-frame
  correction.
- **#330 headless collision — wiring withheld, hoist landed.** Dual review
  converged on a real dependency the contract missed: headless has no
  remote-motion tick, so spawn-registered shadows would freeze into phantom
  obstacles. The issue now carries the full seven-point scope map.
- **S1B (indoor box-admit) and S2 (static sphere emission)** — contracts
  written and committed, not implemented; next session picks them up
  directly.
- **S3 — cancelled**: planned on a misreading; open doors are ethereal, so
  AP-84's approximation is behaviourally equivalent. The register was right.

## 3. Free riders during travel

- **#339 portal-space hang** — every portal you take is a reproduction
  attempt; if you get stuck again, the log captures the readiness flags and
  the session becomes the diagnosis session. Nothing to do actively.

## 4. Deliberately NOT in this sitting

- **C5c's connected-gate batch** (~1 hr: D-1 scenarios, AP-136 six-step park,
  route-7, two-client, nine-stop soak) — standing debt by your direction;
  say the word any morning and it becomes its own sitting. The probe family
  stays in the tree until it runs.
- **AP-156 scale question** — retail does NOT scale cross-cell flood spheres;
  we do. Matching retail here means adopting a retail bug whose direction is
  walk-through for shrunk objects. Your call, explicitly, before any code
  changes: keep our over-inclusive scaling (safe, divergent) or match retail
  (faithful, under-inclusive for scale<1). One sentence from you settles it.