The full real-model gate (A compression / B model switch / U registry /
I install / X auto-update / P host-plugin lanes / R restart kill matrix)
moves into this repo so the lane logic versions with the code under test
and remote CI can run the SAME scripts from the candidate checkout.
Lanes I/X/R and the A/B model calls need a real model endpoint, so they
remain operator-run via the new launcher; ci-gate-plugins.yml keeps
driving Lane P.
- Dockerfile: node:22-slim + the host CLIs pinned to the versions this
repo's own CI uses (dsh / pi / codex / opencode / claude / opencode-v1)
- entrypoint.sh: build the candidate rev, in-container ephemeral verdaccio
(lanes U/I/X, no host registry dependency), keyed-API shims, then run
release-gate-local (A/B/U) + plugin-lanes (P) + restart-lanes (R) +
docker-lanes (I/X) and roll up one GREEN/RED
- docker-lanes.mjs / restart-lanes.mjs / patch-gate.mjs /
verdaccio.config.yaml: the lane drivers and shims
- bili-gate.sh: config-driven launcher — scripts/gate/bili-gate.sh
--config <path> [--rev REF] [--skip ...] [--keep] [--dry-run]. ALL
host-specific facts (model endpoints, API keys, npm registry, git
proxy/mirror, out dir) live in the local JSON config only; nothing
machine-specific is committed here (config.example.json is
placeholders). The stale-image guard from the old host wrapper comes
along: on build failure the existing image is reused only after
byte-comparing every /gate-tools lane script, drift = FATAL.
- README(.zh-CN): full lane table + the endpoint/secret contract +
how-to-run; the old 'the containerized wrapper lives outside this repo'
section is retired