Add an organization-level /health/ operational-evidence view

[szmyty]

Outcome

Add a first-class organization-level /health/ module that presents broad operational evidence across repositories without collapsing status, CI, conformance, releases, audits, freshness, security, accessibility, and documentation into one opaque score.

This is the fleet counterpart to the delivered repository /health/ work in egohygiene/relay#88 and a bounded child of #27 and #30.

Primary question

Which repositories or evidence domains currently need attention, what is failing versus stale or unknown, and which specialized view contains the canonical detail?

Data and ownership

Compose normalized Observatory snapshots and domain summaries. The health page is a navigation/orientation layer, not a validator, policy source, status provider, audit engine, or release authority.

Required experience

• Compact organization overview emphasizing exceptions, newly broken evidence, stale/unknown domains, blockers, and next attention.
• Independent dimensions for CI/checks, runtime status, Hygiene, audits, releases/distribution, security, accessibility, documentation, continuity, and evidence freshness where applicable.
• Explicit conformant/passing, non-conformant/failing, partial, drifted, blocked, stale, unknown, unavailable, exempt, unsupported, and not-applicable states.
• Repository and domain filters with represented revision, evidence age, owner, and canonical deep link.
• Cross-links to /status/, /hygiene/, /audits/, /releases/, /distribution/, and repository /health/.
• No implication that no audit, diagnosis, or monitor evidence means healthy.

Acceptance criteria

• A canonical organization /health/ surface is registered through egohygiene/hygiene#25.
• The page composes versioned normalized summaries rather than re-running checks or scraping dashboards.
• Operational domains remain independent and drill down to their canonical specialized views.
• No universal health/compliance/readiness score hides unknown or not-applicable evidence.
• Passing, failing, partial, drifted, blocked, stale, unknown, unavailable, exempt, unsupported, and not-applicable remain distinct.
• Represented revision, freshness, owner, and provenance are visible for material claims.
• Public output cannot leak private repositories, counts, findings, topology, or evidence.
• One unavailable domain/repository cannot break the remaining page.
• Healthy, mixed, newly broken, stale, unknown-heavy, inaccessible, and partially adopted fixtures pass.
• Mobile, keyboard, screen-reader, reduced-motion, no-color-only, and large-fleet behavior is verified.

Dependencies / related

• Parent shell: Evolve Organization Intelligence into a modular fleet control plane #27
• Master epic: [EPIC] Finish Repository Intelligence, Organization Intelligence, and site control-plane surfaces #30
• Baseline portal: Build an organization-level Intelligence portal at egohygiene.io/intelligence/ #15
• Route registry: Define the canonical public-site surface and route registry hygiene#25
• Repository health view: Render core check evidence at /health/ in Repository Intelligence relay#88
• Fleet Hygiene: Publish a Hygiene conformance dashboard for every repository observatory#5
• Fleet distribution: feat(distribution): publish fleet package availability, version, and installability dashboards observatory#13
• Fleet audits: Normalize repository audit evidence and fleet audit posture observatory#20
• Fleet status: Normalize service-status and incident evidence for repository and fleet views observatory#23

Non-goals

• A universal score.
• Replacing specialized views or canonical evidence.
• Running validators, audits, or monitors.
• Treating missing evidence as success.