Round 2 reviewed the round-1 fix commit and returned 12 findings. The pattern was
that the CORRECTIONS were themselves new claims, and inherited the same defect they
were fixing.
Two were the same class as round 1, reintroduced by the fix:
* "the pull_request_target half IS re-measured at 1.27.1" was unsourced. That
record's only 1.27.1 datum is a timeline-endpoint measurement on PR #752; every
overlap/serialization probe in it is 1.25.4-era (PR #722, runs 7520/7521,
7528/7529). #747 did not re-measure it - now says so, in both copies
* replacing "no longer observable" with "can only arise from two merges to main"
substituted a new closed set that forgets a ref class: docker-build.yml also
triggers on `v*` tag pushes, which are outside main's branch protection. The
honest statement is that the cheap disposable-scratch-branch probe is gone, not
that the event cannot occur
Control bound to the right arm: the mechanics field attached "posting the context ->
200" immediately after arm B's force-merge 405, so it read as controlling that. The
control was run on PR #863's ORDINARY merge. Arm B's force-merge 405 has no control,
and the record now says so.
Ordinary-merge arm pinned to its field value: it ran on scratch/747-base with
block_admin_merge_override at its false default, which is what makes the claim
well-defined - absence blocks an ordinary merge WITHOUT needing the override field;
the field governs the force path only (arm A false -> merged, arm B true -> refused).
The heading no longer asserts "only the override field blocks a FORCED one" as a
general mechanism.
Incomplete fixes completed:
* the cancel-route record's TITLE still claimed 1.27.1 for the MCP and web-UI legs
the body had just marked un-re-run; title and its workflow-process.md index copy
now scope the re-probe to the REST route
* pr-changed-files.sh's parenthetical governed a compound sentence including the
`--depth=1` merge-base clause, which was never re-probed; now split
Also: artifact inventory reconciled (four scratch bases - one ordinary-merge pair plus
three force-merge arms - not "a pair per arm", which implied four arms); the
gate-trigger caveat moved out of the middle of a four-item enumeration it had broken;
a dangling "the 1.25.4-dated note" correcting a belief about a sentence this change
itself deleted; and two negative universals softened to what was observed.
Refs: #747
Decisions-Edit: yes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>