Repository navigation
docs: add generated-output checklist - #146
Merged
Merged
Conversation
docs/OUTPUT-CHECKLIST.md lists what to check on a generated app beyond the validation report: the apps' own tests and linters, substrate setup that must not carry over (google-services.json, store URLs, the env bridge), and the auth, organization, forced-update and admin flows. Each item cites what a passing Orange Baton run (2026-10-18) still got wrong. Linked from the README's project docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UZJxUoubntzu7Ec7DPVfAr
Merged
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.
Summary
Adds
docs/OUTPUT-CHECKLIST.md: what to check on a generated app beyond the validation report, and links it from the README's project docs.The validation report proves the output builds, renders without substrate tokens and gets through one scripted CRUD walk. A passing paid-edition Orange Baton run (2026-10-18), checked by hand on a real iPhone and Pixel 6, still had:
google-services.jsonwith onlyproject_idrenamed (FCM can't get a token)The checklist covers the rename, substrate setup that must not carry over, tests and linters, auth, resources, organizations, forced updates, admin, push/billing/Sentry and localization, with notes on driving real devices (mobilecli for iPhone, adb for Android). It's spec-agnostic and sits next to
SUBSTRATE-CONTRACT.md(rules for the substrate) as the after-the-fact check on the output.Docs only; no code changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01UZJxUoubntzu7Ec7DPVfAr