Session report — extend GitHub link enrichment to commits + devreports cross-refs (parked 2026-05-14)

DARE.CO.UK · PARKED SKETCH · 2026-05-18

Mirrored from ~/.claude/.../memory/project_session_report_link_enrichment_parked.md. This is a design sketch parked for future build — read for context, not as a current deliverable.

Two parked follow-ups to today’s Toolkit-changes hyperlink work; extend the same pattern to (a) repo activity commits and (b) devreports cross-references inside session reports

Today (2026-05-14) shipped GitHub blob URLs on the Toolkit changes section of the session report (commit f17d20d in xlab-co/toolkit). Dan: “The URL links are great to git-hub, invaluable.” Two natural extensions parked for the next pass:

1. Repo activity → commit URLs. The session report’s repo-activity section lists commits affecting dare-co-uk. Today those appear as plain text (commit SHA + message). Each should hyperlink to its GitHub commit page:

• xlab-studio/dare-co-uk commit SHA → https://github.com/xlab-studio/dare-co-uk/commit/<sha>
• Same SHA-pinning discipline — the URL is meaningful forever, not just while the branch is current

Implementation hint: the existing _github_blob_url() helper can be adapted; needs a /commit/<sha> form instead of /blob/<sha>/<path>. The repo activity section already has the SHA; just needs the remote URL resolution.

2. Devreports cross-refs → link to the live report. When the session report mentions another devreports artefact (dare_sitemap_regen_2026-05-14, etc.), it should link to it. Today some sections (e.g. _sitemap_regen_sketch_2026-05-14_) appear as plain text or bare paths. The target URL shape:

• https://devreports.dare.co.uk/<slug> — the live devreports surface (Access-gated; Dan sees real content, others see login)

Implementation hint: regex-detect dare_[a-z_]+_<YYYY-MM-DD> slug patterns in the report text and wrap them in markdown links. Same prefix-routing principle as today’s _host_for_internal_path() fix in the dashboard narrator — both use the same shape detector. Could share the helper via xlab-co/toolkit’s growing path_routing.py (doesn’t exist yet; another small consolidation candidate for v1.5).

Both extensions follow the same principle as today’s work: the session report becomes the canonical “what state was the world in on this day” artefact when links accrete. Future-Dan landing on a session report from months ago should walk straight into the relevant code / commit / devreports entry without archaeology.

Resume condition: next time dare_session_report.py gets touched substantively. Likely triggers: - A new session-report feature being added - A bug surfacing in the report layout - Dan asking for further enrichment

Pairs with: - feedback_hover_preview_on_urls.md — markdown title-attribute tooltips; the lightweight cousin of full hover preview - feedback_thumbnail_on_ship_pattern.md — visual diary substrate - project_dare_thumbnail_service_built.md — devreports already has hover-preview thumbs; session-report cross-refs can opt into the same JS bundle via anchor_enricher.py - feedback_services_1_0_standardised_model.md — the report-emit shape; this enrichment lives inside one service, doesn’t compound across the portfolio yet (could when audrey/dogwood get their own session reports)