Sprint 61k — Template & Pipeline Correctness Audit

- Fix {task.prompt} → {task.message} in all marketing templates (6 files)
- Add author_bio.yml and ad_copy.yml templates for crimson_leaf_marketing
- Add author_bio task_type to marketing_campaign.yml package schema
- Fix book_outline.yml: remove {prose_style} literal, add anti-truncation rule, fix scifi routing
- Fix InputFromUser.yml: echo full operator message in think output
- Fix planning.yml: add agent:Nova top-level field to lock chair
- Fix publishing genesis.yml: fix {task.message} variable and hardcode Nova title
- Add professional_title to AgentContext and build_state_map
- Increase _DEFAULT_MAX_RAG_CHARS from 4000 to 8000
- Fix adj_pass_rate=0.0: thread adjudication criteria through C# and Python

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

templates/InputFromUser.yml

@@ -70,12 +70,14 @@ steps:
       For category (h), emit one hire_agent action per role — Nova is NOT involved.
 
       OUTPUT FORMAT: Your response IS the user-facing reply. Write it directly.
-      - For work requests: "Task Created: [task name]"
+      - For work requests: "Task Created: [task name]" on the first line, then on the next line
+        reproduce the operator's original message verbatim (the full text of their request).
+        This ensures the task description contains the complete brief for Nova.
       - 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.
+      Do NOT use [did: ...] notation. Do NOT add explanations beyond what is specified above.
 
   - type: package
     packet_type: IntakeResponse