chore(web): add gpt5.4 to non-monitored model list

[kilo-code-bot]

Summary

Add gpt5.4 to the HEALTH_CHECK_EXCLUSIONS set in the model health-check route. This excludes it from the top-level health status so it cannot trigger 503 responses, while still reporting per-model health data. This prevents false alerts from inconsistent traffic on this model.

Verification

• Verified the change compiles by inspecting the diff.

Visual Changes

N/A

Reviewer Notes

Single-line addition to the exclusion set. No behavioral changes for other models.

[kilo-code-bot]

WARNING: This exclusion key does not match the model IDs returned by getMonitoredModels()

preferredModels uses openai/gpt-5.4, so HEALTH_CHECK_EXCLUSIONS.has(m) will never match gpt5.4. The health check will continue treating GPT-5.4 as monitored and can still return 503 for it.

Suggested change

	'gpt5.4',
	'openai/gpt-5.4',

[kilo-code-bot]

Code Review Summary

Status: 1 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

WARNING

File	Line	Issue
apps/web/src/app/api/models/up/route.ts	58	Exclusion uses gpt5.4, but monitored model IDs use openai/gpt-5.4, so GPT-5.4 remains monitored and can still trigger 503s.

Other Observations (not in diff)

No additional issues found outside the diff.

Files Reviewed (1 files)

• apps/web/src/app/api/models/up/route.ts - 1 issue

---

_{Reviewed by gpt-5.4-20260305 · 186,686 tokens}