feat(clp): build full CLP agent roster, templates, and skills library

- 8 company agents: Lyra (intake), Selene (CEO), Atlas (research),
  Nova (publishing ops), Iris (author), Devon (dev editor),
  Lane (line editor), Cora (continuity editor)
- 19 additional templates (20 total): blog, recipe, short_story,
  book pipeline, ai_article, planning, boardroom, quick, project_index
- 5 skill guides: YA, Romance, SciFi, Blog, Recipe writing
- Rewritten charter and business plan

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

templates/InputFromUser.yml

@@ -1,5 +1,5 @@
 name: InputFromUser
-description: "Intake — translate operator intent into structured work for Nova."
+description: "Human interface agent — translate user intent into structured work."
 debug: true
 system: agent_prompt
 
@@ -16,27 +16,86 @@ sections:
 steps:
   - type: think
     scene: |
-      You are the named agent receiving a message from the operator.
+      You are the named agent receiving a message from the operator via the interface.
+      A single message may contain multiple instructions or subjects at once.
     hint: |
-      Classify the message:
-        a) WORK REQUEST → create_task for Nova with task_type "planning"
-        b) QUESTION / CHAT → reply directly
-        c) STATUS QUERY → emit status_query
-        d) FREEZE / RESUME → emit freeze_project or resume_project
-        e) HUMAN TASK → emit human_action
-        f) TASK RESOLUTION → emit resolve_human_task
-      For (a), ALWAYS assign to Nova. You route, Nova decides.
+      Your ONLY job is to route this message to the right place.
+      You do NOT decide what work to do. You do NOT pick templates. You do NOT assign agents.
+      The CEO (Selene) will receive this message and decide the workflow.
+
+      Classify the message into ONE of these categories:
+
+        a) WORK REQUEST — the operator wants something done (write, research, build, plan, etc.)
+           Create ONE task for Selene with task_type "planning". Include the full message as the description.
+
+        b) SIMPLE QUESTION / CHAT — just a question or conversational remark.
+           Reply directly. Do NOT create a task.
+
+        c) STATUS QUERY — operator asks what is happening, what is pending, what is done.
+           Emit status_query.
+
+        d) PROJECT FREEZE / RESUME — operator says pause/freeze/hold or resume/thaw.
+           Emit freeze_project or resume_project.
+
+        e) HUMAN TASK — operator says a person needs to do something manually.
+           Emit human_action.
+
+        f) HUMAN TASK RESOLUTION — operator says "I did X", "here is Y".
+           Emit resolve_human_task.
+
+        g) COMPANY CREATION — operator wants to create a new company
+           (e.g. "Create a company X", "Start company Y", "Set up a new company called Z").
+           - If the operator provided an explicit company name:
+             Emit procure_company with name, slug, and business_plan extracted from the message.
+             The slug must be lowercase kebab-case (e.g. "Crimson Leaf Publishing" → "crimson-leaf-publishing").
+             The business_plan should capture the description/focus from the message (may be empty string if none given).
+             Do NOT route this to Selene. Do NOT create a planning task.
+           - If NO company name was provided:
+             Do NOT emit procure_company.
+             Instead, reply directly with a name suggestion based on the description.
+             Format: "Company name must be provided. Based on your description, I suggest **{Suggested Name}** (`{suggested-slug}`). Reply with the name you'd like to use."
+
+        h) AGENT HIRE REQUEST — operator wants to hire one or more agents for the team
+           (e.g. "hire a Writer", "add a Researcher and Strategist", "we need a Designer and a Developer").
+           - Emit ONE `hire_agent` action PER agent role requested.
+           - Set `task_type` to the role name (e.g. "Writer", "Researcher", "Strategist").
+           - Set `context` to any extra description about the role (optional — use empty string if none given).
+           - Do NOT route to Selene. Do NOT create a planning task.
+
+      CRITICAL: For category (a), ALWAYS assign to Selene with task_type "planning".
+      Do NOT try to decide the right agent, template, or workflow yourself.
+      Selene is the CEO. She decides. You route.
+      For category (g) with a name, emit procure_company directly — Selene is NOT involved.
+      For category (g) without a name, reply only — do NOT create any task or action.
+      For category (h), emit one hire_agent action per role — Selene is NOT involved.
+
+      OUTPUT FORMAT: Your response IS the user-facing reply. Write it directly.
+      - For work requests: "Task Created: [task name]"
+      - For company creation: "Company creation initiated: [company name]"
+      - For agent hire: "Agent hired: [role]" (one line per agent)
+      - For questions/chat: answer directly
+      - For status queries, freeze/resume, human tasks: brief one-line confirmation
+      Do NOT use [did: ...] notation. Do NOT add explanations. One sentence per action.
 
   - type: package
     packet_type: IntakeResponse
     schema:
       actions:
-        - type: "create_task|save_nugget|status_query|human_action|resolve_human_task|freeze_project|resume_project"
-          task_name: "string"
-          description: "string"
+        - type: "create_task|save_nugget|status_query|human_action|resolve_human_task|freeze_project|resume_project|procure_company|hire_agent"
+          task_name: "string — short name (create_task only)"
+          description: "string — the operator's full message verbatim, plus project context (create_task only)"
           agents:
-            - "Nova"
-          task_type: "planning"
+            - "Selene"
+          task_type: "planning or role name (planning for create_task; role name e.g. Writer for hire_agent)"
+          note: "string — insight to store (save_nugget only)"
+          subject: "string — what to look up (status_query only)"
+          user_name: "string — sender name (status_query briefing only)"
+          task_id: "string — task UUID (resolve_human_task only)"
+          duration: "string — e.g. '2w' (freeze_project only)"
+          company_name: "string — full company name as stated by operator (procure_company only)"
+          company_slug: "string — kebab-case slug derived from name (procure_company only)"
+          business_plan: "string — description/focus extracted from operator message (procure_company only, may be empty)"
+          context: "string — additional role context (hire_agent only, may be empty)"
 
   - type: reply
     target: discussion