After someone associates an edit with an event, the following information could change:
- The page might be moved to a new title
- The page might be deleted
- The individual revision might be (partially) deleted/suppressed
Because the DB table that tracks collaborative contribution is derived from `page` and `revision`, it needs to react to these changes to the source data, presumably via the relevant domain events (if possible) or hooks.
For page moves, we should aim to 1) display the current (most recent) title in the table view, and 2) not double count the same page in the summary view if it was moved.
For deletions, we need to avoid info leaks. For example, we could exclude all edits to pages that have been subsequently deleted, and also exclude all revision that have been revdelled (regardless of what parts of the revision have been deleted). Another question is whether we would hard-delete the association, or soft-delete it and bring it back if the edit is undeleted.
===Acceptance criteria===
TBD