Concern
There is no native CI. The complete inventory of code execution is:
- The
sandbox evaluator — broken (see separate issue), binding commented out.
- The
webhook evaluator — a synchronous call-out to CI you host elsewhere, verdict unvalidated (separate issue).
merge.postMergeCommand — runs post-merge in a sandbox (the one correct sandbox usage), also gated on the unavailable SANDBOX binding, and silently no-ops when absent.
Nothing replaces GitHub Actions: no workflow files, no job/step model, no runners, no matrix, no artifacts, no caching, no scheduled workflows beyond the 3 fixed crons, no secrets store for jobs, no deployment environments, no status-check aggregation surface. (Stratum's own CI runs on GitHub Actions.)
Impact
An org leaving GitHub loses its entire CI/CD system with no in-platform replacement.
Suggested direction
Document this explicitly as "bring your own CI via the webhook evaluator," and scope whether a native runner model is in project scope.
Concern
There is no native CI. The complete inventory of code execution is:
sandboxevaluator — broken (see separate issue), binding commented out.webhookevaluator — a synchronous call-out to CI you host elsewhere, verdict unvalidated (separate issue).merge.postMergeCommand— runs post-merge in a sandbox (the one correct sandbox usage), also gated on the unavailableSANDBOXbinding, and silently no-ops when absent.Nothing replaces GitHub Actions: no workflow files, no job/step model, no runners, no matrix, no artifacts, no caching, no scheduled workflows beyond the 3 fixed crons, no secrets store for jobs, no deployment environments, no status-check aggregation surface. (Stratum's own CI runs on GitHub Actions.)
Impact
An org leaving GitHub loses its entire CI/CD system with no in-platform replacement.
Suggested direction
Document this explicitly as "bring your own CI via the webhook evaluator," and scope whether a native runner model is in project scope.