Upstream sweep 2026-07-22: ant-sdk and ant-node metadata refresh

[JimCollinson]

Daily upstream-drift sweep. Both audited ranges classified metadata-only; this is a stamp refresh, no prose.

Upstream

• ant-sdk: d1f3cb03 → 71c84b90 (PR #224)
• ant-node: 1b04edd1 → eb74b564 (PR #176)

Source artifacts inspected

• ant-sdk: ffi/README.md, ffi/rust/ant-ffi/src/{lib.rs,client.rs,data.rs,payments.rs}, .github/workflows/ffi-ci.yml, and repo Cargo.toml; cross-checked against the docs language-binding, REST/gRPC, daemon-command, and MCP pages.
• ant-node: docs/adr/ADR-0006-receiver-side-revenue-floor.md, src/payment/{verifier.rs,quote.rs,mod.rs}, src/{node.rs,devnet.rs}, src/replication/*, src/storage/handler.rs, and repo Cargo.toml; cross-checked against docs/core-concepts/payment-model.md and docs/rust/embed-a-node-in-your-application.md.

Developer-facing change

Internal refactor; no developer-facing impact on any documented surface.

• ant-sdk: the diff is confined to the ffi/ mobile C-ABI layer and its packaging CI (renamed/added FFI methods such as connect_default*, an optional data_dir, _with_progress file variants, an ant_ffi_version free function, and a TxKind enum on external-signer transactions). The docs document the daemon REST/gRPC clients (AntdClient), MCP, CLI, and Rust libraries — not the ant-ffi C ABI. The antd daemon, OpenAPI spec, gRPC proto, and CLI surfaces are untouched in this range.
• ant-node: a receiver-side revenue floor (ADR-0006, Proposed) on single-node store admissions — shadow-mode by default and enabled per node through the ANT_PRICE_FLOOR_ENFORCE / ANT_PRICE_FLOOR_TOLERANCE_PERCENT environment variables. No page documents node payment-verifier configuration or these environment variables; the payment-model statement that nodes verify the payment proof on receipt remains accurate.

Files changed in this PR

• 49 docs pages: source_commit and verified_date refreshed inside the drifted <!-- verification: --> blocks only. Non-drifted blocks (ant-client, evmlib, self_encryption, ant-protocol) left byte-identical.
• skills/start/version.json: verified_commits values for ant-sdk and ant-node (key set unchanged).
• skills/start/SKILL.md: frontmatter verified_commits for ant-sdk/ant-node and the verified_date line. Body, version, published_date, and CHANGELOG.md unchanged.
• planning/sweeps/2026-07-22.md: new per-run summary.

Verification run

• python3 scripts/sweep_poll.py re-run on the prepared branch: status: "ok", 0 drifted records, no malformed-block errors.
• version.json re-parsed as valid JSON; SKILL.md frontmatter re-parsed as YAML — version unchanged (body byte-identical, so no linked release), verified_date and verified_commits updated.
• Diff audited line-by-line: only source_commit:, verified_date:, and skill verified_commits/verified_date lines changed — no prose, no scripts/, .github/, or registry files.
• markdownlint / link-check: skipped — not configured in this environment.

Uncertainties

The ant-node crate Cargo.toml reads 0.14.4 at both SHAs while docs/rust/embed-a-node-in-your-application.md pins ant-node = "0.11.0". That is pre-existing (the version did not move in this range) and plausibly correct under the current-merged-truth installation rule if crates.io publishes 0.11.0, so it is out of this sweep's scope and left unchanged — flagged here only for a reviewer to confirm the published crate version.

---

Generated by Claude Code