a38aa2603a
Worker B measured that recorded negatives cluster at the head of every partition: 39 of the first 40 worklist rows and 57 of 271 tier-1 rows (21%) were addresses an earlier session had already attempted and recorded. The triage tool never read the negatives index, so every closed negative returned to the queue head and workers rediscovered them. Fix: sf3_triage reads the tracked config/near_match_negatives.tsv (a new --negatives input) and excludes those rows as recorded_negative=69. The tracked index was grown from 38 Phase-8 rows to 94 by importing 56 Phase-9 negatives from the workers' reports and the coordinator's absorption record (filtered to unregistered; tracked rows win on conflict). Worklist regenerated: the head is now genuinely fresh (0x800F9134, 0x80042D88, 0x800450C4, ...). 3 new synthetic tests; plan-level tests wired for the new argument. The phase plan said extract negatives only at close; B's measurement showed the harm is per-cycle, so the index is now a living tracked input. Note for P9-T8: keep importing worker negatives each cycle.