Skip to content

docs(README): clarify step 5 fast gate vs VISUAL>=1 build mode#119

Merged
dadachi merged 1 commit into
mainfrom
docs/step5-fast-vs-build
Jun 12, 2026
Merged

docs(README): clarify step 5 fast gate vs VISUAL>=1 build mode#119
dadachi merged 1 commit into
mainfrom
docs/step5-fast-vs-build

Conversation

@dadachi

@dadachi dadachi commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

What

Step 5 ("Drive the build green") listed only the build-mode Layer 2 commands — bin/rails db:prepare+runner, xcodebuild build, ./gradlew assembleDebug — and presented them as the unconditional exit gate.

Those only run when NATIVEAPPTEMPLATE_VISUAL>=1. src/dispatch.ts:143:

const layer2Mode: Layer2Mode = visualLevel >= 1 ? "build" : "fast";

At the default VISUAL=0, Layer 2 runs in fast mode (src/validation/layer2.ts):

Platform Default (fast) VISUAL>=1 (build)
Rails bin/rails routes bin/rails db:prepare + bin/rails runner 'puts OK'
iOS xcodebuild -list xcodebuild build -scheme …
Android ./gradlew --version ./gradlew assembleDebug --no-daemon

Change

Reword step 5 to describe both the default fast gate and the VISUAL=1+ escalation, matching the Runtime table (line ~126) and the VISUAL=1 flag doc (line ~218), which already state this correctly.

🤖 Generated with Claude Code

Step 5 described only the build-mode Layer 2 commands (xcodebuild build,
gradlew assembleDebug, rails db:prepare+runner) and presented them as the
unconditional exit gate. Those only run when NATIVEAPPTEMPLATE_VISUAL>=1
(src/dispatch.ts:143 forces build mode). At the default VISUAL=0, Layer 2
runs in fast mode — bin/rails routes, xcodebuild -list, ./gradlew
--version — a lighter probe, no full build. Spell out both paths to match
the Runtime table and the VISUAL=1 flag doc.
@dadachi dadachi merged commit 476a043 into main Jun 12, 2026
1 check passed
@dadachi dadachi deleted the docs/step5-fast-vs-build branch June 12, 2026 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant