panellisted

Convene an external panel review on $ARGUMENTS. Five panelists — `deepseek-flash` · `nemotron` · `glm` · `kimi` · `minimax` — each with its own endpoint, key alias and reasoning effort, all configured outside this file. `NOTES.md` beside this one holds the measurements behind every rule here; read a section of it when you are about to change that thing, or when its symptom appears. **Write the package and the summary in the language the user asked in** — one language end to end, never mixed. ## 0. When to convene Convene on genuinely open questions where being wrong is expensive to undo. A panel summoned to agree only manufactures consensus, which is worse than no panel at all. ## 1. Build the question package The panel can search the web and read the repository, but it **cannot see this conversation** and will not navigate a codebase you know better. Hand over the load-bearing material yourself. Use Read/Grep to pull the real content, then assemble: - Background and stack (one line) - The goal and the hard constraints - The relevant code **verbatim — paste it in full, never elide with `...`** - Decisions, constraints and exact user quotes settled in conversation but never written down - At most three specific questions **Ask for full reasoning at whatever length it takes.** Capping the question count keeps them focused; capping answer length deletes exactly what §3 adjudicates on. **Always end the package with these requirements:** > 1. List the key assumptions you