Review a change for modular-monolith dependency violations, domain leakage, plugin trust, adapter coupling, premature distribution, and future API/UI compatibility.
Audit a run, strategy, tool, dataset, prompt, or report for hidden operational assistance H, knowledge assistance K, engine leakage, retries, and attribution errors.
Scaffold the Zugzwang uv monorepo after the blocking human gates are ratified. Use for M0 workspace creation, package boundaries, tooling, lockfile, and the first fake-only vertical slice.
Implement, validate, import, redact, or evolve the self-contained run bundle and its checksummed evidence/analytical artifacts.
Perform an independent, defect-first review of a Zugzwang change covering correctness, architecture, scientific integrity, persistence, security, tests, migrations, and documentation.
Create or review an operational SQLite migration and any related event/bundle upcaster with interruption, compatibility, and evidence-preservation tests.
Design or preregister a Zugzwang experiment with causal hypotheses, controls, protocol coordinates, datasets, metrics, power, budgets, promotion gates, and claim limits.
Implement or modify the standard-chess environment, state/action codecs, legal transitions, renderers, tasks, opponents, or PGN export behind the chess port.