Upstream sweep 2026-07-21: refresh verification SHAs (metadata-only)

[JimCollinson]

Metadata-only stamp refresh. All 40 drifted records across four upstream repos were audited against their pinned head SHAs and classified metadata-only. No prose PR and no manual-review issues were opened.

Upstream

• ant-client: bcab72ae → 9a4d8c4d (PR #153)
• ant-node: 571868a1 → 1b04edd1 (PR #179)
• saorsa-core: d323c462 → b0ee4877 (PR #146)
• saorsa-transport: 95efb84f → d9e1687c (PR #125)

Source artifacts inspected

• ant-core/src/data/error.rs, ant-core/src/data/client/mod.rs, ant-core/src/data/client/data.rs, ant-cli/src/commands/data/chunk.rs (ant-client) at 9a4d8c4d
• src/replication/mod.rs, src/replication/protocol.rs (ant-node) at 1b04edd1
• Cargo.toml, Cargo.lock (saorsa-core at b0ee4877, saorsa-transport at d9e1687c)
• Cross-checked against the recorded docs pages: docs/rust/library-reference.md, docs/cli/command-reference.md, and the multi-repo reference pages.

Developer-facing change

Internal refactor; no developer-facing impact.

• ant-client adds a typed Error::NotFound variant so a well-formed address with nothing stored surfaces as NotFound rather than InvalidData, plus a matching not_found message=… arm in the ant chunk get --all-peers diagnostic summary. No recorded page contradicts this: the Rust error example uses a catch-all arm, the CLI reference documents --all-peers without listing its literal status strings, and the SDK-binding pages that name a NotFound error are sourced from ant-sdk (not in this sweep) and already document it.
• ant-node adds per-peer served-bytes traffic accounting — internal instrumentation and an INFO log line, no documented surface.
• saorsa-core and saorsa-transport are release-only version bumps (Cargo.toml/lock); no recorded page pins a version for either crate.

Files changed in this PR

• 23 docs pages: refreshed source_commit/verified_date in the drifted <!-- verification: --> blocks only. Non-drifted blocks (e.g. saorsa-pqc, self_encryption on the multi-repo reference pages) left byte-identical.
• skills/start/version.json and skills/start/SKILL.md frontmatter: refreshed ant-client/ant-node verified_commits values; SKILL.md frontmatter verified_date updated. Body, version, published_date, and CHANGELOG.md unchanged.
• planning/sweeps/2026-07-21.md: new run summary.

Verification run

• Re-ran python3 scripts/sweep_poll.py on the prepared branch: status: "ok", 0 drifted records, no malformed-block errors.
• skills/start/version.json parses as JSON; SKILL.md frontmatter parses as YAML with version unchanged (0.1.6-draft) — linked-release rule holds (body unchanged, so no release-metadata movement).
• Diff confirmed to touch only verification-block lines and skill verified_commits/verified_date (77 insertions / 77 deletions, no prose).
• markdownlint: skipped — no markdownlint config present in the repo.

Uncertainties

None. The ant-client Error::NotFound variant is real but invisible to the current docs surface (no page enumerates ant-core error variants); if a future page documents ant-core error handling in detail, that would be a prose change rather than a stamp refresh.

---

Generated by Claude Code