Add project phase tracking and firm knowledge context for agents

[zinkh]

Summary

This PR introduces project phase history tracking (ESQ/APS/APD/PC/PRO/DCE/ACT/VISA/DET/AOR) and exposes firm-specific benchmarks to AI agents via a new firm_knowledge context scope. Architects can now track which mission phase each project is in, view phase transition history, and agents can reference real historical data (phase durations, price catalogs, DPGF costs, CCTP templates) when making recommendations.

Key Changes

Database & Schema

• New table project_phase_history — tracks phase transitions with entered_at and exited_at timestamps
• Added migration file and updated schema.sql with RLS policies
• Indexed on (tenant_id, project_id) for efficient queries

Backend API (server.ts)

• GET /api/projects/:id/phase-history — fetch all phase transitions for a project
• POST /api/projects/:id/phase — set current phase (auto-closes previous phase, logs activity)
• Validates phase exists and prevents redundant transitions

Agent Context & System Prompt

• Added firm_knowledge to AgentContextScope type
• New context builder functions:
  • summarizePhaseBenchmarks() — averages phase durations (min 2 samples per phase)
  • summarizeCostHistory() — aggregates DPGF item prices by designation/unit
• Agent system prompt now includes:
  • Phase duration benchmarks from completed phases
  • Price catalog (articles_type) limited to 40 rows
  • Historical DPGF costs (top 30 by frequency)
  • CCTP excerpts (5 max, 2000 chars each)
• Gated behind firm_knowledge scope — agents without it don't pay token cost

Frontend UI (ProjectDetail.tsx)

• New phase selector showing all 10 mission phases as toggleable buttons
• Current phase highlighted in primary color
• Phase history timeline below selector showing entry/exit dates
• Fetches and displays phase history on project load
• Calls handleSetPhase() to update via API

Types & Localization

• Added ProjectPhaseHistoryEntry interface
• Added firm_knowledge to agent config UI with descriptive label
• Added French/English translations for phase UI labels

Implementation Details

• Phase transitions are atomic: exiting old phase and entering new phase happen in sequence
• Minimum 2 completed phases required before averaging (prevents single-sample bias)
• Cost history aggregates by designation|unite key to group variants
• CCTP excerpts truncated to 2000 chars to control token usage
• All firm_knowledge data is tenant-isolated via RLS
• Activity logging records phase changes for audit trail

https://claude.ai/code/session_01Ruo4H7HxCTkiNKX9wweHt9