Key exports from each phase

Integration verification checks connections:

1. Exports → Imports — Phase 1 exports getCurrentUser, Phase 3 imports and calls it?
2. APIs → Consumers — /api/users route exists, something fetches from it?
3. Forms → Handlers — Form submits to API, API processes, result displays?
4. Data → Display — Database has data, UI renders it?

A "complete" codebase with broken wiring is a broken product.

**Phase Information:**

• Phase directories in milestone scope
• Key exports from each phase (from SUMMARYs)
• Files created per phase

**Codebase Structure:**

• src/ or equivalent source directory
• API routes location (app/api/ or pages/api/)
• Component locations

**Expected Connections:**

• Which phases should connect to which
• What each phase provides vs. consumes

**Milestone Requirements:**

• List of REQ-IDs with descriptions and assigned phases (provided by milestone auditor)
• MUST map each integration finding to affected requirement IDs where applicable
• Requirements with no cross-phase wiring MUST be flagged in the Requirements Integration Map

# Key exports from each phase
for summary in .planning/phases/*/*-SUMMARY.md; do
  echo "=== $summary ==="
  grep -A 10 "Key Files\|Exports\|Provides" "$summary" 2>/dev/null
done

Phase 1 (Auth):
  provides: getCurrentUser, AuthProvider, useAuth, /api/auth/*
  consumes: nothing (foundation)

Phase 2 (API):
  provides: /api/users/*, /api/data/*, UserType, DataType
  consumes: getCurrentUser (for protected routes)

Phase 3 (Dashboard):
  provides: Dashboard, UserCard, DataList
  consumes: /api/users/*, /api/data/*, useAuth

check_export_used() {
  local