feat(intelligence): render the semantic Git journey

[szmyty]

Closes #32

Outcome

Materializes /journey/ as a semantic, release-bounded Repository Intelligence history that connects intent, work, code, proof, and delivery without flattening the repository into a raw commit list.

What changed

• preserves Observatory's canonical lifecycle-event order and deterministic release chapter boundaries
• renders five calm semantic lanes for roadmap/ADR intent, issues/PRs, commits, checks, and releases/deployments
• explains why every chapter formed and inserts neutral 72-hour interval markers without claiming inactivity
• reverse-links only explicit quest and ADR relationships, with stable cross-view fragments
• keeps orphaned or unlinked events visible as unclassified context without inventing intent
• expands each event into recorded transitions, actor, assertion, freshness, provenance, canonical source, and quest-level changed-file evidence
• adds URL-backed state, kind, time, chapter, release, actor, assertion, freshness, roadmap, and decision filters
• adds sticky chapter navigation, keyboard traversal, browser-local resume, structural chapter comparison, and optional replay
• progressively discloses playback and comparison to keep the default history cognitively light
• disables automatic replay for reduced-motion preferences while retaining manual scrubbing
• keeps every event in static HTML and uses browser content-visibility for large histories
• permits only full immutable historical commit links while keeping source blobs pinned to the represented commit
• renders honest missing and empty journey states
• adds 240-event history coverage and advances REL-RI-004 to complete / REL-RI-005 to active pending merge
• adds the action's journey output and updates Relay's catalogs and documentation

Boundaries

Observatory owns chronological normalization and release chapter formation. Relay owns display lanes, explicit cross-view navigation, static route composition, and disposable browser state. Pull-request merge events are rendered exactly as projected; raw Git parent topology, private branch names, and event-level file paths remain explicitly unavailable until a reviewed public-safe contract supplies them. Relay does not scrape providers, infer causality, calculate productivity, or deploy the consumer site.

Validation

• python3 -m unittest discover --start-directory tests --pattern "test_*.py" --verbose — 110 passed
• python3 -m compileall -q actions scripts tests
• node --check actions/repository-intelligence/assets/site.js
• python3 scripts/validate_actions.py
• jq empty action-catalog.json workflow-catalog.json tests/fixtures/repository-intelligence-site/snapshot.json
• git diff --check origin/main...HEAD

Roadmap-Step: REL-RI-005
ADR-Ref: ADR-007

[devactivity-app]

Pull Request Summary by devActivity

Metrics

Achievements

• @szmyty
  Earned XP: 15⭐
  Check Your Progress