fix: add proposal index, wire prior proposals into edgar review + proposal templates, unblock CLO proposal

templates/company_proposal.yml

@@ -9,6 +9,13 @@ sections:
   - message
   - instructions
 steps:
+  - type: tool
+    action: git_read_file
+    params:
+      path: "deliverables/proposals/index.md"
+    output_key: prior_proposals
+    optional: true
+
   - type: think
     max_tokens: 2000
     output_key: exec_summary
@@ -20,6 +27,14 @@ steps:
       the brief. Do NOT rename, rebrand, or creatively reinterpret the company.
       The brief was written from the mission charter -- it is authoritative.
 
+      === PRIOR PROPOSALS (read this before writing) ===
+      {prior_proposals}
+      === END PRIOR PROPOSALS ===
+
+      The prior proposals above are your institutional memory. Study them.
+      Do NOT repeat a company that was already proposed. Do NOT reuse names,
+      slugs, or concepts that were rejected. Build something new and better.
+
       Write the EXECUTIVE SUMMARY section. Include:
 
       1. PROPOSED COMPANY
@@ -206,6 +221,32 @@ steps:
     dest_path: "deliverables/proposals/proposal-{task.id}.md"
     commit_msg: "proposal: company_proposal task={task.id}"
 
+  - type: think
+    max_tokens: 600
+    output_key: index_update
+    hint: |
+      You just wrote a company proposal. Update the proposal index.
+
+      Read the current index content:
+      {prior_proposals}
+
+      Append a new entry at the bottom of the "## Submitted Proposals" section.
+      Use this exact format:
+
+      ### [Company Full Name] -- Task {task.id}
+      Date: 2026-04-29
+      Status: AWAITING DAVID'S APPROVAL
+      Summary: [2-3 sentences: what was proposed, what gap it fills, key differentiator
+                from any prior proposals]
+
+      Output the COMPLETE updated index file content from the very beginning.
+      Do not truncate. Do not skip sections. Include all prior entries plus the new one.
+
+  - type: document
+    source_step: index_update
+    dest_path: "deliverables/proposals/index.md"
+    commit_msg: "index: add proposal {task.id} to proposal index"
+
   - type: reply
     target: channel
     channel_name: "crimson_leaf:general"

templates/strategic_review.yml

@@ -41,6 +41,13 @@ steps:
     output_key: latest_log_entry
     optional: true
 
+  - type: tool
+    action: git_read_file
+    params:
+      path: "deliverables/proposals/index.md"
+    output_key: prior_proposals_index
+    optional: true
+
   - type: think
     max_tokens: 8000
     rotate_participants: true
@@ -60,6 +67,9 @@ steps:
 
       === LAST CYCLE ENTRY ===
       {latest_log_entry}
+
+      === PRIOR PROPOSALS (all proposals ever submitted) ===
+      {prior_proposals_index}
       ===
 
       Analyze from YOUR perspective:
@@ -162,6 +172,11 @@ steps:
       - State why now (cost of waiting another 30 days)
       - Include 90-day success criteria (measurable, e.g. "weekly P&L report delivered")
       - Note known constraints or dependencies
+      - Reference what was wrong with prior proposals so the new one is different
+
+      === PRIOR PROPOSALS (study these -- do NOT repeat them) ===
+      {prior_proposals_index}
+      ===
 
       Output ONLY the brief text. No labels. No preamble.