fix(clp): add genesis template, fix roster-driven task types

- templates/genesis.yml: copied from global seed, fixed to use
  roster-driven task types (no hardcoded generic type list)
- agents/nova/agent.yml: added genesis to supported_templates

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

templates/genesis.yml

@@ -0,0 +1,44 @@
+name: genesis
+description: "Project genesis — quick think → structured initial task list → child tasks spawned. Runs once when a new project is created."
+system: agent_prompt
+agent_prompt:
+  - "= system.md"
+sections:
+  - agent
+  - project
+  - roster
+  - message
+steps:
+  - type: think
+    agent: first_available
+    hint: |
+      You are {agent.name}, {agent.professional_title}.
+      A new project has just been created and needs its initial work broken down.
+
+      PROJECT GOAL: {task.prompt}
+
+      Review the project goal and the TEAM ROSTER available to you.
+      Think through what the first concrete deliverables should be.
+      Be specific: what research is needed? What analysis? What is the right sequence?
+      Reference the TEAM ROSTER — use EXACT agent names and task types from the roster.
+      Each agent's supported_templates list tells you the valid task types for that agent.
+      Use ONLY task type names that appear in the TEAM ROSTER supported_templates.
+      Do NOT invent task type names.
+
+  - type: package
+    packet_type: PlanningResponsePacket
+    schema:
+      tasks:
+        - task_name: "string — short descriptive name"
+          description: "string — full instructions for the assigned agent"
+          agents:
+            - "string — EXACT agent name from TEAM ROSTER"
+          task_type: "string — one of the valid task types above"
+          priority: "integer 1 (critical) to 5 (nice-to-have)"
+    insert_children: true
+
+  - type: close
+    rag_update: false
+
+adjudication:
+  enabled: false