Document and automate one complete contributor verification command

[clintecker]

Finding

The repository now carries a 489-test pytest suite, invariant collection gates, property/fuzz/state/integration/visual tests, coverage and mutation ratchets, selftest, lint/type checks, site projection checks, and consumer proofs. CONTRIBUTING still leads with press selftest and a real-book run but does not name the reusable pytest suite or provide one authoritative local command matching CI.

Scope

Define a supported contributor verification entry point and a layered fast-to-complete ladder. It may be a Make target or small script, but it must compose existing tools rather than reimplement their laws.

Invariants

• One documented command from a clean supported checkout installs/resolves development dependencies and executes the default pre-PR proof.
• Fast layers fail before expensive real-tool/container/consumer layers.
• The command never passes on zero collected tests, missing required capabilities, skipped required layers, or stale generated projections.
• CI calls the same entry points contributors call.
• Optional/live/costly proofs are explicitly classified with capability diagnostics and replay instructions.
• No step depends on wall-clock sleeps or hidden global environment.

Acceptance criteria

• CONTRIBUTING contains fast unit/property, full local, exact-container, real-consumer, mutation/coverage, and release-bound commands with expected evidence.
• A clean-room script proves the documented command on every supported Python platform.
• The command emits a concise summary of collected invariants, skipped capabilities, artifacts/receipts, and rerun commands.
• Drift tests fail when CI gains a required proof not present in the contributor entry point or vice versa.

Links

• Contribution guide
• Invariant ledger
• Pytest configuration
• Selftest workflow

[clintecker]

Done in 6b058b9. scripts/verify.sh runs the local half of CI's quality gate fast-to-complete (pre-commit battery, then coverage + mutation ratchets and the site build); CONTRIBUTING documents the ladder and names the CI-only layers. Composes existing tools, no reimplementation.