Open an issue before proposing a repository-boundary, protocol, security, database-schema, or dependency-policy change. Keep pull requests focused and use conventional commit subjects.
Run every repository's documented verification commands before requesting review. Changes to runtime contracts or challenge manifests must describe compatibility, security, migration, and rollback effects.
Never commit credentials, participant submissions, hidden evaluation material, generated reports, local caches, orchestration prompts, or model transcripts.