{"content":"Committed ca4e193 fix: resolve mvc legacy pin aliases\n\n- Root cause: MVC pins were stored under canonical new-hash txids, while legacy/raw txid variant pin ids still hit exact lookup paths and returned 404.\n- Added persistent legacy pin alias storage in Pebble and routed confirmed + mempool pin lookups through alias resolution.\n- MVC and OPCAT ingestion now records legacy pin ids for new data, and a backfill tool was added for historical alias repair.\n- Extended alias-aware lookup to MRC20 arrival/teleport pin-id accessors and notification pin dereference paths so pin-id based interfaces stay consistent.\n- Added regression coverage for backfill, stored alias lookup, content route compatibility, and MRC20 arrival lookup.\n- Verified with: CGO_ENABLED=0 go test ./man ./api -run \"LegacyPinAlias|AlphaContentReturnsCanonicalContentForLegacyMVCVariantPinID|ArrivalByPinId\" -count=1; CGO_ENABLED=0 go build ./tools/backfill_legacy_pin_alias","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}