mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-11 13:17:07 +00:00
kevinveenbirkenbachandClaude Opus 5
fb54aa1451
A cancel request does not stop a running step. The runner asks it to end, and a step that ignores the signal keeps going, bounded only by its own timeout-minutes -- 350 for a deploy. Meanwhile the concurrency group holds the newer run on pending until the occupant is terminal, not until it is cancel-requested. Measured on run 32859801382: the cancel was accepted at 15:27:45 and thirteen minutes later ten deploy jobs were still running and the newer run still had not started. The sweep now waits FORCE_CANCEL_AFTER_SECONDS and force-cancels whatever is still not completed. Cleanup steps are skipped for those, which is the price: the artefacts of an already superseded run help nobody. Only entry-cancel-superseded.yml sets the variable -- a closed pull request and a deleted branch have nothing waiting on the group, so they keep cancelling and walking away. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Meta-Layout Integration Tests 🗂️
Integration tests for cross-cutting metadata that describes the project itself: role categories, CLI entrypoints, domain declarations, and GitHub-side CI/CD artefacts (workflows, Dependabot).
Each child directory pins one meta surface; see the per-directory README for scope. Per-role structural rules (meta/main.yml, meta/services.yml, includes) live under roles/; infrastructure layout lives under infrastructure/.
For framework and make test-integration usage see integration.md.