kevinveenbirkenbachandClaude Opus 5 128e177255 fix(bluesky): notify the compose rebuild only after the backend renders the stack ...

The pre-compose staging (social-app clone, login-broker copy, pdsadmin
download) ran before sys-stk-backend and notified compose-build and
compose-up. On a fresh host the container runtime's first flush ("Restart
and enable docker service") then ran the compose handlers before
/usr/bin/ca-inject and compose.yml existed, and "Generate CA trust
override" failed (run 34615516009, job 103327034609).

The staging tasks now only register their result. A changed-only notifier
after the sys-stk-backend include triggers compose-build and compose-up, so
no compose topic is pending at any earlier flush, and the handler-only
include that registered the owner early is gone. The ordering test asserts
both halves: the staging files notify no compose topic, and the rebuild
notifier sits after the backend include.

Verified locally in compose, variant 1: the reinstall full cycle passed
pass 1 with failed=0 and the rebuild task changed after the backend
include, pass 2 Playwright passed, and an update run finished failed=0 with
the rebuild task skipped.

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

2026-09-11 20:46:10 +02:00

..

cli

fix(ci): answer a role-only selection by existence, not by variant None

2026-09-10 01:44:59 +02:00

group_vars

fix(litellm): gate consumers on a served model, not on the gateway being deployed

2026-09-04 19:48:32 +02:00

library

…

plugins

refactor(sso): compute the app logout target once in the sso lookup

2026-09-11 13:06:19 +02:00

roles

fix(bluesky): notify the compose rebuild only after the backend renders the stack

2026-09-11 20:46:10 +02:00

scripts

…

utils

fix(litellm): let the database follow the inventory and keep the network a dedicated one is reached on

2026-09-11 13:32:36 +02:00

__init__.py

…