GitNexus/gitnexus/test/fixtures/ruby-captures-golden
Gergo Magyar e718eebca0 test(golden): regenerate capture goldens for wire format v2 (#2766)
Follow-up to the codec v2 commit, which was incomplete: the VERSION
prefix is part of every emitted `@reference.receiver-chain` capture, so
the committed golden snapshots drifted for exactly the languages that
mint chains. I verified that commit with targeted unit tests rather than
the full unit suite, so the goldens were not in the set I ran.

Regenerated with UPDATE_GOLDEN=1. Two distinct causes in the diff:

- csharp, php, python, ruby, rust, swift — pure `1|…` -> `2|…` prefix
  rewrites. Entry counts unchanged, which is what shows this is a
  spelling change and not a capture-set change.
- go — 100 -> 102 entries, the two files added by the pointer-receiver
  regression fixture, plus the same prefix rewrite.

Also bumps the v1 payloads in the fold unit tests, which decode through
the same codec and so refused every chain under v2.

Full scope-resolution unit suite green: 90 files, 1371 tests.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-01 16:28:29 +00:00
..
expected-captures.json test(golden): regenerate capture goldens for wire format v2 (#2766) 2026-08-01 16:28:29 +00:00