Re-record VCR cassettes for the v3 line (relaton main fetch behavior)

[ronaldtse]

Re-record VCR cassettes for the relaton v3 line

The v3 line (PR #133) resolves relaton main, whose fetch behavior changed enough that the recorded HTTP interactions no longer match:

VCR::Errors::UnhandledHTTPRequestError (Relaton Fetch relaton fetch calls fetch and return XML / YAML / BibTex, …)

Local runs also re-record some cassettes incidentally (timestamps, edge-cache region IDs — e.g. spec/ieee cassettes) — those should be reverted and only deliberately re-recorded.

Checklist:

• Re-record the relaton Fetch/VCR cassettes against relaton main behavior
• Audit cassettes that local runs mutate (ieee corrigendum/528/1619) — revert and lock
• Keep the 2.x line's cassettes untouched (it tests released-relaton behavior)

[ronaldtse]

Re-record progress (v3 @ cb8ff6e):

• iso_2146.yml re-recorded and pushed — against the v3 index-v2.zip fetch flow, with the zip body sha-verified byte-identical to the live download. It could only be recorded out-of-band with stdlib psych: every dump path inside a relaton process routes through yeptris, and yeptris#168 makes those dumps emit partially-UTF-8-encoded/mangled binary (recorded body came back 1.15 MB vs the real 764 KB zip — +385,290 bytes ≈ one extra byte per high byte — plus raw unparseable octets).
• v3 code fixes pushed: version command drops the relaton-bib line and only prints processor gems that actually exist; the Recognised types expectations now derive from the registry instead of the hardcoded v2 flavor list.

Remaining blockers, all upstream yeptris (the suite cannot even reach the cassette under the rebind):

1. yeptris#167 — Psych::VERSION missing; mechanize 2.14.1's cookie-jar gate NameErrors at require time, killing every Relaton::Db::Registry.instance path.
2. yeptris#168 — dump side fixed out-of-band, but the load side also rejects the core !binary tag (DisallowedClass), so stdlib-recorded cassettes can't replay under yeptris yet.

Checklist: cassette re-record done; ieee-mutation audit clean (no incidental cassette mutations in the tree); 2.x line untouched.

[ronaldtse]

Progress on the v3 line (6ad4910, validated against the relaton v3 branch + yeptris 0.6.14.1):

• The fetch acceptance suite is fully green cold-cache (20/0) — unblocked by yeptris 0.6.14.1's parse fix (the 11 MB ISO index went from ~200s to ~8s; prefix scaling is linear now).
• Ported relaton 05add9456's friendly malformed-identifier message to this branch's fetch_document (Parslet::ParseFailed → "<code>" is not a recognized standards identifier) — without it an unparseable reference was an uncaught pubid error, exit 1.
• Acceptance shell-outs now run bundle exec relaton instead of the ambient binstub, so they exercise this branch's exe regardless of what's installed.

Remaining: the 9 subcommand_collection failures are one root cause and it's upstream — yeptris#180: invalid YAML raises Yeptris::ParseError where stdlib raises Psych::SyntaxError, so read_yaml's rescue Psych::SyntaxError misses and collection ls/get/search crash on non-YAML files instead of skipping them. Once that taxonomy gap closes, the suite should be fully green.

[ronaldtse]

Superseded by #133 — merged into lutaml-integration (v3 line: relaton >= 3.0.0.pre.alpha monogem, moxml/leptris XML + yeptris YAML stack, pubid 2.0.0.pre.alpha.13). Full CI matrix 11/11 green; VCR checklist items landed with the cassette refresh on relaton main (relaton/relaton@54d3a33f).