fix: make release-v441 publication merge-ready

[UnArbosFive]

Summary

• restore the mainnet watcher content-verification path
• skip redundant SDK release candidates through a tested PyPI-state planner
• refresh the SDK lockfile, Python formatting, raw-call coverage, and generated docs
• keep the claim-root weight assertion lint-clean without a function-wide exemption

Why

The release train must preserve exact stable-artifact verification while avoiding RC publication after both stable Python package bases already exist. This consolidates the release quality-gate fixes into one merge-ready change targeting release-v441.

The planner publishes only when both bases are available, skips only when both are published, and fails closed for mixed or indeterminate PyPI state.

Verification

• Python RC planner unit tests: 6 passed
• exact live PyPI planning command: passed
• workflow YAML parse: passed
• uv sync --python 3.14 --locked --all-extras --dev: passed
• Ruff check and format check: passed
• ty check: passed with no errors
• SDK tests: 984 passed, 1 skipped
• SDK codegen coverage and name checks: passed
• generated docs drift check: passed
• uv lock --check: passed
• cargo fmt --all -- --check: passed
• focused runtime Clippy with -D warnings: passed
• focused claim-root weight test: passed
• git diff --check: passed

Scope

This PR supersedes #2996 by including its lockfile correction and the remaining release quality-gate fixes.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
subtensor	Ready	Preview, Comment	Jul 27, 2026 3:04pm

[github-actions]

🛡️ AI Review — Skeptic (security review)

VERDICT: SAFE

VERY HIGH account-age scrutiny, mitigated by repository admin permission and substantial merged work; no Gittensor association found. Branch: fix/skip-unchanged-sdk-rc → release-v441.

Static analysis found the release-workflow changes consistent with the stated behavior. RC publication skips only when both stable package bases exist and fails closed on mixed or indeterminate PyPI state. The PR does not alter AI-review trust instructions, runtime behavior, dependency sources, credential permissions, or author/committer identity.

Findings

No findings.

Conclusion

No malicious behavior or security vulnerability was found in the PR-specific changes.

---

🔍 AI Review — Auditor (domain review)

VERDICT: 👍

UNKNOWN Gittensor association; very new account, but repository admin with substantial recent merged contributions. Maximum code scrutiny applied.

The implementation matches the description: RC publication occurs only when both stable bases are absent, skips when both exist, and fails closed on mixed or indeterminate PyPI state. The mainnet watcher’s immutable artifact-verification path is restored, generated SDK/docs updates are consistent, and the targeted planner tests plus git diff --check passed.

This PR is the better candidate. Recommend closing #2996. It includes #2996’s quality-gate fixes together with the tested RC planner and associated lockfile/documentation updates. PR #2994 is the intended parent integration branch; the other file overlaps are unrelated generated documentation or release-line changes.

Findings

No findings.

Conclusion

The release workflow is internally consistent, tested, and preserves stable-artifact verification while correctly skipping redundant SDK release candidates.

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍