- config.example.json shipped agentsR='' (present-but-empty), which the
jget/:-/|| chain treats as unset-inherited from GATE_AGENTS — Lane R
would run the full P agent set, hit 'unsupported lane' and false-red
after paying for six agents of real-model turns. Example now ships the
launcher default dsh,pi, matching _doc_agentsR.
- entrypoint.sh: rm the per-run rc files before launching the concurrent
subshells — a stale .rc-plugins/.rc-restart in a persistent outDir
could be read back if the subshell died before its final echo, a
failure direction that HIDEs a red in release verification.
- both READMEs: the dsh-variants opt-in sentence still listed dsh-google
(now in the default set), and laneScript/snapshotRender were missing
from the config-key lists (they only had _doc_* in the example).
cleanEnv() strips BILI_* from the lane spawn env by design, so
BILI_ROLLOUT_SNAPSHOT_RENDER set container-wide still resolved to
off(bucket) in every lane (verified in the #6785 gate run: rollout line
showed snapshotRender=off(bucket, 7206/10000 vs 0bp) with the env set).
The knob now writes rollout.features.snapshotRender=true into the P/R
lane bili.json — the config tier the rollout resolver honors above
bucketing. GATE_SNAPSHOT_RENDER stays harness-internal; the proxy never
sees it.
The snapBase storage substrate reaches the R lanes via the bundled
restart-lanes.mjs, but the P lanes prefer the candidate checkout OWN
plugin-lanes.mjs — which predates the GATE_SNAPBASE knob, so P ran
off-state in candidate-branch verification. laneScript forces the
bundled copy (the entrypoint already supports GATE_LANE_SCRIPT for
exactly this). snapshotRender flips BILI_ROLLOUT_SNAPSHOT_RENDER
(env tier > 0% rollout) so the egress BODY plane renders live —
without it storage.snapBase only exercises the v2 substrate, not the
body path the verification is actually after. Both keys documented in
config.example.json.
config.example.json gains the key with a _doc_snapBase line; README en/zh
config-key lists gain the entry: P/R lanes only, "all" or protocol
cohort subset, absent/off = byte-identical gate.
Coverage follow-up (PR#6793 review, owner asked: 协议是否齐全/场景/客户端):
1) Lane R gains a claude agent (opt-in via agentsR): the first non-openai
CLIENT-SIDE wire through the deep restart scenario. Prefix topology —
claude-code speaks anthropic over HTTP to a harness-managed bili proxy
child (-> recorder -> model); the small window is bili-side (provider
context + proxy restart, prefix-lane rule) at 32768 (claude's
unfoldable floor sits near the wall — Lane P lesson). Kill matrix:
the proxy is killed via SIGTERM/SIGKILL and re-established on the SAME
port by the harness (nothing auto-respawns a manually started proxy);
each respawn must resume the session, outbound stays compact AND
non-empty, exactly one live proxy (no split-brain). Every turn also
gets the 600s budget (claude small-window preflight is a multi-stage
distillation; the 300s budget SIGTERMs mid-preflight — Lane P lesson).
2) dsh-google joins the default Lane P matrix: the google-generative-ai
client door now runs in every gate (the harness lane + wire assertions
already existed; it just was never in the default set).
Also: restart-lanes setHostWindow is now async (the claude window flip
restarts the proxy and must complete before the next turn); the claude
proxy handle is hoisted to lane scope so teardown always reaps it; stale
duplicate comment removed.
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