kevinveenbirkenbachandClaude Opus 5 7e1c2d1273 test(gpu): make the lookup's consumers assert wiring instead of passing vacuously ...

Collapsing the three GPU call sites into one lookup moved the whole decision behind lookup('gpu', ...), but both consumers' tests still stubbed lookup with a constant. One test per file went red; three more kept passing for the wrong reason, because the stub's {} is falsy and every negative case was therefore true no matter what the template did.

The stubs now branch on the lookup name and record what they were asked, so each file guards what it still owns: the answer reaches the compose key or the role variable, and the lookup is asked for this service. The declared-flag-times-device matrix stays with the lookup's own tests, which is also where the boolean() over bool() rationale now lives, checked rather than written beside the call it protects.

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

2026-10-05 20:34:19 +02:00

..

cli

fix(merge): repair what the main merge left broken

2026-10-04 03:21:09 +02:00

group_vars

feat(readme): let a role name the companions its documented deploy needs

2026-09-25 09:03:56 +02:00

library

test(stack-host-files): read back what apply just wrote, uncached

2026-10-03 22:54:25 +02:00

plugins

fix(gpu): decide GPU acceleration in one lookup instead of at every call site

2026-10-05 17:45:00 +02:00

roles

test(gpu): make the lookup's consumers assert wiring instead of passing vacuously

2026-10-05 20:34:19 +02:00

scripts

fix(ci): limit the fingerprint shortcut to branches of this repository

2026-10-05 03:06:57 +02:00

utils

fix(images): leave a retired role out of image discovery and the pin watch

2026-10-05 18:30:50 +02:00

__init__.py

…