D112 — Stuck report as part of the route

Decision

The stuck report is part of the route: structured RouteResult::Unrouted (reason code, the router's words, rips, fails, pad positions, blocker nets) and a JSON report with the open connections, the crowding of their regions, the parts at their ends, the portfolio's variants, cuts and escape_rings. It carries a disclosure block, is size-limited (40 open connections), and --advisor-redact replaces net and part names by aliases (N1, P3) that are mapped back before the advice is checked. The failure event gets region and blocker_nets

Alternatives

Sending the board file; sending names unconditionally; waiting for doc 06's closed-set boundary analysis before reporting blockers

Reason

Names from a board are a prompt-injection surface and, sent to a cloud model, a disclosure; the report must say what it holds. The victims of the rejected route are the cheap and true part of "blockers" (doc 17 §3)