Strip the two additive IMP-94 attributes (data-region-id,
data-content-unit-id) symmetrically at both the 89-a fixture capture
script and the b4 mapper source SHA parity test before SHA-256 hashing,
honoring the issue body guardrail "mdx 01-05 의 final.html SHA =
byte-equivalent except for new data-* attrs" without recapturing the
pre-89-a baseline. The strip regex is anchored on the leading-space +
attr-token shape emitted by src/region_marker_stamper.py:131-135 so the
#96 data-frame-slot-id axis stays disjoint.
The marker-parity cross-axis tests for emergency_p4b_verbatim_code and
emergency_p4_ai_inline append sites are converted from pytest.skip to
vacuous-truth early return when the Emergency P4/P4b anchors are absent
in HEAD — the assertion target does not exist in IMP-94 scope, but the
contract still locks placement_markers=[] when the Emergency axis lands
later. Refreshed 89a_pre_baseline_sha.json (2026-05-27T04:19:30Z) holds
the normalized sizes/SHAs for mdx 01-05 post-stamper.
Scope: regression harness + fixture only; zero src/ edits. Verified
35/35 marker-parity + 18/18 SHA parity in a clean detached worktree at
HEAD 2afedfc with these four files applied.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
kyeongmin
6e9e3ee1fb