Tags and links do not tell you a source moved. They only tell you the notes are related. I still did not know which conclusion needed a look.
What worked: pin the passage the conclusion stood on, then check whether that passage is still the same. Sync, a rename, a delete, two machines writing the same file — those are how it happens. I do not re-read the vault.
Dawni’s Zotero / Retraction Watch + Bases queue is the right tool when a paper updates. This is the in-vault case: a note under a conclusion changed, and the conclusion is still sitting there.
I shipped a small display-only plugin for that, Chamber Drift. It reads a report already in the vault and shows which conclusions lost support. It does not write notes.
Community plugins → Browse → search Chamber Drift.
Two-minute try without the CLI: the demo vault zip is on the GitHub release for abm9111/chamber-obsidian. Open that folder as a vault, install from Browse, open Retention.md. The note says 14 days; a conclusion still stands on 30.