End-to-end validation of dugite-node and dugite-cli against cardano-node on the local 3-node devnet (dugite-bp ↔ dugite-relay ↔ cardano-relay). Use when the user asks to run integration tests, validate a build before release, exercise the transaction surface (good + bad txs across every era/type), cross-validate dugite forging against Haskell, soak-test, or sanity-check changes touching ledger/consensus/network/forging/CLI. Orchestrates testnet/local-devnet (setup → run → tx-zoo → evidence → verify) across multiple configuration rounds and produces a single pass/fail report. NOT for unit tests (use `just test`) or public-testnet soaks (use scripts/soak).
Manages Dugite releases — version bumps, CI verification, changelog, GitHub release, and devnet-validate QA integration. Use when preparing a release tag, publishing crates, or checking release readiness.
Cross-validate dugite-node's ledger-state calculations byte-exactly against the Haskell cardano-node 11.0.1+ reference implementation, per-epoch, via paired ledger-state dumps and the canonical IntersectMBO source. Use when investigating any divergence in reserves/treasury/fees/deposits/rewards/snapshots/pool-state/governance vs Haskell; before changing any RUPD/reward/snapshot/era-transition formula in dugite-ledger; when triaging GitHub issues tagged "epoch-diff" or "#615-class"; when a "residual drift" remains after a ledger fix; or when about to commit any ledger fix that changes per-epoch state. NOT for tx-level Phase-1/Phase-2 validation drift (use devnet-validate) and NOT for consensus header divergence.
Review the Dugite project documentation (mdBook, published as GitHub Pages at https://michaeljfazio.github.io/dugite/) section by section for accuracy, relevance, and currency. Use when asked to review docs, update documentation, audit the wiki, check for stale content, or verify docs match the code. Works through every page in docs/src/ cross-referencing against actual source code.