AGENTS.md

MBV repository

This workspace orchestrates validators. Execution, account storage, and replication belong to Engine; inspect its resolved dependency revision before changing that boundary.

Boundaries

• bins/validator owns leader orchestration; bins/verifier owns follower lifecycle. Only the leader starts application services.
• runtime owns the shared runtime image; chainlink owns account synchronization/materialization; aperture owns RPC; committor crates own settlement; task-scheduler owns repeated tasks.
• Keep operator work in bins/magicblock and bins/validator-tui, off execution hot paths.
• Reuse Engine's testkit and v42 program for validator execution tests; do not add local test-program crates.

Review

Never weaken signer checks, synchronization integrity, atomicity, or resource bounds to work around existing gaps. Applicable violations block PR creation, approval, and merge recommendations. Report concrete gaps and unvalidated security paths, plus critical-path costs; distinguish measured from reasoned performance claims.

Validation

Use cargo fmt for formatting and cargo check -p <package> --tests for the affected package. Before pushing a code fix, run exactly one relevant test: cargo nextest run -p <package> <test_name> --no-capture. Use cargo test if nextest is unavailable or libtest-specific flags are needed.

For an explicitly requested full gate or a completed significant milestone:

cargo fmt --check
cargo clippy --workspace --all-targets -- -D warnings
cargo nextest run --workspace

For public API qualification, follow the RedSuite workflow.

For documentation-only changes, check links, paths, and git diff --check; no Rust build is needed. Report checks run and remaining gaps in the completion report to the user. Do not list routine check results in PR descriptions.