Signage/ci/display-scenarios at 914034dda0a2adcec67415897c5917216bbbcf46 - Signage - The Covenant

Zayin/Signage

Files

T

ekklesiaandClaude Opus 5.5 3073baeb8b

CI / lint (pull_request) Successful in 12s

Details

CI / typecheck (pull_request) Successful in 15s

Details

CI / test (pull_request) Successful in 19s

Details

CI / build (pull_request) Successful in 18s

Details

CI / integration (pull_request) Successful in 3m34s

Details

ci: build, test, and run Signage inside a pinned Ekklesia on every change

Signage had no CI. Its tests passed while three defects shipped that
appear only inside Ekklesia, in a real browser. Every job now assembles
Signage into a pinned platform commit, as an instance does, and
installs that workspace with --frozen-lockfile:
- lint, typecheck, test: Signage's own checks;
- build: the platform's gates against exactly this module set (boundary
  rules, module manifest, migrations), then the build;
- integration: the deployment image from the platform's Dockerfile,
  then the platform's split-topology smoke. It pairs a kiosk display,
  restarts it on the same profile, and runs the scenarios in
  ci/display-scenarios.

The supporting files:
- ci/platform.env pins one platform commit. ci/assemble.sh fetches the
  platform's main and refuses a pinned commit that is not on it, so CI
  only runs reviewed platform code.
- ci/pnpm-lock.yaml is the assembled workspace's lockfile, regenerated
  with ci/update-lock.sh.

Same trust rules as the platform: actions pinned by SHA,
persist-credentials false, no secrets, no pull_request_target.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-05 19:11:53 -05:00

5 lines

303 B

Plaintext

Raw Blame History

 # The platform's display-device scenarios this repository's CI runs against Signage, one per line
 # (scripts/lib/deploy-smoke-display.mjs in the pinned platform). Pairing a kiosk and restarting it on
 # the same profile always run first. A change that makes another scenario pass adds it here.
 two-pages