CI Guardrails – Planetary Orchestrator Fabric v0

This demo ships with a dedicated CI workflow to check changed planetary demo code on pull requests and main. A passing run supports the tested scenarios; it is not a production certification.

Workflow Summary

• Location: .github/workflows/demo-planetary-orchestrator-fabric.yml
• Triggers:
  • Any change beneath demo/Planetary-Orchestrator-Fabric-v0/**
  • Dependency updates (package.json, package-lock.json)
  • Manual runs via workflow_dispatch
• Environment: Hardened Ubuntu 24.04 runner with outbound network locked to the declared GitHub, npm and Python dependency endpoints.

Job Stages

1. Checkout & Hardening – Uses step-security/harden-runner to freeze outbound egress except the allowlist.
2. Dependency Sync – npm ci ensures deterministic dependency graphs.
3. Recovery and computer-work regressions – Run the Node regression suite and five Python checks, including the real adapter against an authenticated local fixture. No live provider is called.
4. Type Safety – npx tsc --noEmit validates the demo sources compile without generating JS.
5. Unit Tests – npm run test:planetary-orchestrator-fabric executes deterministic simulations verifying shard balance, node failover (<2% drop), checkpoint resume, and the automated restart drill.
6. Demo Execution – npm run demo:planetary-orchestrator-fabric:ci runs the fabric end-to-end in CI mode, producing reports under reports/ci-latest.
7. Acceptance Autopilot – npm run demo:planetary-orchestrator-fabric:acceptance -- --label ci-acceptance --jobs-high-load 4000 --outage-node mars.gpu-helion proves the <2% drop rate and restart recovery criteria.
8. Artifact Validation – Node scripts ensure summary.json, events.ndjson, dashboard.html, and owner-script.json exist and contain required sections.

Branch Protection

Add the following required status checks to the repository settings:

• demo-planetary-orchestrator-fabric

With this in place, no pull request touching the demo can merge without a green, reproducible run.

Local Verification

Run the same steps locally:

npm ci --no-audit --prefer-offline --progress=false
npx tsc --noEmit --project demo/Planetary-Orchestrator-Fabric-v0/tsconfig.json
npm run test:planetary-orchestrator-fabric
npm run test:planetary-orchestrator-fabric:regressions
python -m pytest demo/Planetary-Orchestrator-Fabric-v0/tests/test_simulation.py -q
npm run demo:planetary-orchestrator-fabric:ci
# Optional: run the combined acceptance suite locally
npm run demo:planetary-orchestrator-fabric:acceptance -- --label local-acceptance
# Optional: replay the curated blueprint during acceptance
npm run demo:planetary-orchestrator-fabric:acceptance -- --label local-blueprint --jobs-blueprint demo/Planetary-Orchestrator-Fabric-v0/config/jobs.blueprint.example.json
# Optional: rehearse the restart drill locally
demo/Planetary-Orchestrator-Fabric-v0/bin/run-restart-drill.sh --label ci-drill

Deliverables Captured by CI

These checks validate the simulator and allocation task. Record hosted CI results for the exact pull-request commit and commission production integrations separately. Browser checks can be run with node --import tsx demo/Planetary-Orchestrator-Fabric-v0/tests/browser-qa.cjs after installing Playwright Chromium.