docs: Add overlap analysis for non-AI coordinator patterns

Detailed comparison showing:
- Existing doc addresses L-015 (premature completion)
- New doc addresses context exhaustion (multi-issue orchestration)
- ~20% overlap (both use non-AI coordinator, mechanical gates)
- 80% complementary (different problems, different solutions)

Recommends merging into comprehensive document (already done).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

apps/api/prisma/schema.prisma

@@ -1053,3 +1053,37 @@ model TaskRejection {
   @@index([manualReview])
   @@map("task_rejections")
 }
+
+model TokenBudget {
+  id           String   @id @default(uuid()) @db.Uuid
+  taskId       String   @unique @map("task_id") @db.Uuid
+  workspaceId  String   @map("workspace_id") @db.Uuid
+  agentId      String   @map("agent_id")
+
+  // Budget allocation
+  allocatedTokens    Int   @map("allocated_tokens")
+  estimatedComplexity String @map("estimated_complexity") // "low", "medium", "high", "critical"
+
+  // Usage tracking
+  inputTokensUsed    Int   @default(0) @map("input_tokens_used")
+  outputTokensUsed   Int   @default(0) @map("output_tokens_used")
+  totalTokensUsed    Int   @default(0) @map("total_tokens_used")
+
+  // Cost tracking
+  estimatedCost      Decimal? @map("estimated_cost") @db.Decimal(10, 6)
+
+  // State
+  startedAt     DateTime  @default(now()) @map("started_at") @db.Timestamptz
+  lastUpdatedAt DateTime  @updatedAt @map("last_updated_at") @db.Timestamptz
+  completedAt   DateTime? @map("completed_at") @db.Timestamptz
+
+  // Analysis
+  budgetUtilization  Float?   @map("budget_utilization") // 0.0 - 1.0
+  suspiciousPattern  Boolean  @default(false) @map("suspicious_pattern")
+  suspiciousReason   String?  @map("suspicious_reason")
+
+  @@index([taskId])
+  @@index([workspaceId])
+  @@index([suspiciousPattern])
+  @@map("token_budgets")
+}