feat: migrate-publish-datamaps via antd 0.7.0 external-signer chunks

[Nic-dorman]

Summary

Adds cmd/migrate-publish-datamaps, an operator binary that walks completed private uploads carrying a locally-stored DataMap and back-publishes each one as a single on-network chunk via antd's new external-signer chunk surface (POST /v1/chunks/prepare + POST /v1/chunks/finalize, shipped in ant-sdk v0.7.0). After it runs, downstream consumers can fetch each file directly via autonomi://<addr> instead of proxying through indelible.

Payment flows through indelible's existing wallet (WalletService.GetDefault → DecryptKey → evm.Signer.PayForQuotes) — the same path the upload worker uses for normal file uploads. No daemon-wallet provisioning, no env wrangling, no special key handling.

Concrete trigger: PROD-01 has ~78 completed-private uploads (the foundations corpus from 2026-05-06) that pre-date public visibility. Migrating them lets pub-library drop the indelible proxy for those papers.

Surface

• internal/migrate/publish_datamaps.go — testable migrator with two decoupled interfaces (ChunkPublisher for antd-go, EvmPayer for evm.Signer), JSONLines progress, --dry-run / --limit / --uuid / --verify flags, idempotent "already on network" exit that doesn't re-pay.
• cmd/migrate-publish-datamaps/main.go — thin wrapper: loads indelible.toml, opens the existing SQLite, resolves the default wallet, wires antd-go + evm.Signer, handles graceful SIGINT.
• services.UploadService.MarkPublished / ListPrivatePublishCandidates — small additions. data_map is preserved on the migrated row; the download handler (internal/handlers/uploads.go) prefers data_map over datamap_address when both are populated, so the row stays downloadable through indelible's existing API either way.

ant-sdk dep bump

• github.com/WithAutonomi/ant-sdk/antd-go: v0.6.1 → v0.7.0 (adds PrepareChunkUpload / FinalizeChunkUpload).

Operational note

The migration binary calls /v1/chunks/prepare and /v1/chunks/finalize on the antd daemon indelible manages. PROD-01's antd must be upgraded from v0.6.1 → v0.7.0 before this binary will work — the new endpoints don't exist on older daemons. Drop the v0.7.0 binary at /usr/local/bin/antd (from the ant-sdk release page, antd-linux-amd64) and restart indelible.service; ~30s outage.

Test plan

• go test ./... clean — handlers, worker, services, migrate, etc.
• Migration unit tests cover:
  • Happy path: rows flip to visibility='public' with correct datamap_address, with correct prepare/pay/finalize call sequencing
  • Already-on-network skip: no payment, no finalize, but row still flips to public
  • Dry-run: no network calls, no row mutations
  • Generic prepare error: one row fails, the rest proceed
  • Verify mismatch: row stays private when ChunkGet returns different bytes than were sent
  • --limit + --uuid filters
  • Bad-hex data_map skip (per-row failure, no network call)
• End-to-end smoke verified against Arbitrum One mainnet at the SDK layer (ant-sdk#61 discussion): 256-byte payload round-tripped via prepare → payForQuotes (external wallet) → finalize → ChunkGet with full byte equality.
• Operator (post-merge):
  1. Drop antd v0.7.0 binary on PROD-01, restart indelible (~30s outage).
  2. make migrate-publish-datamaps-linux, scp to PROD-01.
  3. ./migrate-publish-datamaps-linux-amd64 --config /opt/indelible/indelible.toml --dry-run → confirm candidate count.
  4. Run for real; verify a few /api/v2/uploads/{uuid} responses now report datamap_address.

🤖 Generated with Claude Code