work-planlisted

# Work / 3. Plan Produce an implementation-ready plan without changing source files. Read [../QUALITY.md](../QUALITY.md) first. Make the plan protect reliability, restraint, modular boundaries, the simplest complete implementation, human authorship, clean breaks over obsolete compatibility, meaningful tests, and proof over status reports. Prefer existing dependencies and durable architecture over speculative packages or stopgaps. ## Fixed route - Launch exactly one `gpt-5.6-sol` subagent at `xhigh` effort with `fork_turns: none`. - Give it a fun call sign, the exact task statement, source of truth, read-only ownership, constraints, acceptance checks, and validation requirements. - Require it to inspect independently and return concrete evidence, not a status report or a claim that an unproved step is “routine.” - Require it to register the exact goal before inspection and complete it only after its evidence is collected. - Let the analyst run until it returns the plan, a real blocker, or a user-input request. Do not cancel it because a polling window or arbitrary wall-clock interval elapsed; a wait timeout is not a failure. - The analyst must not edit, commit, deploy, spawn, or delegate. - Report the successful launch as a compact table with `Agent`, `Working on`, `Goal`, `Ownership`, and `Model`. ## Required plan The parent defines the mission, then the analyst inspects only relevant context and resolves evidence-backed decisions. Keep any early alternatives independen