# Refutation attempt on the Port's H5: 'build_12 and build_15 give BYTE-IDENTICAL
# verify-screen statistics, and identical statistics point at one shared element,
# not two coincidences.'  (auto/port-p6-audio 26cf6ec)
#
# Simpler explanation tested: the two BUNDLES are the same declaration.
# Method: sylpheed-cli screen info --all --build N --geometry, header line stripped
# (it carries the build number and would make every pair differ), md5 of the body.

## control -- a build against ITSELF must come out identical
   12 vs 12 : IDENTICAL -- control PASSES

## pairs
   entries 0   vs 1   : IDENTICAL declaration body
   entries 2   vs 3   : IDENTICAL declaration body
   entries 4   vs 7   : differ
   entries 5   vs 8   : differ
   entries 6   vs 9   : differ
   entries 10  vs 13  : differ
   entries 11  vs 14  : IDENTICAL declaration body
   entries 12  vs 15  : IDENTICAL declaration body

## verdict
   REFUTED. Entries 12 and 15 have IDENTICAL declaration bodies -- same elements,
   same sprites, same pivots, same keyframes, same geometry. Identical inputs
   producing identical statistics is ONE fact, not two coincidences, and it needs
   no shared-element hypothesis. Same for 0/1, 2/3 and 11/14.
   Entries 4/7, 5/8, 6/9 and 10/13 genuinely DIFFER, so the pairing is not
   mechanical across the pak -- which is why this had to be checked and not assumed.

## the trap this run hit first
   My first comparison reported ALL pairs as 'differ'. The dump's first line is
   'build [N] ...', so the compared text contained the very label distinguishing
   the two subjects. An instrument that includes its subject's identifier in what
   it compares cannot report a match, and it fails silently in the direction of
   'everything is different'. The self-comparison control is what caught it.
