feat(monitoring): scoped rules, occurrences and flow receipt workspace

[Proxicon]

Summary

Adds the tenant-scoped /monitoring workspace for rules, explicit client groups, bypasses, active occurrences and history. Operators can inspect observation quality and age, acknowledge an occurrence, clear it with a reason, and manage a bypass under the corresponding permissions.

Rule editing supports CPU, disk and exact selected-service conditions, target previews and immutable published-flow selection. Occurrences link to their pinned flow version and actual run ID; validated receipts expose incident ID, tracking number and a safe incident link. Flow run results keep those fields readable and keyboard accessible on narrow screens.

Edits survive revision conflicts and failed saves. Pending saves prevent duplicate submission, and cancellation and generation fences reject stale tenant/editor/preview responses. Selected-service watch notices describe the state at save time. The dedicated authenticated Monitoring client uses circuit credentials with no policy retries, redirects or shared cookies.

The fullscreen Services viewer restores its opener only after that exact native dialog is removed. Tenant/client changes, returning to an earlier selection, and disposal invalidate pending restoration.

Scope

• Implements Monitoring UX: Signals dashboard, scoped rules/groups, alert clear and bypass management #144 above #150 Flows (d6f91b1a5474158445d8e57ca1c3d43ea0ba8ef9) and #149 Monitoring backend.
• Inherits 0.1.1-beta.1; beta merge and release remain pending.
• Final source: 2130e2317961cef69f7a6912d8a984398923b81d.

Refs #141, #143, #144, #145.

Validation

• Integrated Flows, Monitoring and credential-isolation regression: 54 component and 19 browser cases passed, zero skips.
• Receipt presentation correction: 5 component and 2 paired browser cases passed, including visible keyboard focus and CSS195×422@DPR2 wrapping.
• Final Services correction: 20 component, 6 Monitoring browser and 7 Services browser cases passed, zero skips. A real admission regression failed all six layouts before the change and passed after it: launcher focus now waits for the exact dialog's removal. Component cases cover pending dismissal, tenant/client changes, A→B→A and disposal.
• Keyboard fixtures await completed theme-menu closure and activator focus before opening Services. The previous hosted System-theme opening timeout lacked a trace; its exact cause is unproved. Existing assertions and timeouts remain intact.
• Shared typed-API layout fixture: 13 cases passed. Shared PostgreSQL fixture regression: 174 cases passed with no retained idle pools.
• Final hosted CI: all 21 checks passed. Independently verified 2,773 generic tests (2,372 backend, 314 components, 68 browsers and 19 API integration) plus 12 Windows installer tests, all passed with zero skips. Uploaded archive digests and source/test-merge tree identity match. Hosted native focus traces verify the dialog was removed before manual opener restoration in all six layouts.

Disclosure

No credentials, customer or employee data, private URLs, internal hostnames or deployment details are included.