Fifteen models flipped from JSON to prose in seventy-two hours

**OUTPUT FORMAT (binding, read first):** your entire response must be exactly one JSON object matching the schema at the end of this brief. The first character of your reply must be `{` and the last must be `}`. No markdown, no headings, no commentary before or after, no code fences, no explanations — the JSON object only.

You are a skeptical principal engineer reviewing a DRAFT incident episode before it enters a curated dataset. The episode was mined from a public bug-tracker thread. Your job is to attack it: find every technical claim that is wrong, implausible, or internally inconsistent — and say what a correct version would look like.

**The draft under review:** RECORD: OpenROAD issue #6066 — BoomTile/Megaboom: 20k routing congestion DRCs at only 0.24 placement density.

**Your review, as a single bare JSON object:** {"verdict": one of SOUND | SOUND-WITH-RESERVATIONS | SUSPECT | IMPLAUSIBLE-FOR-THIS-RECORD, "objections": [...], "mechanism_check", "evidence_check", "attribution_check", "missing_from_story", "most_defensible_part"}

**Hard rules:** attack the NUMBERS, the causal chain, and whether the intervention explains the outcome — not the writing. Do not browse the web or fetch any page. Fewer sharp objections beat a padded list.