[bug]: transfer proof stuck PENDING, listAssets zero

Description

Environment

• Node: mcu-616-main (Voltage)
• TAPD Version: 0.7.0-alpha
• TAPD REST: https://xxxx.m.voltageapp.io:443
• Chain: sync_to_chain=true, block_height in sync

Issue
One outbound Taproot Assets transfer has been confirmed on-chain for over 4 hours. In ListTransfers, one output (the one to the recipient) still shows
proof_delivery_status = PROOF_DELIVERY_STATUS_PENDING. As a result, getMcu616Balance() (and thus listAssets for that asset) returns 0, and we cannot send new asset batches for orders.

Self-check (via TAPD REST)

• Universe federation: 1 server — universe.lightning.finance:10029
  (default mainnet Universe present).
• Universe sync config (GET /v1/taproot-assets/universe/sync/config):
  • PROOF_TYPE_TRANSFER:
    • allow_sync_insert=false
    • allow_sync_export=true
  • PROOF_TYPE_ISSUANCE:
    • allow_sync_insert=false
    • allow_sync_export=true

The node exports proofs to the federation but does not insert (pull) proofs from it. We suspect this is why the transfer output never leaves PENDING and our balance stays zero.

Request
Please enable allow_sync_insert for PROOF_TYPE_TRANSFER (or the equivalent setting on your side) so that this node can pull transfer proofs from the federation and the delivery status can move to COMPLETE. If your default policy is to keep insert disabled, we would like to understand the recommended way to resolve persistent PENDING and zero listAssets after a chain-confirmed transfer.

Recipient Address (for Reference)
The pending output is for this MCU616 address (decoded successfully, asset_id and amount match):
tapbc1qqqszqspqqzzp0nudneszexrnu3k7f7qla59u9mlkfkfz26hsln2e2l40z853n3zqcssyuzuqygr965m0pahjqxuknee3kvdhvfpjlux6aut8rvw3zevst4ppqssxz4mcx29d3teh37m2lcv9rhzjd0kde656t0utrdqau4rx670rzulpgyl7qqqgsvrwupyqqxzuatwd9mx2unnv4e8qce69uhh2mnfwejhyum99ekxjemgw3hxjmn89enxjmnpde3k2w33xqcrywgdvsptt

Thank you.