feat(scaffold): clarify dev:harness is a MOCK in app create/init next-steps - #42
Merged
Conversation
…-steps A developer ran `civitai app create`, followed the printed `npm run dev:harness`, clicked Generate, got a placeholder image, and thought the real generation was broken. The terminal next-steps never said dev:harness mounts a mock host. Add a 2-line clarification under the dev:harness next-step (page-money / SDK templates only) spelling out mock-vs-live at the moment the user reads it: dev:harness = synthetic, no real Buzz/compute; dev:live = a real generation that spends Buzz (full-scope key, see README). The page-money README already carries the authoritative mode table — this just surfaces the distinction in the terminal output. Extends the app-create test to assert "MOCK" and "dev:live" appear. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Problem
A developer ran
civitai app create, followed the printednpm run dev:harness, clicked Generate, got a placeholder image, and concluded the real generation was broken. The terminal next-steps never told themdev:harnessmounts a mock host (synthetic results, no real Buzz/compute).Change
printScaffoldResult(internal/cmd/app_init.go) now prints a tight 2-line clarification under thedev:harnessnext-step — for the SDK / page-money templates only (NeedsHarness()), sostatic/page-viteoutput is unchanged:The page-money README already carries the authoritative mode table; this just surfaces the mock-vs-live distinction at the moment the user reads the terminal output. No README changes needed.
Tests
Extended
TestAppCreateDefaultsToPageMoneyto assert the output containsMOCKanddev:live.go build/go vet/go test ./...green,gofmt -lclean.🤖 Generated with Claude Code