health: file over_budget moments to Chromeria #60

What: contextmd-serve health should file the new moment status over_budget to toolboxmd/chromeria, not here.
Why: toolboxmd/chromeria#251 adds over_budget (a moment cut because its work outran the 1.2 s serving budget); health.py files unknown statuses to contextmd.
So what: the serving owner adds the status to STATUSES and the Chromeria OWNERS list after #251 merges; no user action.

Outcome

A high rate of over_budget moments is filed against toolboxmd/chromeria.

Acceptance criteria

• over_budget is in STATUSES and owned by CHROMERIA in contextmd/serve/health.py.
• A test fails before the change: a log with enough over_budget moments yields a finding owned by toolboxmd/chromeria.

Non-goals

• Changing the serving budget itself (fix(server): Cue waits up to 1.5 s for a score the moment needs now chromeria#251, #248).

Blockers

• fix(server): Cue waits up to 1.5 s for a score the moment needs now chromeria#251 merged.

Required proof

• tests/test_health* with the new case, red before and green after.

Elon record

• Requirements and who asked: findings reach the owner that can fix them (existing health contract); over_budget exists because of fix(server): Cue waits up to 1.5 s for a score the moment needs now chromeria#251 (planner request after Grok's review).
• Deleted: nothing.
• Bottleneck: none; one-line ownership mapping.
• Checked myself: health.py STATUSES, OWNERS and owner() default.