Launch gate: native extension and integration-audit policy

[metaforismo]

Goal

Define native extension and integration-audit rules before accepting CUDA, Triton, Metal, HIP, or SIMD submissions.

Launch checklist

• Define allowed native languages and build systems.
• Define sandbox/no-network build policy.
• Define maximum build time and artifact size.
• Require CPU/Python fallback or clear track declaration.
• Add mini inference/training-loop integration audit.
• Define rejection policy for unsafe build scripts or hardware-specific assumptions outside a track.
• Add result-card fields for integration audit status.

Acceptance criteria

• Native submissions can be built from a clean checkout by a trusted runner.
• Microbenchmark wins are not promoted unless integration audit does not regress.
• The website can distinguish Python smoke, native candidate, verified runner, and scaled audit status.