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

docs: close the focused-state question against the declaration table, and log a third freeze-free run

Browse Source 
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE
This commit is contained in:
Sylpheed RE agent
2026-08-24 03:50:58 +00:00
parent afc37df459
commit 09a51b01cf
1 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/re/BACKLOG.md
View File

@@ -189,9 +189,14 @@ See [`structures/ui-composable-bundles.md`](structures/ui-composable-bundles.md)
title capture cannot separate the two — its resting elements are all
`0xffffff`. A screen with a coloured primitive, captured, would.
* ❔ **What marks a focused state in the file.** The pairing rule that shipped is
a naming convention, not a decoded field. `kind = 0x3002` is a button record;
whether a bit of `kind` marks the focused variant is the cheapest probe.
* 🔴 **What marks a focused state in the file — NOT the declaration entry**
(2026-08-24). Swept disc-wide and asserted: **54** name-paired focused/base
pairs, **all 54** with identical `kind` (all `0x0`), **no** bit ever set on the
focused entry and clear on its base, and the only words of the 60-byte entry
that ever differ are **`+48`/`+52`, the pivot**. The naming pairing is not
standing in for a field — there is no field.
❔ Still open: the `.rat` record, the RATC child stream, or the game's code.
See [`structures/ui-rat-layout.md`](structures/ui-rat-layout.md).
* ❔ **What makes a bundle a screen rather than a fragment.** `is_composable`
admits 1 786 extra bundles, mostly 2–5-element button+glow fragments.
* ❔ **What `opt ` links.** Refuted as focus; unexplained otherwise.
@@ -337,7 +342,10 @@ is what the autopilot needs in order to CHOOSE a target. One run in:
freeze (the control is therefore measured twice: 27 and 24 lines, same single
pair), and the earlier freezes came in a cluster — so this is a ~30-minute
lottery per run rather than a dependable step. `freeze_watch.sh` waits for one
unattended and snapshots the probe at the moment it lands. `frozen.py` detects the state in one call; `ob_hunt.py` /
unattended and snapshots the probe at the moment it lands. **Three** runs in a
row have now failed to freeze (the third ended in GAME OVER), and the probe's
healthy control is measured three times — 27, 24 and 36 lines, always the same
single pair. `frozen.py` detects the state in one call; `ob_hunt.py` /
`ob_flag.py` abort on it. **Roughly two runs in three.**
See [`mission-freeze-resume-spin.md`](mission-freeze-resume-spin.md).