kevinveenbirkenbachandClaude Opus 5 00c02251c0 Merge branch 'feature/swarm-nfs' into feature/svc-net-tor ...

Every conflicted hunk resolves onto the swarm-nfs side, because on all six
files it is the strict superset: it carries the display-name codec
(utils/roles/display.py) the CI role selections now encode through, and the
sequencing glyph move from 910748ec4. svc-net-tor holds no unique content on
any of them -- runs.py even had non-conflicted hunks already calling `codec`,
so keeping its side would have left a NameError.

The lint fallout is settled in the same commit, as 4afc9b770 did for the
previous merge: the shell-or-true lint lives on svc-net-tor (c505ce746) and
swarm-nfs brings two unmarked `|| true` sites with it. Both get a nocheck
reason rather than a rewrite, because neither swallows anything -- the
slaptest call is the measured exception of c4bbbba93 and has_cn_config decides
right below it, and the dockerd restart is followed by an is-active poll that
fatals. In both the exit code was never the authority.

make quality green end to end.

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

2026-08-07 07:47:15 +02:00

..

profile

Merge branch 'feature/swarm-nfs' into feature/svc-net-tor

2026-07-19 15:31:08 +02:00

variant

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

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

__init__.py

…

test_playwright_summary.py

…

test_pytest_summary.py

…

test_run_name.py

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

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