# Candidate release gates

A nominated Blacksite candidate requires, when relevant:

- Full workspace/all-feature tests.
- Strict all-target/all-feature Clippy with warnings denied.
- Deterministic content processing and read-only check parity.
- Level/sample/project validators and migration idempotence.
- Packaging, packaged artifact validation, and launch.
- Named native editor/runtime scenarios against candidate binaries.
- Documentation authority/contradiction audit.
- Clean candidate-tree or nominated dirty-tree digest evidence.

Do not precede workspace tests with a redundant workspace check unless a target is otherwise uncovered. Documentation-only changes do not invalidate code gates when recorded inputs are unchanged. Closure additionally requires every issue criterion, epic checklist synchronization, and configured Gitea evidence.