JSON specifications for the protection rules on main and develop. Apply via the branch-protection.yml workflow (ticket #14) once it lands; until then, this directory is read-only documentation that the Branch-protection contexts sync CI job verifies against the actual workflow jobs.

The contexts array must list every required check by its workflow name: field. The Branch-protection contexts sync job (.github/scripts/check_required_contexts.py) fails CI when:

• a workflow job exists but is missing from the contexts array (lets a new check run without being required)
• a context is listed but no workflow job has that display name (stale entries that silently stop blocking merges)

Update this file in the same PR that adds or renames a CI job. Workflows that should NOT be required (scheduled, tag-triggered, label-only) live in the EXEMPT_WORKFLOWS map at the top of check_required_contexts.py.