[codex] Add in-app support queue and launch evidence#15
Merged
Conversation
## 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.
## Summary - Add post-merge main Flutter CI and Web Pages readiness run IDs to the MVP launch evidence. - Keep the support-inbox and store artifact blockers explicit. ## Changes Made ### Launch Evidence - Updated the current verdict and full-test evidence to reference main commit 1c7db18. - Added GitHub Actions run IDs 28601898762 and 28601898718. ## Why - Main-branch evidence is stronger than pre-merge PR evidence for launch review. ## Notes for Reviewers - Docs-only change; verified with git diff --check and a targeted secret/blocker scan.
## Summary - Add the local release web build and live localhost web smoke to the MVP launch evidence snapshot. - Keep the strict release audit status explicit: support inbox proof remains the single failing strict gate. ## Changes Made ### Release Evidence - Updated the snapshot context to the post-merge evidence-refresh branch. - Recorded the refreshed strict audit timestamp and result. - Added local runnable web build and local web app smoke evidence. ## Why - The latest autonomous run proved the release web artifact can be served and exercised locally, so the launch evidence should preserve that result. ## Notes for Reviewers - Docs-only update; no app code, secrets, or generated build artifacts are committed. - Local web smoke passed with 59 checks, zero app console errors, and zero failed requests.
## Summary - Add an authenticated Supabase-backed support request queue for FlowFit Help & Support. - Keep email support as a fallback public contact path while app support requests go through RLS. - Update release readiness, smoke verification, docs, and tests for the new support gate. ## Changes Made ### App Support Flow - Added SupportRequestService and SupportRequestDraft validation. - Added in-app Message Support and Report a Bug dialogs that submit support requests. - Added the support_requests table constant and widget coverage for the Help & Support actions. ### Backend and Release Gates - Added the support_requests Supabase migration with authenticated RLS policies and service_role processing grants. - Extended backend verification SQL and live Supabase app smoke to cover support request create/read/delete. - Updated release readiness audit behavior so verified in-app support downgrades missing/weak email receipt metadata to warnings while DNS failures still fail strict mode. ### Docs and Tests - Refreshed release readiness docs for the app-owned support path and remaining store/contact warning. - Updated release guard tests and table constant tests for the support request queue. ## Why - Users need a working in-app support path even if the public support inbox still needs platform-review evidence. - Release checks should distinguish app-owned support capability from external inbox proof. ## Notes for Reviewers - Local evidence files already show Supabase smoke passing support request create/read/delete and release audit at 76 pass, 2 warnings, 0 failures. - Full Flutter test suite, analyzer, and Dart format check passed locally.
## Summary - Record the post-apply Supabase migration drift check as up to date. - Add the latest local full Flutter test, web build/smoke, Android debug build, and Wear debug build evidence. ## Changes Made ### Release Evidence - Updated the MVP launch readiness snapshot with post-fix verification results. - Kept the public support inbox as an external store/contact warning while the app-owned support queue remains verified. ## Why - The PR should carry the latest launch evidence for the in-app support request fix instead of stale pre-apply migration wording. ## Notes for Reviewers - Docs-only commit; no runtime code changes.
Iron-Mark
changed the title
## Summary - Refresh the release-status snapshot evidence for PR #15 at the current head. - Replace stale GitHub-variable audit counts with the current 77 pass, 2 warn, 0 fail result. ## Changes Made ### Launch Evidence - Updated the MVP launch readiness snapshot to include PR #15 mergeable and green-check status. ## Why - The launch handoff should not point reviewers at the older PR #13 failing snapshot after the support queue fix is green. ## Notes for Reviewers - Docs-only change; generated build evidence remains ignored.
## Summary - Remove a brittle exact PR head hash from the launch readiness snapshot row. - Keep the current PR #15 strict snapshot result and green merge state evidence. ## Changes Made ### Launch Evidence - Made the tracked evidence row stable across later docs-only commits while the ignored generated snapshot carries the exact head. ## Why - The tracked release note should not become stale every time a docs-only evidence correction lands. ## Notes for Reviewers - Docs-only change; no runtime code changes.
## Summary - Allow the GitHub Pages app-web deployment path to use the authenticated in-app support queue without requiring external support inbox proof. - Keep Android and iOS store artifact builds strict about verified support inbox evidence. - Update release docs and guard tests for the web-only support proof exception. ## Changes Made ### Release Gates - Added -AllowUnverifiedWebSupportEmail to the store release wrapper and wired it only into the Web target. - Changed the GitHub Pages workflow to emit a notice instead of failing when FLOWFIT_SUPPORT_EMAIL_VERIFIED is false. ### Tests and Docs - Extended release guard source tests to cover the web deploy workflow and support-proof messaging. - Updated release runbooks and launch evidence notes to distinguish app-web deploy proof from store submission proof. ## Why - The MVP support surface is now the app-owned support request queue, so Gmail or inbox proof should not block the deployable web app. - Store submission artifacts still need external contact evidence for marketplace review readiness. ## Notes for Reviewers - Verified the strict web path still fails without the new switch when FLOWFIT_SUPPORT_EMAIL_VERIFIED=false. - Verified the web build succeeds with the new switch while Android/iOS calls remain strict.
## Summary - Update current release handoff docs so app-web builds use the in-app support queue path instead of external inbox proof. - Keep Android/iOS store artifact guidance strict about -SupportEmailVerified. - Extend the release source guard to preserve the app-web/store submission distinction. ## Changes Made ### Documentation - Refreshed store checklist, metadata draft, script docs, and release runbook web commands. - Clarified that external inbox proof remains a store-contact artifact requirement. ### Guard Test - Updated source assertions to require -AllowUnverifiedWebSupportEmail for app-web guidance and retain explicit store proof wording. ## Why - The MVP support surface is the authenticated in-app support request queue, so current handoff docs must not steer app-web launch back to Gmail/inbox proof. ## Notes for Reviewers - Verified with Dart format, release guard source tests, stale-pattern scan, diff check, and strict store metadata verification.
## Summary - Refresh the MVP launch snapshot for PR #15 and the app-owned support queue path. - Replace stale missing-manifest claims with current app-web artifact build and verification evidence. - Keep Android/iOS store-upload artifacts and platform submission as separate external handoff items. ## Changes Made ### Release Evidence - Documented the clean app-web release wrapper run and strict artifact verification for build/web and the web release ZIP. - Updated evidence file descriptions and launch plan to match the current app-web MVP path. ## Why - The release snapshot should reflect that app-web artifacts are now generated and verified instead of claiming no artifact manifest exists. ## Notes for Reviewers - Avoided hardcoding a self-referential current commit SHA in the tracked doc; generated evidence files record exact commits.
## Summary - Remove the active mailto support action from Help & Support. - Keep the configured support email visible as passive public contact metadata. - Update route smoke, web smoke, profile docs, and release evidence wording for the primary in-app support flow. ## Changes Made ### Help & Support - Message Support is now the primary support action. - Report a Bug still opens the in-app support request dialog with a bug template. - Generic support submission failures now ask users to try again instead of falling back to an email workflow. ### Tests and Docs - Updated Help & Support widget coverage and route smoke expectations to use Message Support. - Updated web app smoke to verify the support route by Message Support. - Refreshed profile and launch-readiness docs to describe email as passive store/legal contact metadata. ## Why - The app-owned Supabase support queue is the release-ready support path, while public inbox proof remains a store/contact concern. ## Notes for Reviewers - Verified with Dart format check, Flutter analyzer, and focused Help & Support plus route smoke tests.
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
support_requests.Why
Verification
pwsh -NoProfile -File scripts\verify_dart_format.ps1flutter analyzeflutter testflutter test test\scripts\release_guard_source_test.dartflutter test test\screens\profile\help_support_screen_actions_test.dart test\app\flowfit_phone_app_navigation_smoke_test.dartRemote Status