Add an organization-level /hygiene/ contract-conformance view

[szmyty]

Outcome

Add a first-class organization-level /hygiene/ module that shows which versioned Ego Hygiene contracts apply to each repository and the current evidence-backed adoption/conformance posture across the fleet.

This is the fleet counterpart to egohygiene/relay#75 and a bounded child of #27 and #30.

Primary question

Which repositories need attention for which applicable contracts, is the evidence failing versus missing or stale, and what canonical policy/evidence/remediation should I inspect next?

Data and ownership

Consume the normalized model from egohygiene/observatory#5. Hygiene remains policy/applicability authority; validators remain with Egolint, Relay, Identity, and specialist owners; Pace remains rollout authority. The organization page is a read-only projection.

Required experience

• Matrix and compact mobile views by repository and contract domain.
• Filters for repository class/profile/lifecycle, contract owner/version/domain, state, rollout stage, and freshness.
• Explicit conformant, non-conformant, partial, drifted, migration-planned, advisory, blocked, stale, unknown, unavailable, exempt, unsupported, and not-applicable states.
• Progressive-adoption posture such as observe/advisory/ratchet/enforce without treating every newly introduced contract as a blocking failure.
• Deep links to policy, repository /hygiene/, source evidence, represented revision, remediation issue, migration plan, or exemption.
• Cross-links to Audits, Identity, Decisions, Releases/Distribution, Health, and repository detail without copying their canonical data.
• Summary by exception and attention needed; no opaque universal percentage.

Acceptance criteria

• A canonical organization /hygiene/ surface is registered through egohygiene/hygiene#25.
• The module consumes Observatory 💰 [platform] Complete GitHub Sponsors profile (szmyty) #5 rather than re-running validators or scraping repository pages.
• Applicability, conformance/adoption state, freshness, represented revision, owner, rollout stage, and source evidence are visible.
• Missing, stale, partial, blocked, exempt, unsupported, unknown, and not-applicable remain distinct.
• Public output cannot leak private repository existence or metadata.
• Repository rows deep-link to Relay #75 views and canonical evidence.
• A small, partially adopted, exempt, drifted, stale, and inaccessible fixture set passes.
• Mobile, keyboard, screen-reader, reduced-motion, no-color-only, and large-fleet behavior is verified.
• One failed repository snapshot cannot invalidate the remaining view.

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
• Route registry: Define the canonical public-site surface and route registry hygiene#25
• Fleet model: Publish a Hygiene conformance dashboard for every repository observatory#5
• Repository view: Add a contract-first /hygiene/ view to Repository Intelligence relay#75
• Continuous control loop: Roadmap: make audits, hygiene, and organization intelligence a continuous control loop hygiene#58

Non-goals

• Defining policy in the UI.
• Treating all contracts as universally applicable.
• Running validators or mutating repositories.
• Replacing repository /hygiene/ pages.
• A single organization compliance score.