Show useful data before the first preview - #51
Merged
Merged
Conversation
Review samples or an empty start with the Plan, then check the visible records and intended login. Keep reseeding deliberate and preserve development-only samples and changed passwords.
raghubetina
force-pushed
the
codex/first-preview-guide
branch
from
September 23, 2026 04:35
bd812a6 to
bde5f71
Compare
raghubetina
marked this pull request as ready for review
September 23, 2026 04:44
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.
The tester journey moved from setup straight to CRUD without checking that reviewed examples or the intended login were usable. The README now includes the sample-data or explicit empty-start choice in Plan review, checks visible relationships and demo sign-in, explains when development seeding is needed, and preserves changed passwords and development-only samples during continuation.
The baseline commit and publication instructions in README, AGENTS, and CONTRIBUTING retain reviewed public demo values in the generated source while excluding real credentials and private CLI state.
Part of Skills #83. This aligns tester instructions with the published Skill and generated README; it changes no pins, seed implementation, authentication, or container behavior.
Validation:
script/checkpassed with pinned Ruby 4.0.5 and Node 24.18.0;git diff --checkpassed. Hosted CI passed atbde5f71b4c08c1f4d910ed0dd50db637d711728b, including source/depth-one checks and both configured devcontainer installation smokes. The existing source/local-preview evidence retains its original inputs. This documentation change records no fresh generated-app Codespace or unaided colleague trial.Exact companion testing-guide edits are retained locally for coordinator review. The live gist and its historical trial results are unchanged. Its separate archive-path and Selenium guidance work remains under Service #729/#730.