v0.8.0 - Check commands and check evidence

Every agent is handed the project's check commands. sssf.config.yaml's quality: block was known only to quality.py, so an agent asked to settle a claim with a check guessed an entrypoint - and in a project that wraps its toolchain (a container, a version manager, a task runner) the guess fails for reasons unrelated to the code. agents.project_checks_notice now renders the block into every agent's system prompt as a # Project checks section: each check's name and its real argv, the same entrypoints the verify gate runs. Unconditional, so no ADW, roster, or prompt change is needed in any stamped repo; a repo with no quality: block renders no section.

A review verdict says what evidence it rests on. ReviewOutput gains checks_executed and checks_note. In an ensemble, a reviewer whose checks could not run rests on strictly less evidence than one whose did, and nothing in the envelope said so - a blind reviewer's blocker carried a peer's weight for three rounds. The synthesizer now weighs a reviewer that ran a check above one that did not on any claim about behavior. gates.verdict_consistent refuses a checks_executed: true that names nothing, so a claim of evidence cannot buy authority it did not earn.

Reviewers stay inside their remit: the suite is the verify phase's job, a reviewer may run one check to settle a specific claim, and nothing re-runs the suite - three fan-out branches racing one working tree is how checks corrupt each other.

agents.py, the reviewer/synthesizer prompts, and the operator skill are MANAGED, so stamped repos pick this up on their next update.

PR #44.