refactor: move all project folders into projects/ subdirectory

This change reorganizes the repository structure to keep the root directory
clean. All 15 project folders are now nested under projects/, alongside
infrastructure directories (agents/, templates/, deliverables/, rag/, skills/).

This allows the repository to grow without polluting the core service directories.

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

templates/InputFromUser.yml

@@ -53,7 +53,7 @@ steps:
            - 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."
+              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").

templates/book_chapter.yml

@@ -38,6 +38,11 @@ steps:
       PROSE STYLE GUIDE: {prose_style}
       TARGET CHAPTER LENGTH: ~{chapter_target_words} words
 
+      CONTINUITY GUARDRAILS:
+        - Use ONLY the outline / character bible and the immediately previous chapter for continuity.
+        - Ignore future chapters, editorial reviews, roundtables, polish drafts, and any non-chapter artifacts.
+        - Never pull facts from a deliverable whose filename indicates a later chapter than {chapter_ref}.
+
       ⚠️ CRITICAL: Your task name tells you EXACTLY which chapter to write.
       Look at the CURRENT MESSAGE — write THAT chapter and ONLY that chapter.
       Do NOT write Chapter 1 unless the message explicitly says "Chapter 1".

templates/chapter_polish.yml

@@ -3,12 +3,17 @@ description: >
   Iris polishes the chapter using the editorial consensus from the review roundtable.
 debug: true
 model: power
+system: agent_prompt
 
 skills:
   - guides/YAFictionGuide.md
   - guides/RomanceFictionGuide.md
   - guides/SciFiFictionGuide.md
 
+agent_prompt:
+  - "= identity.md"
+  - "agent.rag.json"
+
 sections:
   - agent
   - project
@@ -43,6 +48,7 @@ steps:
       Preserve everything the editors marked as STRENGTHS.
       Do not add new plot elements not already present.
       Match the genre tone and audience level throughout.
+      Output ONLY the fully rewritten chapter text.
 
   - type: document
     filename: "{{task_name_slug}}-polished"

templates/chapter_review.yml

@@ -4,6 +4,7 @@ description: >
   critique in their editorial domain.
 debug: true
 model: power
+system: agent_prompt
 
 skills:
   - guides/YAFictionGuide.md

templates/chapter_roundtable.yml

@@ -5,6 +5,10 @@ description: >
   The output is a consensus critique (or documented disagreement) for the polish step.
 
 debug: true
+system: agent_prompt
+
+agent_prompt:
+  - "= identity.md"
 
 skills:
   - guides/YAFictionGuide.md