kevinveenbirkenbachandClaude Opus 5 910748ec41 refactor(ci): mark deploy-mode sequencing with a many-legged crawler ...

The traffic light said "gate" everywhere else in the pipeline, on the PR
scope check and on the dependency gate, so reusing it for the deploy-mode
order made an ordering knob look like another pass/fail barrier. A crawler
reads as what sequencing is: segments following each other in a line.

Both failure-report entries in the orchestrator move to the ladybug in the
same commit, because they already held the caterpillar and one workflow
cannot spend the same glyph on ordering and on failures. The ladybug is what
the bug-report issue template already uses.

Only the test fixture spells the glyph out; the parser derives its segment
heads from the workflow's own run-name, so it follows the change on its own.
The traffic light stays where it means a gate, and as the release-candidate
symbol in the glossary.

A run title created before this commit still carries the traffic light, so
recovering its sequencing input from the title yields nothing and a retrigger
leaves that one input on the workflow default.

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

2026-08-06 20:58:36 +02:00

..

variant

feat(ci): name deploy jobs after the role, not its id

2026-08-06 20:09:53 +02:00

__init__.py

feat(ci): render Playwright JUnit reports as workflow step summary

2026-05-17 15:30:05 +02:00

test_playwright_summary.py

feat(ci): swarm run summaries with per-host role runtimes

2026-07-19 02:39:27 +02:00

test_pytest_summary.py

style(ci): black-reflow the runtime model, render and their tests

2026-07-19 02:39:28 +02:00

test_run_name.py

refactor(ci): mark deploy-mode sequencing with a many-legged crawler

2026-08-06 20:58:36 +02:00