AP-SPEC-032: freeze Phase 7 semantics

[bordumb]

Bounded PR unit

AP-SPEC-032: Semantic-freeze PR only.

This PR establishes the versioned semantic-freeze inventory and its CI validator, fixes the public Rust package catalog, and reserves the collision-free public SDK coordinate auths-proof-sdk. It does not create or publish a release candidate.

What changed

• adds release/semantic-freeze.json with 42 versioned entries across frozen meaning, frozen bytes, and release metadata;
• adds cargo xtask semantic-freeze and makes it part of the authoritative CI gate;
• rejects owner-path escape, missing/symlink owners, duplicate identities, same-version semantic or byte drift, and inventory changes without a global freeze-version bump;
• derives all implemented bounded-domain source owners from the domain registry while preserving vertical domain ownership;
• fixes the exact publishable Rust closure at 27 packages rooted at auths-proof and auths-proof-sdk;
• marks non-public workspace packages non-publishable and validates required public package metadata;
• renames the SDK package to auths-proof-sdk while retaining the internal dependency alias to avoid source-level churn;
• strengthens the core boundary check to parse actual Cargo dependency tables and resolve paths canonically;
• updates the formal source-closure digest for the package and lockfile changes;
• records the GitHub-first verification policy in AGENTS.md.

Tests and evidence

• Phase 7 entry-gate evidence: exact merged-main CI run succeeded at https://github.com/auths-dev/auths-proof/actions/runs/30644122505
• cargo xtask ci: passed locally before the GitHub-first policy was added. This included architecture, semantic freeze, workspace tests and clippy, core boundary, MSRV, fuzz smoke, Lean/Aeneas qualification, Kani, bindings, package smoke tests, live-demo parity, and compliance.
• semantic-freeze validator: 11 xtask tests passed; inventory reported 42 entries and 27 public Rust packages.
• formal qualification: 107 compiled statements, 4 reviewed external links, 0 compiled external axioms; source-closure digest c5f185d14eb2afa12eb39d424fab17d3b943f16fd070f60c0b8df8da40785542.
• package smoke: all 27 selected Rust crates packaged successfully; npm and Python install smoke tests passed.
• authoritative merge evidence remains this PR's hosted GitHub CI, including pinned two-run Charon/Aeneas translation and full-history Gitleaks.

Affected claims

• frozen meanings and byte surfaces cannot drift under the same semantic IDs and versions;
• the first-RC public Rust catalog is exact and excludes private workspace packages;
• the public SDK coordinate is auths-proof-sdk;
• bounded-domain semantics remain owned by their vertical domain modules;
• core-boundary path decisions are based on resolved Cargo dependency paths rather than incidental strings.

Explicit exclusions

• no release manifest, SPDX SBOM, provenance, attestation, assurance bundle, or release archive is produced here;
• no package, tag, GitHub prerelease, or public assurance claim is published;
• no RC preparation or promotion workflow is enabled;
• no external reviewer or design partner is engaged;
• no secret is uploaded and no external gate is claimed.

Remaining gate conditions

• merge this unit only after all hosted code checks pass, including pinned formal translation and Gitleaks;
• complete the AP-SPEC-032 release-evidence PR;
• complete the prepare/promote workflow PR;
• complete the candidate-closure PR;
• obtain two successful hosted preparation runs and SLSA 1.2 Build Level 3 evidence;
• receive explicit promotion authorization before any RC publication;
• close Phase 8 exact-claims gates before AP-SPEC-033 or AP-SPEC-027 through 031 begins;
• complete independent external review before making strong public security claims.

Rollback and withdrawal

Before any RC consumes this freeze, revert this PR. After a freeze is consumed, do not mutate an existing ID/version: introduce a new semantic version and freeze version. This PR changes no external release state.

[bordumb]

CI follow-up: dependency job 91224072139 failed because cargo-deny interpreted seven path-only dev-dependencies on private workspace testkits/adapters as wildcard versions. Commit 88b2334 enables cargo-deny's allow-wildcard-paths behavior: wildcard registry dependencies remain denied, while repository-local path dev-dependencies are permitted. No local verification rerun; the new hosted CI run is the evidence.