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

port: take formats-pin-2026-08-30b and stop owning the +0x08 read

Browse Source 
The tag was cut within the iteration, so screen.rs now calls
ui_layout::loop_length_units and its local RATC guard and byte read are deleted.
One line, as predicted -- and the doc comment promising that deletion is the only
reason a temporary reading did not quietly become permanent.

A pin bump moves the whole crate, not one function, and this pin is recorded
load-bearing, so both commits between the tags were read before taking it:
b5df02a adds the public function, d020845 is comment-only -- two 'fixed code
under an unfixed description' corrections. No behavioural change in either, and
the oracle RMSEs confirm it: main_menu 13.21, extras 13.38, title 14.16, all
identical across the bump.

d020845 is worth noting for what it is. The rest override's comment still claimed
it tested the shifted time reading that the record-layout fix had refuted, and a
continue branch was documented with the pre-fix rule. Both are the same failure
this port hit in spin_period_units: a doc comment describing the rule the body no
longer implements. Three instances now, across two agents and two languages.

examples/record_loop_control.rs deliberately did NOT follow the API. The moment a
control calls the thing it exists to check it stops being a control and becomes
the API tested against itself; the falsifier means something only because the
reading is independent. Re-run at the new pin, unchanged. So the port holds one
copy of this reading instead of two, and it is the copy whose job is to disagree.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
This commit is contained in:
Sylpheed port agent
2026-08-30 21:27:54 +00:00
parent f7fee7a77f
commit edd5af5be5
5 changed files with 57 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
docs/port/DECISIONS.md
View File

@@ -9,7 +9,7 @@ dies, which is what this file is for.
<!-- INDEX: generated by tools/port/index-decisions -- do not hand-edit -->
239 sections. Search this before re-deriving anything.
240 sections. Search this before re-deriving anything.
* [P0 — the exporter, 2026-08-28](#p0--the-exporter-2026-08-28)
* [P1 — Godot draws the screen, 2026-08-28](#p1--godot-draws-the-screen-2026-08-28)
@@ -250,6 +250,7 @@ dies, which is what this file is for.
* [A refutation attempt on the fade numbers — it survives, from a third reader](#a-refutation-attempt-on-the-fade-numbers--it-survives-from-a-third-reader)
* [The walk is checked too, and "only the ring moves" tested against my own renderer](#the-walk-is-checked-too-and-only-the-ring-moves-tested-against-my-own-renderer)
* [The `+0x08` ask came back answered — and is not consumable yet](#the-0x08-ask-came-back-answered--and-is-not-consumable-yet)
* [The pin moves to `formats-pin-2026-08-30b`, and the port stops owning `+0x08`](#the-pin-moves-to-formats-pin-2026-08-30b-and-the-port-stops-owning-0x08)
<!-- /INDEX -->
## P0 — the exporter, 2026-08-28
@@ -12483,3 +12484,38 @@ big-endian read. So the deletion my doc comment promises is a one-line switch.
branch would replace a deliberate pin with an incidental one — and `BLOCKED.md`
already records this pin as load-bearing. **Asked for a tag; keeping the local
read, which is guarded and controlled, until one exists.**
## The pin moves to `formats-pin-2026-08-30b`, and the port stops owning `+0x08`
The tag was cut within the iteration, so the deletion the doc comment promised is
done: `screen.rs` calls `ui_layout::loop_length_units` and its local `RATC` guard
and byte read are **gone**. One line, exactly as predicted — the promise in the
comment is the only reason a temporary reading did not quietly become permanent.
**What the pin actually brings, checked before taking it.** A pin bump moves the
whole crate, not one function, and this one is recorded load-bearing, so the two
commits between the tags were read rather than assumed:
| | |
|---|---|
| `b5df02a` | adds the public `loop_length_units` |
| `d020845` | **comment-only** — two "fixed code under an unfixed description" corrections |
No behavioural change in either. `d020845` is worth noting for what it is: the
`rest` override's stated purpose was retired by the record-layout fix and the
comment still claimed it tested the shifted reading, and a `continue` branch was
documented with the pre-fix rule. **Both are the same failure this port hit in
`spin_period_units` — a doc comment describing the rule the body no longer
implements.** Three instances now, across two agents and two languages.
### 🔴 The control did NOT follow the API, on purpose
`examples/record_loop_control.rs` still reads the raw four bytes. **The moment a
control calls the API it exists to check, it stops being a control and becomes
the API tested against itself.** The falsifier — 0 of 1 781 records declaring
less than their own last pose — means something only because the reading is
independent of the crate's. Re-run at the new pin: unchanged, 7 exact and
`ptbtn00f` the one hold.
📌 So the port now holds **one** copy of this reading instead of two, and it is
the copy whose job is to disagree.