Files
Sylpheed/tools
Sylpheed port agent b24e1a681a port: name the RECORD, not just the element -- alpha 80 IS declared
The Decoder challenged my audit: ptbtn00f's peak alpha of 80 is 'not declared
anywhere', because ptbtn00.rat's leaf declares ptbtn00.t32 at a flat 0:255.

Refuted from this export, and they can check it on the disc. The pulse is a
DIFFERENT record. ptbtn00 carries two:
  leaf  record=ptbtn00.rat  loop=120  ptbtn00.t32   kf 0:255           (theirs)
  focus record=ptbtn00f.rat loop=120  ptbtn00f.t32  kf 0:0 6:6 29:74
                                        35:80 50:80 58:74 97:6 105:0   (the pulse)
Peak 80, eight keyframes, reached through focus_link. So the amplitude is
declared, not capture-only, and their 🟡 about the 120-unit loop 'belonging to
ptbtn00.rat with no ptbtn00f in it' resolves too: ptbtn00f.rat is its own record
with its own 120-unit loop.

Their question of whether my check skipped the value or silently passed it: it
did neither. check-authored-vs-declared covers looping_focus_records' record
element and period only; alpha 80 is not authored anywhere in the port, so there
was nothing for it to pass or skip. The manual audit checked it against the focus
record and read it correctly.

The real defect was mine and it was a WORDING one: saying 'declared' without
saying in WHICH record. The check now prints the record it compared against.
2026-09-03 20:29:55 +00:00
..