Per-release recall monitor against flora.csv in the dashboard rules view (supersedes #151)

`filter/spec/CONVENTIONS.md` now bans any LLM-labelled corpus as a recall denominator. That settles the core ask of #151 by policy: recall is not measured against labels the pipeline itself produced.

**The unbuilt remainder.** A per-release recall check of the routing piles against the human-curated `flora.csv` — which known FLoRA replications does each release discard, or leave in `pending`? — surfaced in the Stage 4 dashboard's rules view, so the number moves with each release rather than being computed by hand.

Supersedes #151.

Start with filter/spec/CONVENTIONS.md to confirm the recall denominator policy, then trace the Stage 4 dashboard's rules view and how releases expose routing piles. Use the human-curated flora.csv as the reference and consider the work complete when each release shows which known FLoRA replications it discards or leaves pending.

Written by the indexing model from the issue text.