mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
The any-number-of-meshes test zipped the specs against the planned meshes without strict=, which ruff reports as B905 and the lint-python job failed on. Both sequences come from the same declarations, so strict=True also turns a plan that drops a mesh into a failure instead of a silently shorter loop.