feat(antd): wire visibility through /v1/upload/prepare

[Nic-dorman]

Summary

Wires visibility through /v1/upload/prepare and surfaces the bundled-DataMap address on /v1/upload/finalize. Bumps antd to 0.6.1.

The file-path side is fully unblocked against the pinned ant-cli-v0.2.2. The in-memory /v1/data/prepare side returns 501 for visibility:"public" until upstream data_prepare_upload_with_visibility merges; once it does, that 501 path flips to a real call (no other changes needed in this PR's footprint).

Mainnet validation (2026-05-06)

End-to-end external-signer wave-batch public upload validated on Arbitrum One mainnet against this branch (rebased on top of v0.6.0):

• 10 KB test file → 3 data chunks. Public prepare returned 4 payments (private control returned 3) — DataMap chunk bundled into the same PaymentIntent.
• Cost scaled proportionally: 0.0352 ANT private → 0.0469 ANT public (4/3 ratio, DataMap priced as one chunk).
• ERC-20 approve tx + single payForQuotes tx covering all 4 quotes — atomic external-signer payment.
• /v1/upload/finalize returned data_map_address populated; chunks_stored=4 matched the bundled payment count.
• /v1/files/download/public {address: data_map_address} round-tripped the file byte-for-byte (SHA256 match).

Behavior

Caller	Before	After
/v1/upload/prepare {path}	private prepare	unchanged (omitting visibility is implicitly private)
/v1/upload/prepare {path, visibility:"public"}	(field ignored, private prepare)	public prepare — DataMap chunk bundled into the same PreparedUpload payment batch
/v1/upload/finalize	returns {data_map, address?, chunks_stored}	also returns data_map_address? when prepare was public
/v1/data/prepare {data, visibility:"public"}	private prepare	501 until data_prepare_upload_with_visibility is exposed upstream
Any caller passing store_data_map: true	unchanged	unchanged — legacy path honored, paid by daemon wallet

Files

• antd/src/types.rs:
  • PrepareUploadRequest, PrepareDataUploadRequest: optional visibility: Option<String>
  • FinalizeUploadResponse: optional data_map_address: Option<String> (skipped from JSON when None — old clients see no new fields)
  • New helper parse_visibility(Option<&str>) -> Result<ant_core::data::Visibility, String>
  • 7 new unit tests
• antd/src/rest/upload.rs:
  • prepare_upload now calls file_prepare_upload_with_visibility instead of file_prepare_upload
  • prepare_data_upload returns AntdError::NotImplemented (501) when caller asks for visibility:"public"
  • finalize_upload threads result.data_map_address through to the response (both wave-batch and merkle branches)
• antd/openapi.yaml: documents the new visibility field on both prepare requests, the new data_map_address on the finalize response, the 501 case on /v1/data/prepare
• antd/Cargo.toml: 0.6.0 → 0.6.1

Wire-compat

• proto3-style: all new fields are Option<String> with serde-default. Old clients that don't send visibility get private behavior. New clients talking to an old daemon (pre-0.6.1) get the field silently ignored — same private behavior as before — and data_map_address will be absent in the response (the new field is omitempty).
• The legacy store_data_map: bool field is kept and still honored so existing callers don't break. New callers should prefer visibility:"public" instead.

Test plan

• cargo test — 26 pass (visibility serde round-trip, parser accept/reject, finalize response serialization with/without data_map_address)
• End-to-end mainnet validation as above

Follow-ups

• antd-go SDK consumer (feat(antd-go): PrepareUploadPublic + DataMapAddress #58)
• antd-py SDK consumer (feat(antd-py): prepare_upload_public + data_map_address #59)
• The other 13 SDKs — mirror the same pattern (cpp/csharp/dart/elixir/java/js/kotlin/lua/mcp/php/ruby/rust/swift/zig)
• Flip the 501 — once the upstream data_prepare_upload_with_visibility lands and antd's pin bumps, replace the early-return in prepare_data_upload with a real call.

🤖 Generated with Claude Code