lab(pod): always refresh the template's lab (no stale-binary skip) #291

Merged

omarz merged 1 commit from development_provisioning_preflight into development

2026-05-24 15:18:32 +00:00

omarz commented

2026-05-24 15:18:27 +00:00

Member

seed_lab_into_pod returned early when ~/hero/bin/lab already existed, so the
template kept running whatever lab it was first seeded with. A stale lab there
silently changes build behaviour — e.g. it ignores PATH_CODE and clones repos
into /tmp/code instead of ~/hero/code (so the sources never make it into the
template snapshot). Always install the orchestrator's (host) lab over the
pod's copy instead; install(1) overwrites, so the template can't drift.

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

seed_lab_into_pod returned early when ~/hero/bin/lab already existed, so the template kept running whatever lab it was first seeded with. A stale lab there silently changes build behaviour — e.g. it ignores PATH_CODE and clones repos into /tmp/code instead of ~/hero/code (so the sources never make it into the template snapshot). Always `install` the orchestrator's (host) lab over the pod's copy instead; install(1) overwrites, so the template can't drift. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

omarz added 1 commit

2026-05-24 15:18:27 +00:00

lab(pod): always refresh the template's lab (no stale-binary skip) a16cb17113

seed_lab_into_pod returned early when ~/hero/bin/lab already existed, so the
template kept running whatever lab it was first seeded with. A stale lab there
silently changes build behaviour — e.g. it ignores PATH_CODE and clones repos
into /tmp/code instead of ~/hero/code (so the sources never make it into the
template snapshot). Always `install` the orchestrator's (host) lab over the
pod's copy instead; install(1) overwrites, so the template can't drift.

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