docs: antd v0.6.1 — health fields, upload visibility, MCP port discovery

[JimCollinson]

Upstream

• ant-sdk: d7652ec3 → 529280c3 (chore(antd): release v0.6.1)
• ant-client: 71ad53b0 → 6cada1d6 (merge rc-2026.4.4)
• ant-node: 23aee15c → 0c2f2c97 (merge rc-2026.5.1, payment verifier clock skew — internal only)
• ant-protocol: 65651f3a → 8955144b (merge rc-2026.4.4, Cargo.lock only — metadata-only)

Source artifacts inspected

• antd/openapi.yaml — primary REST API spec
• antd/proto/antd/v1/health.proto — gRPC HealthCheckResponse
• antd/src/types.rs — PrepareUploadRequest, PrepareDataUploadRequest, FinalizeUploadResponse, HealthResponse
• antd/src/main.rs — EVM/build-commit fields wired into AppState
• antd-mcp/src/antd_mcp/discover.py — port-file path changed to ant/sdk/daemon.port
• antd-mcp/src/antd_mcp/server.py — check_health() now surfaces all six new fields
• ant-core/src/data/client/data.rs — new data_prepare_upload_with_visibility method
• ant-core/src/data/client/file.rs — Visibility enum (Public/Private)
• ant-core/src/data/mod.rs — pub use client::file::Visibility confirmed

Developer-facing change

antd v0.6.1 introduces four breaking additions to the REST and gRPC health surface, a new upload visibility parameter, and a corrected MCP port-file discovery path:

1. GET /health and HealthCheckResponse now return six new required fields: version, evm_network, uptime_seconds, build_commit, payment_token_address, payment_vault_address.
2. POST /v1/upload/prepare accepts a new optional visibility field ("private" | "public"). Public uploads bundle the DataMap chunk into the payment batch; finalize returns data_map_address.
3. POST /v1/data/prepare accepts visibility but returns 501 for "public" (blocked on ant-core upstream PR #73). Use /v1/upload/prepare for public external-signer uploads today.
4. antd-mcp now reads the port file from ant/sdk/daemon.port (matching where antd writes it); the previous mismatch note is corrected.
5. ant-core gains data_prepare_upload_with_visibility(content, Visibility) and the Visibility enum as public API.

Files changed in this PR

• docs/sdk/reference/rest-api.md — health response, visibility param on prepare endpoints, data_map_address on finalize, 501 error code
• docs/sdk/reference/grpc-services.md — HealthCheckResponse fields, Common messages table
• docs/sdk/how-to-guides/use-external-signers-for-upload-payments.md — visibility param, data_map_address on finalize, data_prepare_upload_with_visibility for Rust callers
• docs/mcp/mcp-server-reference.md — port-file discovery corrected, check_health() response updated
• docs/rust/library-reference.md — Visibility type in key types table, data_prepare_upload_with_visibility in external signer section
• skills/start/SKILL.md — health shape updated, MCP discovery claim corrected; frontmatter bumped 0.1.3-draft → 0.1.4-draft
• skills/start/version.json — version 0.1.4-draft, published_date 2026-05-11, verified_commits updated
• skills/start/CHANGELOG.md — 0.1.4-draft entry added
• planning/sweeps/2026-05-11-prose.md — sweep summary added

Why prose changed

• rest-api.md: The GET /health response shape changed — six new required fields exist at 529280c3 in antd/openapi.yaml and antd/src/types.rs:HealthResponse. The prepare endpoints have a new visibility field. The finalize response has data_map_address.
• grpc-services.md: antd/proto/antd/v1/health.proto at 529280c3 adds six new fields to HealthCheckResponse.
• use-external-signers-for-upload-payments.md: Visibility is now a valid prepare parameter for file uploads, and finalize returns data_map_address. The ant-core native path has a new data_prepare_upload_with_visibility method.
• mcp-server-reference.md: antd-mcp/src/antd_mcp/discover.py at 529280c3 switched from ant/daemon.port to ant/sdk/daemon.port, matching antd's write path. The check_health() server function now returns all six new health fields.
• library-reference.md: ant-core/src/data/mod.rs at 6cada1d6 now pub uses Visibility from client::file. data_prepare_upload_with_visibility is a new public method on Client.
• SKILL.md body: Health shape was stale; MCP discovery claim was factually wrong after the port-file path alignment.

Linked skill release

SKILL.md body changed → linked release applies per planning/routines/upstream-sweep.md:

• version.json: version 0.1.3-draft → 0.1.4-draft
• version.json: published_date 2026-05-02 → 2026-05-11
• SKILL.md frontmatter version: 0.1.3-draft → 0.1.4-draft
• SKILL.md frontmatter verified_date: 2026-05-02 → 2026-05-11
• CHANGELOG.md entry added for 0.1.4-draft

Verification run

• Scanner (python3 scripts/sweep_poll.py) re-run on prose branch: status: "ok", 0 drifted records on the 6 prose pages. Remaining 14 drifted records are all in the companion sweep PR, correct by design.
• JSON (python3 -m json.tool skills/start/version.json): valid
• Linked-release rule confirmed: SKILL.md body changed ↔ version, published_date, frontmatter version, verified_date, and CHANGELOG all updated
• Endpoint/type re-grep against pinned upstream checkouts confirms: HealthResponse struct has all 6 new fields at 529280c32c024c92b68436abb6ace956c8da66ba; Visibility is re-exported from ant_core::data at 6cada1d6b318a93e52ea6c34aa4b68fc2782c946; antd-mcp/discover.py uses ant/sdk/ path at 529280c32c024c92b68436abb6ace956c8da66ba

Uncertainties

• The 501 note on POST /v1/data/prepare with visibility:"public" references ant-client PR #73. That PR is not merged as of the audit. The page correctly documents the current (501) behavior and directs users to /v1/upload/prepare instead.
• Reviewer should confirm the data_map_address description in rest-api.md matches the intent in antd/src/rest/upload.rs (not audited in full detail — inferred from types.rs and openapi.yaml).

---

Generated by Claude Code