p2a-task-breakdownlisted

# Plan2Agent Task Breakdown Break an approved implementation spec into tasks that an agent or developer can execute. ## Inputs - `spec_json` conforming to `p2a` package schema `spec.schema.json`. - `spec_json.approval: approved`. - `spec_json.open_decisions: []`. - Every intake `CQ-n` has a valid `spec_json.clarifying_question_disposition`. - Known constraints. - Optional BuildLore-derived spec evidence containing prior failure signals. ## Output Return a `task_graph_json` object conforming to `p2a` package schema `task-graph.schema.json` with: - `schema_version`: `p2a.task_graph.v1` - `projectId` - `version` - `sourceSpec` (use the Gate B folder path, for example `.plan2agent/artifacts/<project_id>/gate-b-spec/spec.json`, when the source is a persisted artifact) - `tasks` Each task must include: - `id` - `title` - `intent` for new tasks: one plain sentence in the approved product spec's primary language stating who can do what when the task is complete - `description` - `status` - `dependencies` - `acceptanceCriteria` - `targetArea` - `suggestedAgentPrompt` - `sourceSpecRefs` - explicit `workKind: ui | non_ui | mixed` for every task under an approved `full + current_iteration` visual experience, with lightweight and optionally overlapping `visualImpact.screenStates` on `ui` and `mixed` tasks ## Validation Gates - Reject task breakdown if the spec is not approved. - Reject task breakdown if any unresolved decision remains. - Reject task breakdown if Gate B clarifyin