feat(ci): baked CI image + runner config + self-check workflow (T14)

Stand up the foundation's own CI on its Forgejo runner. The committed scope here
is the self-contained half (toolchain + typecheck); the stack-state-dependent
pipelines (pulumi preview, backup-verify) need CI secrets + a state fetch and
land next.

- containers/ci-image/Dockerfile + VERSIONS IMAGE_CI: one baked image carrying
  exactly what preflight validates (pulumi/bun/node/docker/git/age/zstd/jq/vault/
  psql/mc). Built on the VM (like caddy-cloudflare) and used LOCALLY by the runner.
- runner.ts: give act_runner a config.yaml — container.network=foundation-net (so
  job containers reach foundation-forgejo:3000 for checkout + the data plane) and
  force_pull=false (use the local foundation-ci image, no registry). Self-heals on up.
- .forgejo/workflows/ci.yml: preflight (tools + versions vs VERSIONS pins) +
  typecheck (bun install + tsc --noEmit on bootstrap). Gates every push.
- run.sh / backup.sh / restore.sh / dr: take PULUMI_CONFIG_PASSPHRASE from env when
  set (CI secret), falling back to `pass` (operator) — so the scripts run pass-free
  in CI.

Reusable-workflows architecture (per the chosen direction) — the ecosystem CI
(semantic-release, docker/npm/bun builds, eslint/yamllint over the 999_testing.md
candidates) builds on this image + runner next phase.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

VERSIONS

@@ -72,6 +72,13 @@ IMAGE_REGISTRY=registry:2@sha256:PIN_DIGEST
 # (T04) and backup put/get (T12). RustFS speaks enough of the MinIO admin API.
 IMAGE_MC=minio/mc:latest@sha256:a7fe349ef4bd8521fb8497f55c6042871b2ae640607cf99d9bede5e9bdf11727
 
+# CI toolchain image (T14): the baked image the foundation's own .forgejo/workflows
+# run in (pulumi/bun/node/docker/git/age/zstd/jq/vault/psql/mc). Built ON the VM from
+# containers/ci-image/Dockerfile (like caddy-cloudflare) and used LOCALLY by the runner
+# (runner config force_pull:false) — not pulled from a registry, so the tag is the ref.
+# Rebuild: scp the Dockerfile + `docker build -t foundation-ci:latest .` on the VM.
+IMAGE_CI=foundation-ci:latest
+
 # NOTE on specific images:
 #   IMAGE_RUSTFS uses `latest` because RustFS does not (yet) publish stable
 #     semver tags reliably (PLAN-002 R3 — RustFS is young). MUST be pinned by