CONTRACTS

@cc [owner:spolu,label:coding] commit-message-title
Commit messages start with a short descriptive sentence or title. An optional body provides context
that is useful beyond the title.

@cc [owner:spolu,label:coding] pull-request-format
Pull requests have a short descriptive sentence or title and a concise body summarizing the changes
and how they were validated.

@cc [owner:spolu,label:documentation] readme-skill-shared-prefix
Ignoring the skill's YAML frontmatter, `README.md` and `skills/code-contracts/SKILL.md` must share
an identical text prefix from `# Code Contracts` through the end of the
`## Specification and grammar` section.

@cc [owner:spolu,label:architecture] shared-contract-verification
`skills/code-contracts/SKILL.md` defines the verification procedure invoked by `$code-contracts verify`;
`.github/actions/contract-review/review.md` delegates general verification to that procedure and
provides workflow-specific context, notification, and output rules.

@cc [owner:spolu,label:product] contract-verification-relevance
Diff reviews MUST report pre-existing violations only when directly related to changed behavior,
an assumption the change relies on, or an introduced or modified contract, and MUST explain that
connection. File, declaration, or call-graph proximity alone MUST NOT qualify. The same relevance
rule MUST apply to findings carried forward from earlier reviews. Explicit audits without a diff
MUST cover the selected scope.