AP-034: enforce Auths release identity

[bordumb]

Summary

Implements AP34-PR4 as the release-identity and stale-name enforcement unit.

• makes auths-v<version> the only accepted release tag shape;
• changes hosted release artifact and generated schema identities from repository-scoped names to Auths product names;
• validates the authoritative naming inventory, all 33 predecessor dispositions, the 28-crate closure, and nine topological publication tiers;
• rejects legacy public coordinates and current Auths Proof product headings outside exact justified historical allowances;
• binds release workflow, npm, Python, Rust roots, artifact families, and semantic-freeze metadata to the inventory.

Tests and evidence

• cargo xtask public-naming: passed with 23 surfaces, 33 predecessor crates, and 9 publication tiers.
• Focused public-naming tests: 3 passed.
• Focused release-tag acceptance and rejection tests: 3 passed.
• Formal translation source closure: passed at deeaa08cb05e8b456b3f72dc0d01d281bb59815006db6ac4e04aa79f3abdfc08.
• Architecture DOT matches the JSON generator output byte-for-byte.
• Semantic-freeze Rust roots, ordering, and all frozen owner digests match.
• Hosted CI remains authoritative for the full repository suite.

Affected claims

• Public product identity is Auths.
• First-RC tag identity is auths-v1.0.0-rc.1 after the workspace version is promoted by the separately governed release-candidate work.
• Public Rust roots are auths and auths-sdk.
• Public language packages are @auths-dev/sdk and auths.
• auths-proof remains valid only for the bounded proof component and literal temporary repository or provenance coordinates.

Exclusions

This PR creates no tag, release, package, artifact publication, attestation, deployment, DNS change, repository rename, archive, yank, or registry owner change. It does not claim AP-SPEC-032 or any external release gate has passed.

Remaining gates

• Green hosted CI for AP34-PR4.
• Accurate predecessor-repository notice and migration or deferral ledger in AP34-PR5.
• auths.dev content alignment in AP34-PR6.
• Rebase and regenerate AP-SPEC-032 release evidence after all AP-SPEC-034 gates pass.
• Explicit owner authorization remains required for any tag creation or publication.

Closes no issue until every AP-SPEC-034 bounded unit and external naming gate is complete.