mennanov

Use when Rust source under `src/` changes and the Lean proof project needs re-derived types/functions — covers the pipeline, which files are generated vs hand-maintained, and the expected noise.

Use when bumping the pinned Charon or Aeneas release tag in this repo — walks the coupled set of values that must move together, the regeneration/build sequence, and the known drift points enforcement catches.

Use when adding or modifying Rust code under `src/` — covers the constraints that keep the state machine translatable to Lean via Charon + Aeneas, and what to do when you need something Aeneas can't translate.

Use when writing or modifying code in a project that uses BlockWatch — proactively link co-dependent code with `<block affects=...>`/`<block name=...>` so it catches drift when one side changes without the other (an enum and its docs, a constant and its config), or assert two places hold the same value with `<block same-as=...>`. Also for lists that must stay sorted/unique or values with a strict format/size, and when editing files that contain `<block ...>` tags (affects, same-as, keep-sorted, keep-unique, line-pattern, line-count, check-ai, check-lua).