fix(atlas): treat skipped jobs as OK in run aggregate

Tag-push runs skip the deploy job (deploy is main-only), so runs with a skipped
job were mislabelled "running" in the timeline. Skipped now counts as completed-
OK; only genuinely in-progress states aggregate to running. Test-first.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

internal/atlas/runs.go

@@ -73,21 +73,21 @@ func RecentRuns(tasksJSON []byte, n int) ([]RunDot, error) {
 
 // aggregateState folds per-job outcomes into a run outcome.
 func aggregateState(jobs []Job) string {
-	allSucceeded := true
+	pending := false
 	for _, j := range jobs {
 		switch j.State() {
 		case "failure", "cancelled", "error":
 			return "failure"
-		case "success":
+		case "success", "skipped": // completed OK — skipped (e.g. deploy on a tag push) doesn't block
 		default:
-			allSucceeded = false
+			pending = true // running / in_progress / waiting / queued / unknown
 		}
 	}
-	if allSucceeded {
+	if pending {
-		return "success"
-	}
 		return "running"
 	}
+	return "success"
+}
 
 // LatestRunJobs parses a Gitea `/actions/tasks` response (per-job entries,
 // newest first) and returns the newest run with its jobs in pipeline order.

internal/atlas/runs_test.go

@@ -89,6 +89,16 @@ func TestRecentRuns_GroupsRunsNewestFirstWithAggregateState(t *testing.T) {
 	}
 }
 
+func TestRunState_SkippedJobsCountAsOK(t *testing.T) {
+	// A tag-push run skips the deploy job; the run still succeeded.
+	s := atlas.RunSummary{Jobs: []atlas.Job{
+		{Status: "skipped"}, {Status: "success"}, {Status: "success"},
+	}}
+	if s.State() != "success" {
+		t.Fatalf("skipped+success run state = %q, want success", s.State())
+	}
+}
+
 func TestLatestRunJobs_ErrorsWhenEmpty(t *testing.T) {
 	if _, err := atlas.LatestRunJobs([]byte(`{"workflow_runs":[]}`)); err == nil {
 		t.Fatal("expected error on empty, got nil")