Lean body where each step is a compact test plus a one-line verify/fix note; the single Fowler quote frames the testing angle rather than explaining CQRS, so every token earns its place.

Eight concrete, executable pytest functions with real asserts and parametrize; placeholders like events=[...] are intentional fixture abstractions, keeping examples copy-paste-ready.

Steps 1-8 are clearly sequenced and risky operations (eventual-consistency window, rebuild+swap, out-of-order) each carry explicit Verify checkpoints and feedback loops ('if they diverge, replay the events missing... then re-run').

An overview spine with two well-signaled, one-level-deep links to a real references/rebuild-swap-and-read-your-writes.md file (confirmed present) that holds the longer swap/read-your-writes tests; content is appropriately split.

Lists multiple concrete actions — 'write-model + read-model consistency tests, projection-replay determinism, projection-versioning + zero-downtime swap, eventual-consistency-window assertions' — matching the multiple-specific-actions anchor, not the partial level 2.

Explicitly answers both what ('Build CQRS read-model projection tests...') and when ('Use when a read model is derived... adding a projection, migrating... or chasing a... report') with an explicit 'Use when' clause.

Includes natural user-facing triggers, notably the colloquial bug report 'I changed it but the UI shows the old value', plus 'adding a projection' and 'migrating a projection schema'; good coverage of terms a user would actually say.

A clearly defined CQRS-projection-testing niche with distinct triggers unlikely to fire for sibling skills; conflict risk is low.