kpi-coach rubric: Rule 9 to cover lock TAKEN/RELEASED banners + N-separate-DM fanout as a structural-fanout sub-case

PM ruled ACCEPT on both scrp-kpi-coach-venus RULES FEEDBACK items (2026-08-12). (1) Extend Rule 9's record-keeping class to cover lock TAKEN/RELEASED banners - same shape as FINISHED banners (state broadcast, no recipient action requested) but Rule 9 is written around 'quotable FINISHED banner' and misses them. (2) Add N-separate-DM-fanout as its own STRUCTURAL-FANOUT sub-case, distinct from aro-blast: worker_fanout_24h only detects aro: broadcasts, so coder-mba-l-cc's identical lock-state body sent as 8 and 9 individual DMs scored as nine ordinary messages and the section came back empty. Detector should key on identical-or-near-identical body across N recipients within a short window REGARDLESS of transport - the fanout is a property of the message, not of the delivery mechanism. NOTE for my own design: this is the same discriminator problem as messages.fanout (see memory project_fanout_rows_have_agent_recipients) - cardinality is not path; here we WANT the cardinality/content test precisely because path-stamping misses the N-DM case.