Maintain validation and surface-capture loop
How Maintain turns native iOS and backend work into reviewable evidence: regenerate the Xcode project, run simulator surface capture, verify docs/backend/iOS gates, check staging when credentials are available, and keep TestFlight/App Store blockers explicit before release decisions.
Workflow steps
- 1
Select the source revision and environment that will define the release or review candidate
Decision
- 2
Regenerate Maintain.xcodeproj from XcodeGen so simulator evidence matches the current source tree
Action
- 3
Run the AppSurfaceCaptureUITests harness to export sign-in, onboarding, Home, Log, Trends, Activity, Profile, and export-state screenshots
Action
- 4
Run docs, backend type/check/test, and route-contract smoke gates appropriate to the change scope
Process
- 5
Run iOS build, unit, snapshot, UI, surface-capture, and runtime-smoke lanes before marking app work ready
Process
- 6
When staging credentials are available, run staging drift and deployed staging auth/API smoke before device or TestFlight sign-off
Action
- 7
Human operator reviews health-adjacent wording, screenshots, blocker state, and whether the evidence represents local or origin state
Decision
- 8
Keep TestFlight/App Store release blocked until App Store Connect access and production API/Worker reachability are verified
State