Fix production SDK call metadata drift

[UnArbosFive]

Summary

• regenerate the SDK call catalog from the release-v438 production node metadata
• remove the feature-gated faucet call, which is absent from production builds
• keep the raw-call coverage catalog aligned with the production call surface

Verification

• python -m codegen.check --drift passes against the exact release node artifact
• python -m codegen.check --coverage passes (249 calls covered)
• python -m codegen.check --names passes

[vercel]

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

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

[github-actions]

🛡️ AI Review — Skeptic (security review)

VERDICT: SAFE

VERY HIGH account-signal scrutiny (0 public repos), mitigated by repository admin status and substantive merged history; no Gittensor association found. Branch: fix-release-clone-sdk-drift → release-v438.

Findings

No findings.

Conclusion

The small, mechanical diff removes a test-only faucet call from the production SDK catalog and its coverage exemption. It introduces no executable, runtime, dependency, CI, or trust-boundary changes and no security vulnerability was found.

---

🔍 AI Review — Auditor (domain review)

VERDICT: 👍

UNKNOWN Gittensor association; newer account, but repository admin with substantial merged contribution history. Maximum external-contributor scrutiny applied.

The patch is a minimal, internally consistent synchronization of the generated Python SDK catalog with the production runtime metadata. Removing faucet from both the generated calls and the raw-only coverage exemption preserves the coverage invariant.

The overlapping PRs address unrelated runtime features and are not duplicates. No runtime code is changed, so no spec_version bump or runtime tests are required. Static inspection was sufficient; no auto-fixes were needed.

Findings

No findings.

Conclusion

The implementation matches the substantive PR description and introduces no domain-correctness, testing, migration, or release-rule issues. Ready to merge.

[github-actions]

🔄 AI review updated — Skeptic: SAFE Auditor: 👍