Observed source mismatch
On 2026-09-19, after #40 merged at 14:43:46 UTC to d2f488f783dd98167c4ba65fb6a7937ddea92e53, a new Codespace requested from main at 15:02:07 UTC reported prebuild: true but opened clean source aed9635a4dc191eb1f384e500c10648a5cec2215 and installed the older agent versions. Actual source and provider setup logs were checked before any smoke/setup rerun. The fixture was stopped by 15:09 without updating or rebuilding it.
Read-only configuration UI showed Every push for main and .devcontainer/devcontainer.json, all five regions, two retained versions, and optimization enabled. During this attempt, workflow history showed only the successful September 15 prebuild at aed9635, with no automatic successor run. A failed-latest-prebuild fallback was not established.
A manual refresh of the unchanged configuration produced successful run 35451319086 at d2f488f. The next fresh fixture, created at 15:38:08, opened that exact source and passed installation/configuration/catalog and synthetic-state preservation checks. It was stopped at 15:49:35. That success does not explain the absent automatic successor or prove source synchronization on first VS Code attachment.
The complete dated synthesis is in the merged qualification receipt. This operational question is separate from #39's completed latest-agent installation work.
Follow-up
- Establish why no automatic successor appeared for that merge: inspect provider trigger/configuration semantics and available run/event evidence before changing settings.
- Determine the supported actual-source freshness guarantee for both direct-template and existing-repository launch, including whether any first-attachment update occurs. Do not infer it from prebuild success alone.
- Choose a small remedy only if the evidence demonstrates one is needed. Keep the ordinary vendor/GitHub workflow where it works; do not add a custom updater as a speculative workaround.
- Retain actual head/tree verification in qualification. Keep provider behavior distinct from the native-agent installer and First Draft CLI/Skill compatibility.
This issue authorizes investigation only; no scheduling/configuration change or new live fixture is required by its creation. The previous fixtures are shut down and should not be resumed without an assigned test scope.
Observed source mismatch
On 2026-09-19, after #40 merged at 14:43:46 UTC to
d2f488f783dd98167c4ba65fb6a7937ddea92e53, a new Codespace requested frommainat 15:02:07 UTC reportedprebuild: truebut opened clean sourceaed9635a4dc191eb1f384e500c10648a5cec2215and installed the older agent versions. Actual source and provider setup logs were checked before any smoke/setup rerun. The fixture was stopped by 15:09 without updating or rebuilding it.Read-only configuration UI showed Every push for main and
.devcontainer/devcontainer.json, all five regions, two retained versions, and optimization enabled. During this attempt, workflow history showed only the successful September 15 prebuild ataed9635, with no automatic successor run. A failed-latest-prebuild fallback was not established.A manual refresh of the unchanged configuration produced successful run 35451319086 at
d2f488f. The next fresh fixture, created at 15:38:08, opened that exact source and passed installation/configuration/catalog and synthetic-state preservation checks. It was stopped at 15:49:35. That success does not explain the absent automatic successor or prove source synchronization on first VS Code attachment.The complete dated synthesis is in the merged qualification receipt. This operational question is separate from #39's completed latest-agent installation work.
Follow-up
This issue authorizes investigation only; no scheduling/configuration change or new live fixture is required by its creation. The previous fixtures are shut down and should not be resumed without an assigned test scope.