Fini af9292d8f5 fix(ai): classify Type 0 components as non-mobile to skip phone chrome ... 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.		2026-05-09 21:00:00 +08:00
..
ISSUE_TEMPLATE	V0.7.0 (#95)	2026-04-11 23:25:13 +08:00
workflows	fix(ai): classify Type 0 components as non-mobile to skip phone chrome	2026-05-09 21:00:00 +08:00
FUNDING.yml	V0.7.0 (#95)	2026-04-11 23:25:13 +08:00
pull_request_template.md	V0.3.3 (#33)	2026-03-11 21:18:49 +08:00