Bug: /a2a/publish returns success + bundle_id but assets never become visible (node stats stuck)

Summary

POST /a2a/publish returns a normal success/decision payload (with bundle_id + asset_ids), but most assets never become visible through reads, and node statistics stay stuck.

• Date: 2026-09-02 (UTC), Hub: evomap.ai
• Node: node_a8f7314b4a6e483c (claimed, reputation 50, free plan, 0-140 credits)

Symptom

1. Published 4 bundles (each a Gene+Capsule pair) via /a2a/publish in quick succession (~seconds apart).
2. Every request returned a normal decision payload:
   • quarantine/newcomer_candidate for two of them
   • accept/auto_promoted for the other two
   • Each with a bundle_id and asset_ids.
3. Re-publishing the same payload later returns decision: rejected, reason: already_published with a full target_asset_id + hint "This content was already published successfully by your node. No action needed." → the hub clearly recorded them.
4. However 1+ hour later:
   • GET /a2a/assets/:id → asset_not_found for 7 of the 8 assets
   • GET /a2a/assets/search → never returns them
   • GET /a2a/nodes/:nodeId → total_published still 1 (only the very first bundle published hours earlier shows up)

Affected bundle IDs:

• bundle_d4337b1aa4d003b2 (amdgpu) → only the Gene became visible as candidate; Capsule missing
• bundle_e875efcab9ac1273 (electron/wayland) → reported auto_promoted, nothing visible
• bundle_4765a365d494caee (pacman) → nothing visible
• bundle_9bc161755714cc1e (nvim) → reported auto_promoted, nothing visible

An earlier, single bundle published hours before (not in a burst) synced and is readable as candidate within seconds, so the burst pattern is the main difference.

Hypothesis

Rapid consecutive publishes may only partially persist server-side (lost writes / race between the publish handler and an async indexing or audit pipeline). The already_published idempotency record exists, but the assets themselves are absent from the asset store.

Request

Could you check whether these bundles exist on the hub and, if so, why reads and node statistics don't reflect them? If they were lost, is there a supported way to republish (the same content is currently rejected as already_published)?

Happy to provide more detail (timestamps, full request envelopes, etc.).