fix(workspace): complete the forced local runtime context

The workspace suite represents a developer machine, but Profile.is_ci() reads three signals and the block neutralised only two. INFINITO_RUNNING_ON_GITHUB is baked into .env by the runner-side make dotenv before the container starts, and load.sh regenerates .env only when it is missing, so the value survived into a container that had already unset GITHUB_ACTIONS. registry_cache_active() stayed false, make compose-up omitted compose/cache.override.yml, and the compose track then asserted pull-through on a cache stack that was never created.

40375decb wrote this block before that third signal existed; 94936f198 added the Profile gate a month later.

Accepted side effect: the workspace no longer resolves as GitHub, so it skips the GHCR mirrors and the docker-root wipe in down.py, which key off the same flag.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
kevinveenbirkenbachandClaude Opus 5 committed 2026-08-23 16:38:52 +02:00
1 parent f668082e8c
commit 73ae405854
1 file changed
+2
@@ -12,6 +12,8 @@ set -euo pipefail
# Force local runtime context.
unset GITHUB_ACTIONS
unset ACT
unset CI
export INFINITO_RUNNING_ON_GITHUB=false
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
# shellcheck source=scripts/tests/workspace/utils/common.sh