Add an evidence-first /audits/ view to Repository Intelligence

[szmyty]

Outcome

Add a dedicated /audits/ experience to the shared Repository Intelligence shell so a maintainer can quickly understand a repository's audit history, current findings, opportunities, recurring problems, and candidate backlog without reading every full report first.

The canonical source remains the repository-owned audit report and normalized Observatory snapshot. Relay renders a human-friendly projection and never becomes the audit source of truth.

Dependencies

• Parent Repository Intelligence program: egohygiene/relay#27
• Deterministic publication: egohygiene/relay#33
• Aether audit profiles/report contract: egohygiene/aether#86
• Observatory normalized audit model: egohygiene/observatory#20

Core questions

The page should answer, at a glance:

• When was this repository last audited?
• Which profiles were run?
• Was the run complete, partial, blocked, failed, stale, or unavailable?
• What are the highest-priority confirmed findings?
• Which findings are recurring?
• Which findings are feature opportunities or experimental ideas rather than defects?
• Which proposed issues have already been materialized on GitHub?
• What changed between two audits?
• Where is the full canonical report/evidence?

UX structure

Provide a low-cognitive-load experience such as:

Current posture

• latest represented revision;
• latest audit date/freshness;
• profiles executed;
• completion state;
• compact counts by classification/severity/status without a synthetic health score.

Findings explorer

Filter/sort by:

• audit/profile;
• classification;
• severity;
• confidence;
• status;
• area;
• effort/impact;
• issue materialization state;
• first/last observed.

Visually separate:

• confirmed/probable defects and risks;
• contract drift/completeness gaps;
• maintainability/quality opportunities;
• feature opportunities;
• experimental opportunities;
• intentional trade-offs;
• positive observations;
• needs clarification.

Audit timeline

Show immutable audit runs over time with represented revisions, profile versions, freshness, completion state, and links to full reports.

Candidate backlog

Render audit-proposed issues as proposals and show linked GitHub issues separately when they actually exist. Never imply that a suggested issue has been accepted or created.

Compare

Allow comparison between two audit snapshots/runs using Observatory's normalized relationships where available:

• newly observed;
• still recurring;
• explicitly resolved/superseded;
• changed severity/confidence/status;
• newly available/unavailable evidence.

Do not infer resolution from silence in a later report.

Source-of-truth / drill-down behavior

Every summary object should be expandable or linked to:

• canonical audit report;
• source finding/evidence;
• represented commit;
• owning profile/spec version;
• linked GitHub issue when separately created.

The full report should remain available as Markdown/source and may optionally be rendered in-page. Do not convert the UI projection into a competing editable report.

Partial-adoption behavior

The route must remain useful before every repository has the audit system installed:

• no audits → explicit not yet audited/unavailable state;
• unsupported report version → explicit compatibility state;
• stale audit → visible stale label;
• partial/blocked run → show inspected and uninspected scope;
• missing evidence → unknown, never green.

This page must not become a rollout gate merely because infrastructure is still being built.

Accessibility / responsive behavior

• keyboard-accessible filters and disclosure controls;
• screen-reader meaningful state labels;
• no color-only severity/status semantics;
• usable mobile summary before dense tables;
• reduced-motion support;
• large histories remain performant and searchable.

Acceptance criteria

• /audits/ is a first-class route in the shared Repository Intelligence shell.
• It consumes versioned Observatory audit snapshots rather than scraping report prose.
• Latest posture, history, findings, candidate backlog, and source-report links are available.
• Defects, conformance drift, feature opportunities, and experiments are visually/semantically distinct.
• Missing/stale/partial/blocked/unsupported evidence remains explicit.
• Suggested issues and real GitHub issues cannot be confused.
• Two-audit comparison preserves evidence and never infers resolution from absence alone.
• Every finding can drill down to canonical source/evidence when authorized.
• Responsive, keyboard, screen-reader, and reduced-motion behavior is verified.
• Fixtures cover a clean repository, a finding-heavy repository, partial adoption, and no audit history.
• Relay's deterministic build/publication workflow includes the route without clobbering other Pages content.

Non-goals

• Editing audit reports in the browser.
• Running the auditor from the static page.
• Automatically creating/fixing GitHub issues.
• Replacing /health/ or Hygiene conformance with audit findings.