af9292d8f5
Why: "Design a profile card" through MiniMax-M2.7 produced a 375×803 mobile screen with auto-injected status bar, because the planner skill listed "profiles" as a Type 2 single-task screen and the orchestrator's isMobileScreen heuristic ran on width≤480 alone. What: design-type.md + decomposition.md add Type 0 (single component: card / badge / chip / modal) with width=400 height=0 1 subtask no chrome. isMobileFullScreen helper extracted to orchestrator-plan-classify.ts and required by both orchestrator.ts and orchestrator-sub-agent.ts so the two paths can't drift on what "mobile" means (Codex review caught this when only orchestrator.ts had the new check). Verified with same MiniMax + same prompt: 400×320 component, 8 nodes, firstChildRole=card, no status-bar. |
||
|---|---|---|
| .. | ||
| agent.ts | ||
| chat.ts | ||
| connect-acp.ts | ||
| connect-agent.ts | ||
| generate.ts | ||
| icon.ts | ||
| image-generate.ts | ||
| image-proxy.ts | ||
| image-search.ts | ||
| image-service-test.ts | ||
| install-agent.ts | ||
| mcp-install.ts | ||
| models.ts | ||
| provider-models.ts | ||
| provider-url.ts | ||
| validate.ts | ||