Tick: took the remaining findings-queue entry. The ReportPolicy doc comment claimed Ray 'only files past a personal threshold'; the shipped mechanism is unconditional cadence filing with a flat 0.4 [TUNE] weight applied by the aggregates that read the filings. Comment and detection.md Reporting clause now state that mechanism; queue entry deleted. Defense: no binding page ever promised a threshold — detection.md said only 'Ray under-reports' — so this resolves a small question by making the owning spec clause and code comment precise (tick.md's question rule) rather than inventing a mechanism. Behavior is unchanged; the under-reporting weight stays an explicit [TUNE] surface.