Skip to main content
Feature ID: PF-92
Status: 📋 Specification
Spec: PF-92-performance-budget-enforcement.md
Last Updated: 2026-03-23

​
Overview

PF-92 adds CI-level enforcement for frontend bundle sizes and (Phase 2) Lighthouse scores. It integrates with the Vite build pipeline and GitHub Actions only. It does not introduce runtime API contracts, events, or cross-core data flows. PF-07 remains the owner of production Core Web Vitals and error monitoring; PF-92 complements that with gates before merge.

​
Integration Points (from Spec)

​
Lighthouse CI (Phase 2)

  • Routes (must match spec): /login, /dashboard, /patients, /schedule
  • Gating: Category minimums in thresholds (Performance 80, Accessibility 90, Best Practices 90) are blocking hard gates. Overall score bands (<70 block, 70–79 advisory) are advisory only and do not override category minima.

​
Platform / Build Integration

  • No Platform Integration Layer export required for Phase 1–2 — scripts live under scripts/ and run in CI.
  • No event contracts — no publishEvent or pg_notify.
  • No API contracts — no new REST or Edge endpoints.
  • Tenant isolation: N/A — tooling is repository-global, not per-organization.

​
Boundary vs PF-52 and PF-07

​
Security & Compliance

  • PR comments and CI logs must not include secrets, tokens, or customer data.
  • No PHI — build metrics only.