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 `.plan2agent/schemas/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 `planning_memory` context containing recall status, report references, relevant results, and prior failure signals. ## Output Return a `task_graph_json` object conforming to `.plan2agent/schemas/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` - `description` - `status` - `dependencies` - `acceptanceCriteria` - `targetArea` - `suggestedAgentPrompt` - `sourceSpecRefs` ## 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 clarifying question dispositions are missing or invalid. - Dependencies must reference task ids in the same graph. - The dependency graph must be acyclic. ## Rules - Use `todo` as the default status. - Split oversized tasks before returning. - Each task's acceptance criteria must be self-satisfiable from that task's expl