mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-07 19:32:17 +00:00
kevinveenbirkenbachandClaude Opus 5
293c67780d
Run 34421944328 Bluesky#1 stopped at "The requested handler 'compose-up' was not found in either the main handlers list nor in the listening handlers list", right after cloning the social-app build context. The pre-compose staging (01_social_app.yml, 02_login_broker.yml) and the PDS routine (03_pds.yml) notify compose-up and compose-build, but the handlers only exist once sys-stk-backend loads sys-svc-compose, which happens later in the role. 00_core.yml now includes sys-svc-compose with tasks_from: none.yml and handlers_from: main right after the once flag, the same handler-only registration sys-stk-backend and sys-svc-rdbms dedicated.yml already use. The notifications still run at the stack's own flush, after the compose files exist; the role has no earlier flush. A handler-order test pins the registration ahead of the pre-compose block. The oauth2-proxy cfg heal leaves its inline shell for files/shell/heal_sso_proxy_cfg.sh, which receives the cfg path and the container name through the environment. The blanket "container stop ... || true" becomes a precondition: the container is stopped only when container inspect finds it, so a directory is still removed when the container is gone, and a failing stop of an existing container now fails the task instead of vanishing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>