The new ci.yml (#361) runs bazel test //... plus //tools/lint:check, but examples/ is in .bazelignore, so the example-project integration suites (the integration-test skill's scope: build-system support, rendering, interaction, hot-reload against examples/) run nowhere gated. This is the same coverage gap the retired VM bar had — its docs noted the gap (flagged during the #333 review) — carried over to CI.
#345 enrolled examples/ integration runs in SimulatorTestLock, so the sim-claim side is solved; what's missing is a gated runner.
Open questions for whoever takes this:
- Add as a step/job in ci.yml, or a separate workflow (they boot sims and are the heaviest suites — may want to be non-required or scheduled while the CI trial collects wall-clock data)?
- Which examples are mission-critical vs nice-to-have for the gate?
🤖 Generated with Claude Code
The new ci.yml (#361) runs
bazel test //...plus//tools/lint:check, butexamples/is in.bazelignore, so the example-project integration suites (theintegration-testskill's scope: build-system support, rendering, interaction, hot-reload againstexamples/) run nowhere gated. This is the same coverage gap the retired VM bar had — its docs noted the gap (flagged during the #333 review) — carried over to CI.#345 enrolled examples/ integration runs in SimulatorTestLock, so the sim-claim side is solved; what's missing is a gated runner.
Open questions for whoever takes this:
🤖 Generated with Claude Code