Item 3 of the CI-live-tests setup: the integration step now injects NISSE_LLM_*, NISSE_ROLE_EXECUTOR, and NISSE_MATRIX_* from repo Actions secrets. The existing skip-guards mean a missing secret or unreachable service degrades to a skip with its reason printed (-rs), never a red X on unrelated work.
This PR's own CI run doubles as the reachability test (item 2): check the Integration tests step's log — "7 passed" means both live paths work from the runner; skips will name exactly which variables were missing, and a failure will show which network hop broke (the candidates we've seen before: public-IP hairpin into Authelia, or DNS inside the runner container not following split-horizon).
Item 3 of the CI-live-tests setup: the integration step now injects `NISSE_LLM_*`, `NISSE_ROLE_EXECUTOR`, and `NISSE_MATRIX_*` from repo Actions secrets. The existing skip-guards mean a missing secret or unreachable service degrades to a skip with its reason printed (`-rs`), never a red X on unrelated work.
This PR's own CI run doubles as the reachability test (item 2): check the Integration tests step's log — "7 passed" means both live paths work from the runner; skips will name exactly which variables were missing, and a failure will show which network hop broke (the candidates we've seen before: public-IP hairpin into Authelia, or DNS inside the runner container not following split-horizon).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The integration step now receives the LLM and Matrix env vars from
repo secrets, so the live smoke tests run in CI when the runner can
reach the services; the skip-guards keep a missing secret or
unreachable service as a skip, never a failure. -rs surfaces skip
reasons in the CI log for diagnosis.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Skipping now keys solely on NISSE_LLM_BASE_URL and
NISSE_MATRIX_HOMESERVER: if the sentinel is set, the live path is
expected to work and any other missing variable is an assertion
failure naming it, not a silent skip. A misnamed or misplaced CI
secret previously produced a green run with no live coverage.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Item 3 of the CI-live-tests setup: the integration step now injects
NISSE_LLM_*,NISSE_ROLE_EXECUTOR, andNISSE_MATRIX_*from repo Actions secrets. The existing skip-guards mean a missing secret or unreachable service degrades to a skip with its reason printed (-rs), never a red X on unrelated work.This PR's own CI run doubles as the reachability test (item 2): check the Integration tests step's log — "7 passed" means both live paths work from the runner; skips will name exactly which variables were missing, and a failure will show which network hop broke (the candidates we've seen before: public-IP hairpin into Authelia, or DNS inside the runner container not following split-horizon).
🤖 Generated with Claude Code