ux(ci): prefer native GitHub run views #261

Merged

barrettruth merged 1 commit from ux/github-native-ci-summary into main

2026-04-14 21:09:34 +00:00

barrettruth commented

2026-04-14 21:09:23 +00:00

Problem

GitHub CI runs currently flow through a Forge-specific compact summary that loses the native gh run view shape. That makes the in-buffer run surface feel semantically different from GitHub itself, especially for in-progress runs. The old summary interaction model also risks treating non-job lines like annotations as if they belong to the last job.

Solution

Prefer native run views whenever a backend exposes them, which moves GitHub summaries onto raw gh run view output instead of the compact JSON-reduced summary. Update summary parsing so job step lines still open the parent job log, while annotation lines stay non-actionable, and cover both behaviors with specs.

## Problem GitHub CI runs currently flow through a Forge-specific compact summary that loses the native `gh run view` shape. That makes the in-buffer run surface feel semantically different from GitHub itself, especially for in-progress runs. The old summary interaction model also risks treating non-job lines like annotations as if they belong to the last job. ## Solution Prefer native run views whenever a backend exposes them, which moves GitHub summaries onto raw `gh run view` output instead of the compact JSON-reduced summary. Update summary parsing so job step lines still open the parent job log, while annotation lines stay non-actionable, and cover both behaviors with specs.