molecule-core/.gitea/workflows/e2e-workspace-lifecycle.yml

name: E2E Workspace Lifecycle (staginge2e)

# core#2332 P1.10 — close the workspace-lifecycle coverage gap.
#
# soft-restart / pause / resume / hibernate were only unit-tested (httptest in
# workspace-server/internal/handlers/*_test.go) and never proven against a real
# container. This drives the Go staginge2e suite
# (workspace-server/internal/staginge2e/workspace_lifecycle_test.go) which
# provisions a REAL throwaway staging tenant, exercises each lifecycle endpoint,
# and asserts OBSERVABLE container state (status transitions + serve reachability
# + url-cleared-on-stop) — not just HTTP 200.
#
# ADVISORY-BY-INFRA. It needs a live staging tenant (a cold molecules-server / local-docker
# provision, was the ~30+ min cold EC2 path), so the real run is workflow_dispatch
# only — NOT per-PR and NOT a
# required check. Promotion to a required branch-protection context is a separate
# CTO decision (mirrors the cp internal/staginge2e suite, cp#386, and the
# peer-visibility flip-to-required pattern, molecule-core#1296).
#
# SPLIT (main-status coherence): the real staging job now lives in its own
# dispatch-only workflow, e2e-workspace-lifecycle-staging.yml. When it was a
# job HERE behind `if: workflow_dispatch || schedule`, every push/PR run of
# this workflow auto-published a `skipped` commit status for it
# (`E2E Workspace Lifecycle (staginge2e) / E2E Workspace Lifecycle (staging)
# (push)`) on every main HEAD — permanent skip-noise on the default branch's
# status surface. A dispatch-only workflow posts NO status on push/PR at all,
# and posts its REAL verdict when actually dispatched. Same trust model, same
# suite, zero behavior change for the compile gate below.
#
# HONEST GATE — NO continue-on-error mask (feedback_fix_root_not_symptom). The
# PR job validates that the suite COMPILES under -tags=staging_e2e and SKIPs LOUD
# without creds (the suite's contract) — a broken test file fails at PR time. The
# real assertion runs on dispatch/cron with staging creds.
#
# Gitea 1.22.6 / act_runner notes honored: no cross-repo uses (mirrored
# actions/checkout SHA), per-SHA concurrency, pinned GITHUB_SERVER_URL.

on:
  # group A: staging added alongside main so the compile+skip PR gate runs on both protected
  # branches. The real lifecycle-staging job (e2e-workspace-lifecycle-staging.yml) provisions on
  # molecules-server (local-docker) via E2E_PROVIDER and stays dispatch-only — a 30-60 min cold
  # provision is not a per-PR cost (the cheap per-PR coverage is the compile+skip gate here +
  # local-provision-e2e).
  push:
    branches: [main, staging]
    paths:
      - 'workspace-server/internal/handlers/workspace_restart.go'
      - 'workspace-server/internal/handlers/workspace_crud.go'
      - 'workspace-server/internal/staginge2e/**'
      - '.gitea/workflows/e2e-workspace-lifecycle.yml'
  pull_request:
    branches: [main, staging]
    paths:
      - 'workspace-server/internal/handlers/workspace_restart.go'
      - 'workspace-server/internal/handlers/workspace_crud.go'
      - 'workspace-server/internal/staginge2e/**'
      - '.gitea/workflows/e2e-workspace-lifecycle.yml'
  workflow_dispatch:

concurrency:
  # Per-SHA (feedback_concurrency_group_per_sha).
  group: e2e-workspace-lifecycle-${{ github.event.pull_request.head.sha || github.sha }}
  cancel-in-progress: false

env:
  GITHUB_SERVER_URL: https://git.moleculesai.app

jobs:
  # PR / compile gate: prove the staginge2e suite compiles under the build tag
  # and skips LOUD without creds. Cheap, honest, non-required. This is NOT a
  # fake-green mask of the real assertion — it fails if the test file stops
  # compiling. bp-required: pending CTO decision (see header).
  lifecycle-compile-skip:
    name: E2E Workspace Lifecycle (compile+skip)
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
      - uses: actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff # v5
        with:
          go-version: 'stable'
          # cache:false — the self-hosted runner bind-mounts a persistent
          # GOCACHE/GOMODCACHE (/var/cache/ci-go-{build,mod}); actions/cache is
          # redundant and corrupts it by untarring over the bind mount ("File
          # exists" -> "Failed to restore" -> partial cache -> linker/typecheck
          # errors on heavy jobs, e.g. test -race link "too many errors" and
          # go-arch-lint "without types"). Fleet sweep after the cp ci.yml find.
          cache: false
          cache-dependency-path: workspace-server/go.sum
      - name: go vet (staging_e2e tag)
        working-directory: workspace-server
        run: go vet -tags staging_e2e ./internal/staginge2e/...
      - name: Compile + skip-run (must SKIP LOUD without STAGING_E2E)
        working-directory: workspace-server
        run: |
          # No STAGING_E2E / creds → the suite MUST skip (not pass-with-zero-
          # assertions, not fail-open). `go test` exit 0 with a SKIP line is the
          # contract. -run pins to the one test so this stays fast.
          out=$(go test -tags staging_e2e ./internal/staginge2e/ -run TestWorkspaceLifecycle -count=1 -v 2>&1)
          echo "$out"
          echo "$out" | grep -q "SKIP: TestWorkspaceLifecycle_Staging" \
            || { echo "::error::expected a LOUD skip of TestWorkspaceLifecycle_Staging without creds"; exit 1; }