Lighthouse CI Budget for a Route

Add a Lighthouse CI budget for the routes that matter. Fail the build on a regression, not on a noisy score. ROUTES [LIST 3 URLS] Device: [MOBILE] Metrics that gate: [LCP, INP OR TBT, CLS] Numbers I will accept: [TARGETS OR "propose a starting budget from a baseline"] Auth: [PUBLIC | A COOKIE I WILL PROVIDE IN CI] Hosting: [URL OF PREVIEW] DELIVER 1) The config: number of runs, the median, and the assertions. Use numeric budgets for LCP and CLS rather than the overall performance score alone, and say why the score is a bad gate. 2) The CI step and the token or URL it needs. Where the report is uploaded. 3) How we set the first budget: run on main, take the median, add a little room, write the number down. Do not invent a 100. 4) The exceptions process: a comment with an expiry, not a disabled job. 5) What a failure usually means on these routes (image, font, a third party) and the first place to look. Do not gate on accessibility score here if we already have an axe suite; mention both and keep this job about speed and CLS.