mathiasandClaude Opus 4.8 3e28dcf69f 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>

2026-07-20 07:48:30 +02:00

..

atlas.json

feat(atlas): Phase C — live CD/deploy state on stage 07

2026-07-20 07:39:01 +02:00

build_test.go

feat(atlas): Phase B — data-driven /api/atlas.json, CI stage generated from cd.yml

2026-07-20 00:34:06 +02:00

cluster_test.go

feat(atlas): Phase C — live CD/deploy state on stage 07

2026-07-20 07:39:01 +02:00

cluster.go

feat(atlas): Phase C — live CD/deploy state on stage 07

2026-07-20 07:39:01 +02:00

embed.go

feat(atlas): Phase B — data-driven /api/atlas.json, CI stage generated from cd.yml

2026-07-20 00:34:06 +02:00

model.go

feat(atlas): Phase C — recent-runs timeline

2026-07-20 07:45:59 +02:00

runs_test.go

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

2026-07-20 07:48:30 +02:00

runs.go

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

2026-07-20 07:48:30 +02:00

workflow_test.go

feat(atlas): Phase B — data-driven /api/atlas.json, CI stage generated from cd.yml

2026-07-20 00:34:06 +02:00

workflow.go

feat(atlas): Phase B — data-driven /api/atlas.json, CI stage generated from cd.yml

2026-07-20 00:34:06 +02:00