Use generated Compose for browser checks - #52
Merged
Merged
Conversation
Ordinary application checks should use their own Compose files. Keep the browser in the existing workspace project and stop it after failed checks while preserving historical qualification.
raghubetina
force-pushed
the
codex/current-codespaces-guide
branch
from
September 23, 2026 05:09
eeb9fdc to
268d497
Compare
raghubetina
marked this pull request as ready for review
September 23, 2026 05:26
This was referenced Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Browser checks after root Compilation still rely on the archived Drawing Board helper even though the generated application owns its Compose configuration. Use the running container's existing Compose project and the generated Selenium health check, then stop only Selenium even when CI fails. Keep the helper for template and optional nested-application checks, and route current root instructions away from the explicitly historical CLI 0.2.2 contract.
Follows Service #729 on current Board main after #51. Archive-independent attachment and private Codespaces preview remain under #730.
Validation:
script/check, whitespace/newline checks and shell syntax passed. The Board and local colleague-guide command blocks are byte-identical.268d4978b9a2c0d5704dfcfaeb75c8d88f64e591against main09c82de37395cb241af05ee8251fc7dede5fc6ec: source contracts, depth-one checks and both installation smokes.The local fixture used an explicit web-source subset of the used 0.4.0 release-smoke app, with nine relevant runtime inputs matching the current pinned Core. This was a simulated local root-layout transition, not a fresh Compile or pristine artifact check. Codespaces attachment/private-preview and the whole authoring journey were not requalified.
The complete colleague-guide proposal remains local for coordinator review, including current archive paths, RSpec inventory, accepted enum validation, local-primary routing and this recipe. The live gist and historical trial outcomes remain unchanged. No pins, image, setup, attach hook or generated-app implementation changes are included.