[codex] Refresh MVP launch evidence#14
Closed
Iron-Mark wants to merge 5 commits into
Closed
Conversation
## Summary - Add a FlowFit one-page marketing landing page for the Flutter web root. - Keep the app startup available at /#/app and direct app routes available for smoke tests. - Wire APK, privacy, and account deletion CTAs through runtime config and public web URLs. ## Changes Made ### Landing Page - Added a responsive FlowFit landing page using existing logo and onboarding assets. - Added web-only root routing so native Android startup remains unchanged. - Added FLOWFIT_APK_DOWNLOAD_URL for the APK CTA fallback. ### Verification - Added widget and route coverage for landing/app routes. - Extended offline and web smoke documentation and browser smoke coverage for /. ## Why - Give users a clear path to try FlowFit in the browser or download the APK without turning the site into a text-heavy app explainer. ## Notes for Reviewers - The working tree still contains unrelated pre-existing release-readiness edits that are intentionally not included in this commit.
## Summary - tighten FlowFit release readiness gates for Supabase, support inbox, Android live-auth, and store artifact handoff - document the current MVP launch evidence and remaining external blockers - keep local Flutter tests deterministic with serialized test execution ## Changes Made ### Release Gates - add Supabase project DNS reachability checks to local config, GitHub release variable config, strict audit, store release builds, Pages deploy, and Android production release - require native Android live-auth E2E evidence in strict release audit - make support inbox confirmation require structured receipt evidence with external sender and received timestamp - make strict audit reject weak support evidence and missing final store artifact manifests ### Evidence And Docs - add the July 2 MVP launch readiness evidence snapshot - update release runbooks, script docs, and store checklist with support proof and artifact handoff requirements - ignore generated Codex/output artifacts that should not enter source control ### Tests - expand release guard tests for DNS reachability, Android live-auth evidence, support inbox receipt proof, and artifact verification behavior - add dart_test.yaml to serialize the large local test suite ## Why - launch readiness must fail on stale Supabase projects, unverified support inboxes, missing Android E2E evidence, or absent store artifacts instead of relying on shape checks or notes ## Notes for Reviewers - strict release audit still intentionally fails until the configured support inbox has external inbound-mail proof - no secrets are committed; local env and Supabase keys remain ignored/redacted
## Summary - Provide fake but valid Android signing env values in the strict audit MCP helper. - Keep the read-only MCP test focused on the MCP posture instead of failing on missing local signing material. ## Verification - flutter test test\scripts\release_guard_source_test.dart - flutter analyze
## Summary - Record green GitHub PR and CI evidence for the current launch branch. - Replace stale full-test wording with the latest CI test evidence after support-proof hardening. - Keep support inbox, dashboard template copy, and store submission blockers explicit. ## Changes Made ### Launch Evidence - Added PR #13 readiness and GitHub Actions run IDs for Flutter CI and Web Pages readiness. - Updated the current verdict to reflect green repo-controlled evidence while preserving external launch blockers. ## Why - The release handoff should match the current pushed branch state before final launch review. ## Notes for Reviewers - Docs-only change; verified with git diff --check and targeted evidence scan.
## Summary - Correct the MVP launch evidence to show PR #13 was merged into main. - Keep green CI evidence tied to the final PR head commit and preserve the support-inbox blocker. ## Changes Made ### Launch Evidence - Added the main merge commit and merge timestamp for PR #13. - Removed stale ready-for-review wording from the launch snapshot. ## Why - The launch handoff should reflect current GitHub state after the PR merge. ## Notes for Reviewers - Docs-only change; verified with git diff --check and targeted evidence scan.
Owner
Author
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
Verification
Notes