fix(specs): refresh matcher parity fixture after the 585f492 to d4d4f1c redeploy

[dcccrypto]

parity-check has been failing with [percolator-match] DRIFT DETECTED. The cause is the matcher devnet redeploy on 2026-08-25, not any SDK change: the committed spec still described 585f492 while the matcher moved to d4d4f1c.

This is exactly what the check exists to catch, and it caught it.

The drift is entirely additive

change	from
BatchMatcherCall tag 3 — new	76b7106 batch multi-fill ABI
MATCHER_BATCH_HEADER_LEN 18, MATCHER_BATCH_LEG_LEN 26, MATCHER_BATCH_MAX_LEGS 16 — new	same
insurance_fee_remainder_e6 @ 168 — new	64fa492 BUG-101 remainder carry
_reserved 168 → 176	shifted by the field above

Nothing removed, no tag renumbered, so no existing encoder changes meaning.

Verified locally: [percolator-match] parity OK, suite 1008 passed / 31 skipped.

One thing worth knowing about this check

The other three targets — percolator-prog, percolator-stake, percolator-nft — report cargo run failed in CI and locally, because they have no sdk_parity_fixtures bin. So parity-check currently validates only the matcher. Worth either adding the bin to those repos or being explicit that the check is matcher-only.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NgoNgagkvw7i5SSRC3FJ8D

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 951ebbf7-8cef-4768-b572-0a6c8339bc72

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}