The concrete definition of what CLAUDE.md calls the manual review a Blocky bump requires. Renovate opens these as a one-line change to BLOCKYVERSION in blocky/Dockerfile (Tempio bumps are the same shape via TEMPIOVERSION). Most bumps merge as that bare one-liner — this runbook is how you earn that conclusion instead…
Implements tests from a guard specification and proves each guard bites by removing the named production line. Use for regression guards, contract tests, table tests, and vitest cases. Requires a caller-supplied specification — it does not decide what to guard.
Adversarial read-only defect hunt over a named area — wire handling, resource leaks, concurrency, silently dropped events, unwired seams. Produces ranked candidates with a reproduction path. It finds and argues; it never fixes.
Scoped implementation work whose correctness a test or lint run can prove. Use for Go/Svelte changes inside named files with a stated acceptance command. NOT for composition-root wiring, wire formats, REST/WS contract semantics, Matter parity constants, or auth/secret code.
Produces one bundled, read-only device-level review of an ESPHome device configuration: config-pattern conformance, credential and API/OTA hardening, schema currency against the official ESPHome docs, Home-Assistant-driven binding correctness, display rendering discipline, display design conformance (palette roles…
Produces one bundled, read-only repository-level review of an ESPHome fleet: directory layout, package architecture and concern cuts, the substitution and defaults interface each package exposes, deviation handling through !extend / !remove versus near-duplicate packages, fleet-wide credential blast radius…