Use generated Compose for browser checks - #37
Closed
raghubetina wants to merge 1 commit into
Closed
raghubetina wants to merge 1 commit into
raghubetina wants to merge 1 commit into
Conversation
Keep root-adopted Rails testing independent of archived planning helpers while retaining the nested-application qualification path. Select the running Compose project and stop Selenium after failures. Refs firstdraft/firstdraft#729.
raghubetina
force-pushed
the
codex/729-generated-selenium-guide
branch
from
September 19, 2026 00:46
1ff1993 to
6cb6cce
Compare
5 tasks
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.
Superseded — 2026-09-23
All three files in this draft were reconciled on current main in #52, merged as
d290c6baf052e4088f34b7938afb2457351fd122after exact-head CI, Opus 5.5 review and bounded local Docker qualification. The colleague guide now publishes the same reviewed recipe. Do not replay this old draft. Its historical evidence remains below.Service #729 retains fresh Codespaces workflow qualification; #730 and Board #38 retain the distinct attachment/private-preview work. Those are not claimed complete here. No software release is part of this supersession.
Earlier scope and research (historical; the status above governs remaining work)
Root-adopted applications still use
design/script/seleniumfor browser checks even though they contain their own Compose service. Route the ordinary checks through generated.devcontainer/compose.yaml, select the running container's Compose project, and explicitly stop Selenium even after CI fails. Explain the separate normal startup path for fresh generated Dev Containers.Keep Drawing Board's helper and its optional nested-application/template qualification callers. The dated qualification records, private-preview hook, archive location, and Skills pins are unchanged.
Companion documentation packet for firstdraft/firstdraft#729. The coordinator owns dependency-order integration and independent cross-repository review.
Distribution hold: keep this PR draft and unmerged until a separately approved release makes the actual Compilation workflow colleagues use deliver the qualified Core Selenium health check. Drawing Board main is the live template and README; merging Core or Service source does not deploy the Compiler. Source integration and passing candidate checks alone do not make these instructions accurate for distributed tools.
Remaining guidance distribution is release-time integration of this Drawing Board PR and publication of the prepared testing-gist draft after that concrete availability condition is satisfied. The public gist remains unchanged under the same release hold. No helper or compatibility fallback is introduced.
Validation: Drawing Board
script/checkpassed with Ruby 4.0.5 and Node 24.18.0;git diff --check, shell recipe syntax, matching local gist recipe, README anchor, final newlines, and unchanged dated root-qualification bytes passed. Author-context documentation review found no blocking findings. These source checks do not claim new generated Rails/system or Codespaces runtime proof; that qualification belongs to the companion packet.