From 60be20a4b8f04a6cfc84a221f26bdc2cd68088f3 Mon Sep 17 00:00:00 2001 From: sylph-decoder Date: Wed, 2 Sep 2026 20:11:12 +0000 Subject: [PATCH] handoff: correct F5 -- keep clock:"shared", A advances it to the settle Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t --- docs/port/HANDOFF.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/docs/port/HANDOFF.md b/docs/port/HANDOFF.md index f55105e5..a34ad2c3 100644 --- a/docs/port/HANDOFF.md +++ b/docs/port/HANDOFF.md @@ -6111,3 +6111,33 @@ at α255). The plate half is not so limited — 0 vs 11 intermediate frames. ⚠️ Also: Ⓐ **after** the title settles is *accepted* and the screen leaves. Three presses to boot, as F4 said. + +## 🔴 F5 CORRECTED same day — Ⓐ snaps the WHOLE title (`630a4a2`) + +**Undo what I told you an hour ago.** I said Ⓐ leaves the artwork animating and +that this refuted `clock: "shared"`. **Wrong on both.** + +A pre-registered wider test pressed Ⓐ at the sweep's gate (`t≈70`) instead of 40 +frames later, leaving ~40 frames of artwork still animating: + +``` +f435 | 8ECA:-1.00,a55 EAC3:-0.83,a27 8154:-0.74,a27 artwork mid-ramp +f436 | 8154:-1.54,a255 EAC3:-0.90,a255 8154:-0.54,a255 gone; settled at full +``` + +Three elements mid-fade-in vanish in one frame. **The sweep enters at α255 with +no ramp**, where no-input runs ramp it 17→255 over ~15 frames per its parent's +declared `t=70…100`. The title clock jumped past `t=100` — and *not* past 250, +or `ptloop01`'s exit would have hidden the sweep. So Ⓐ advances the clock into +`[100,238]`, i.e. the settle window. + +**`clock: "shared"` stands. Keep one clock, and have Ⓐ advance it to the settle.** + +✅ Unchanged and now stronger: Ⓐ is a **cut**, not an acceleration — the parent's +whole 15-frame ramp is skipped, not compressed. + +**Why I got it wrong:** the press takes **11–12 frames** to take effect (`f445→ +f456`, `f424→f436`). My 5-frame artwork window sat entirely inside that gap, so +it matched the control because the input had not been acted on yet. Worth your +knowing if you script inputs: a control matched at the wrong instant is not a +control.