[372eac39] Panel outage banner: component + health-state delivery + mocked-contract tests

[roboco-app]

Build the panel's visible surface for the active review-path outage (frontend slice of root be2145b0; backend cell builds the detection/health event in parallel). Frozen cross-cell contract: a health/state surface the panel can read carrying outage active flag, outage type (review_path_tools), window start timestamp, and recovered state; exact schema owned by be-pm — deviations are re-synced via main-pm. Deliverables: (1) a banner rendered while the outage is active that disappears when the backend reports recovery; (2) the delivery mechanism is your interaction-detail call within the contract — polling or bootstrap-payload; (3) read-only banner: no remediation actions, decisions stay with PM/CEO; (4) match the existing panel's design system and tokens — functional surfacing, not a redesign; (5) if the backend surface is not merged when QA runs, mock the contract in frontend tests (cover active-outage, recovered, and contract-not-yet-merged cases). Architectural standard: all changes confined to panel/ — banner component in panel/src/components, data fetching in panel/src/hooks, client state in stores. Code against the contract above even though the backend may not have landed.

[github-actions]

Thanks for opening your first pull request on RoboCo!

Quick checklist before review (most of these are enforced by CI, but worth a glance):

• make quality — ruff format check, ruff check, mypy, pytest (≥80% coverage), and the rest of the gate
• Panel changes pass pnpm lint and pnpm exec tsc --noEmit (run from panel/)
• No # noqa / # type: ignore shortcuts; pre-existing violations in touched files are fixed
• Added an entry under ## [Unreleased] in CHANGELOG.md
• Signed the CLA (the bot will prompt you on this PR)
• Signed your commits — master requires verified signatures (SSH signing setup)
• Updated any affected docs under docs/

See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow.

Welcome aboard — a maintainer will review shortly.