Publish strict-valid partial code graphs

[forhappy]

Summary

• keep the closed v1 validator strict while quarantining invalid nodes, incident edges, and identity collisions
• atomically publish a valid non-empty partial graph and disclose exact omission counts through CLI and compass.query/1
• raise the shared production graph reader cap to 1 GiB for qualified enterprise artifacts
• remove the superlinear unique-stub resolver scan found on the full Angular repository
• document heavyweight qualification across Django, Spring Framework, Rails, Laravel, Bevy, ASP.NET Core, Angular, and Entire

Verification

• cargo clippy --workspace --all-targets --locked -- -D warnings
• cargo test --workspace --locked
• cargo test --workspace --locked --no-run
• scripts/qualify_code_graph_v1.sh --fixtures-only
• full release builds and typed searches on all eight pinned heavyweight repositories

The v1 qualification covers 57 languages, 45 node kinds, 28 edge kinds, 24 flows, 23 negative cases, 500k-edge scale, and byte-identical clean, warm, forced, restored, and alternate-checkout builds. Angular now completes in 49.39 seconds after previously exceeding 12 minutes.

Known quality gap

Spring Framework publishes a strict-valid and queryable partial graph, but its incomplete_coverage diagnostic is material: 17.37% of candidate nodes and 22.16% of candidate edges are quarantined. This PR keeps that limitation explicit; producer resolution should be improved separately without weakening the v1 contract.