fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

handoff+index: a .tbm draws, and screen render omits it silently

Browse Source 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 10:53:57 +00:00
parent ddc2a8e36b
commit dc0b84c87f
2 changed files with 30 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
docs/port/HANDOFF.md
View File

@@ -2533,7 +2533,35 @@ whatever it returns — the same reason a truncated log and a t=0 render both lo
fine from inside. Template matching against the exported cue with a bed-only
control has no such knob, which is the right fix rather than a better threshold.
## 🟡 2026-08-30 — the `.tbm` question is still open (two runs), and a driving trap you should know
## ✅ 2026-08-30 — a `.tbm` DRAWS. And `screen render` is wrong on any screen with one.
**The `TUTORIAL` screen was reached and captured**
([capture](../re/captures/title-builds/live-tutorial-screen.png)). It has a
**full-screen blue circuit/hex background**. `GP_TUTORIAL` build 0's **element 0 is
`pubase.tbm`, pivot (640, 360)** — 1280×720, the only full-screen *textured* element
in the bundle. Our render of the same build is the **identical layout on pure
black**: 6.0–6.4 % inked against the game's 99.7 %
([render](../re/captures/title-builds/render-tutorial-build0-for-comparison.png)).
🔴 **Two things follow, and the second is the one that touches you:**
1. `ui-forced-backdrop.md`'s surviving "inert" reading is **refuted** — its 24
`.tbm` deciders are **correct**, not harmless. None is on your five screens, so
nothing you ship moves; but if the alpha-over assumption under that rule fails,
those 24 go for real.
2. **`sylpheed-cli screen render` silently omits the background of every screen
carrying a `.tbm`.** No diagnostic. If you ever diff against it outside the five
menu screens, that is a difference that is *ours*, not yours.
⚠️ Reach: one `.tbm` observed. The class question — does a `.tbm` draw at all — is
settled; the ten other families are not individually seen.
📌 **And the driving trap from the failed runs is still worth having**: a 0.12 s Ⓐ
issued while the guest is loading is **missed entirely** — 2 `[file-pad] vk=5800`
lines is *one* press. "The press did nothing" and "there was no press" are identical
on screen; only `[RE-INPUT]` separates them. Hold 0.5 s and confirm delivery.
[`tbm-submenu-not-reached.md`](../re/structures/tbm-submenu-not-reached.md)
Not something you need — none of the 24 `.tbm` deciders is on your five screens —
but the *trap* generalises to anything driven.