The Puppeteer path uses <br> tags; the PDFKit fallback now normalizes
"1) ... 2) ..." patterns to newline-separated text via PDFKit's
native text rendering.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Convert "1) ... 2) ..." inline lists to line-separated items in PDF
- Use FY-3/FY-2/FY-1 labels in financial table (was FY3/FY2/FY1)
- Applies to both top-level and nested field values
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The document_processing_events table was never populated. Analytics
endpoints now query the documents table directly using status and
timestamp columns. Also updated upload page labels to remove outdated
"Agentic RAG" references.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add normalizeToMarkdown() that converts inline "1) ... 2) ..." patterns
to properly spaced markdown numbered lists for existing documents
- Update Zod schema descriptions to instruct LLM to use newline-separated
numbered items in list fields (keyAttractions, potentialRisks, etc.)
- Fixes wall-of-text rendering in investment thesis and next steps sections
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Newlines within quoted CSV cells render correctly in Excel and Google
Sheets. Previously all newlines were collapsed to spaces, making
bullet lists and paragraphs unreadable.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Analytics endpoints now query document_processing_events table instead of
returning hardcoded zeros (/documents/analytics, /processing-stats,
/health/agentic-rag)
- Add react-markdown for rich text rendering in CIM review template
(readOnly textarea fields now render markdown formatting)
- Fix upload page references from "Firebase Storage" to "Cloud Storage"
- Fix financial year labels from "FY3" to "FY-3" in DocumentViewer
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
API responses with missing nested fields (sessionStats, agentStats,
qualityStats, averageProcessingTime, averageApiCalls) caused .toFixed()
and .map() to crash on undefined. Added ?? null coalescing throughout.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Archive milestone artifacts (roadmap, requirements, audit, phase directories)
to .planning/milestones/. Evolve PROJECT.md with validated requirements and
decision outcomes. Create MILESTONES.md and RETROSPECTIVE.md.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Frontend admin email now reads from VITE_ADMIN_EMAIL env var instead of hardcoded literal
- Consolidate retention cleanup: remove runRetentionCleanup, add document_processing_events to existing cleanupOldData
- Replace personal email in defineString('EMAIL_WEEKLY_RECIPIENT') default with empty string
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add AlertBanner import and render above nav (admin + active alerts only)
- Add AdminMonitoringDashboard import replacing UploadMonitoringDashboard in monitoring tab
- Add activeAlerts state (AlertEvent[]) with isAdmin-gated useEffect fetch
- Add handleAcknowledge with optimistic update and re-fetch on failure
- Remove UploadMonitoringDashboard import (replaced by AdminMonitoringDashboard)
- AlertBanner filters to active service_down/service_degraded alerts only
- AlertBanner renders red banner with AlertTriangle icon and X Acknowledge button
- AdminMonitoringDashboard fetches health+analytics concurrently via Promise.all
- Health panel shows 1x4 grid of service status cards with colored dots
- Analytics panel shows 1x5 stat cards with range selector and Refresh button
- Both components follow existing Tailwind/lucide-react/cn() patterns
- Create 03-02-SUMMARY.md with task outcomes and decisions
- Update STATE.md: advance to Phase 3 Plan 2 complete
- Update ROADMAP.md: mark plan progress for phase 3
- Mark ANLY-02 requirement complete in REQUIREMENTS.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- admin.ts: four endpoints (GET /health, GET /analytics, GET /alerts, POST /alerts/:id/acknowledge)
- Auth chain: addCorrelationId + verifyFirebaseToken + requireAdminEmail (router-level)
- Health: queries all four service names matching healthProbeService output
- Analytics: validates range format (/^\d+[hd]$/) then delegates to getAnalyticsSummary()
- Alerts: findActive() returns all active alerts; acknowledge returns 404 on not-found
- Response envelope: { success, data, correlationId } matching codebase pattern
- index.ts: mounts admin router at /admin alongside existing routes
- Add import for recordProcessingEvent from analyticsService
- Emit upload_started after markAsProcessing (job processing start)
- Emit completed with duration_ms after markAsCompleted (job success)
- Emit failed with duration_ms and error_message in catch block (job failure)
- All calls are void/fire-and-forget (no await) per PITFALL-6 constraint
- Null-guard on job in catch block prevents runtime errors
- requireAdmin.ts: returns 404 (not 403) for non-admin users per locked decision
- Reads env vars inside function body to avoid Firebase Secrets timing issue
- Fails closed if neither ADMIN_EMAIL nor EMAIL_WEEKLY_RECIPIENT configured
- analyticsService.ts: adds AnalyticsSummary interface and getAnalyticsSummary()
- Uses getPostgresPool() for aggregate SQL (COUNT/AVG not supported by Supabase JS)
- Parameterized interval with $1::interval cast for PostgreSQL compatibility
- Phase 2 plan 4 complete — two scheduled Cloud Function exports added
- SUMMARY.md created with decisions, deviations, and phase readiness notes
- STATE.md updated: phase 2 complete, plan counter at 4/4
- ROADMAP.md updated: phase 2 all 4 plans complete
- Requirements HLTH-03 and INFR-03 marked complete
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Created 02-01-SUMMARY.md with full execution documentation
- Updated ROADMAP.md with phase 2 plan progress (2 of 4 plans with summaries)
- Marked requirements ANLY-01 and ANLY-03 complete in REQUIREMENTS.md
- Added 02-01 key decisions to STATE.md
- 9 tests covering all 4 probers and orchestrator
- Verifies all probes return 4 ProbeResults with correct service names
- Verifies results persisted via HealthCheckModel.create 4 times
- Verifies one probe failure does not abort other probes
- Verifies LLM probe 429 returns degraded not down
- Verifies Supabase probe uses getPostgresPool (not PostgREST)
- Verifies Firebase Auth distinguishes expected vs unexpected errors
- Verifies latency_ms is a non-negative number
- Verifies HealthCheckModel.create failure is isolated
- Install nodemailer + @types/nodemailer (needed by Plan 03)
- Create healthProbeService.ts with 4 probers: document_ai, llm_api, supabase, firebase_auth
- Each probe makes a real authenticated API call
- Each probe returns structured ProbeResult with status, latency_ms, error_message
- LLM probe uses cheapest model (claude-haiku-4-5) with max_tokens 5
- Supabase probe uses getPostgresPool().query('SELECT 1') not PostgREST
- Firebase Auth probe distinguishes expected vs unexpected errors
- runAllProbes orchestrator uses Promise.allSettled for fault isolation
- Results persisted via HealthCheckModel.create() after each probe
