Repository navigation
[iOS 1.0] First App Store release tracker #38
Description
Goal
Ship the first public iPhone/iPad release from this monorepo using the existing Expo/React Native app and shared TypeScript game rules. Proposed baseline: offline local play, native local persistence, no account or Convex dependency, and no unapproved commerce/analytics features. The scope issue owns final decisions.
Reference and current state
Use CodexBar APP-STORE.md, CodexBar CHANGELOG.md, CodexBar PRIVACY.md, CodexBar SUPPORT.md, versioned metadata, screenshot capture, native QA, and review evidence as the release standard. Adapt the release/support package, not CodexBar's provider, widget, or Watch features. Do not copy its privacy, encryption, pricing, age-rating, or rights declarations.
The existing mobile app still uses Convex, lacks complete native release assets/configuration, and has not been qualified as a signed iOS release. Recent engine, desktop-offline, and redesign work is present in the local dirty checkout at base 3487c64; the baseline issue must review and land the relevant work before depending on it. Existing repository audit issues were checked; they are closed and are not being reopened or duplicated.
Release rules
- Each child owns acceptance criteria and validation evidence. Dependencies are completion prerequisites; drafts and discovery can run in parallel where safe.
- Native simulator/device/TestFlight evidence is required. Expo JavaScript export and the mobile web adapter do not prove App Store readiness.
- Store marketing page and a public marketing/support/privacy website are separate deliverables.
- Keep Apple credentials, identity documents, private review/tester contacts, payment information, and secrets out of GitHub. Owner approval is required for legal/commercial decisions, spending, external invitations, submission, and public release.
- No release date, price, app name, or broad accessibility/privacy claim is assumed. Recheck Apple upcoming requirements and Apple submission requirements at submission.
Work breakdown
1. Decisions and foundation
- [iOS 1.0] Confirm first-release scope, public name, and brand rights
- [iOS 1.0] Establish the mobile release baseline and reproducible native iOS configuration
- [iOS 1.0] Create the app record and complete account, pricing, and regional setup
- [iOS 1.0] Maintain the iOS changelog, release tracker, and versioned release notes
2. App implementation
- [iOS 1.0] Ship offline mobile gameplay with durable saves and resume
- [iOS 1.0] Build the iPhone and iPad gameplay interface and accessibility
- [iOS 1.0] Add in-app rules, About, support, privacy, and review destinations
- [iOS 1.0] Create licensed iOS app icons, launch assets, and brand files
3. Release engineering and compliance
- [iOS 1.0] Automate native iOS checks, distribution signing, and reproducible archives
- [iOS 1.0] Audit privacy, native SDK manifests, permissions, and export compliance
4. Storefront and public information
- [iOS 1.0] Publish a marketing landing page, support site, and privacy policy
- [iOS 1.0] Prepare and preview the complete App Store product page and localized metadata
- [iOS 1.0] Automate App Store screenshots and produce approved marketing captures
5. Beta qualification
6. Review and first release
- [iOS 1.0] Complete App Review preflight, submit the first version, and track approval
- [iOS 1.0] Publish the approved release and verify the live store, support, and changelog
Start here
Start with [iOS 1.0] Confirm first-release scope, public name, and brand rights and [iOS 1.0] Establish the mobile release baseline and reproducible native iOS configuration. Prepare [iOS 1.0] Maintain the iOS changelog, release tracker, and versioned release notes and [iOS 1.0] Create the app record and complete account, pricing, and regional setup after those decisions. Gameplay/UI and release engineering can then proceed alongside content preparation. TestFlight does not wait for final marketing screenshots, but public submission requires the accepted beta, complete storefront, and compliance evidence.
Definition of shipped
- All child issues and release-blocking defects are resolved with evidence.
- Owner-approved product name, rights, scope, price, availability, and legal declarations are recorded.
- The exact accepted signed build is approved and publicly available.
- A store-installed build works offline on iPhone and iPad and preserves local saves.
- Public product page, website, support/privacy links, versioned changelog, and matching source release are verified.
Milestone: iOS 1.0
Activity
HemSoft commentedon Sep 27, 2026
Mission completion blocker
Completion of the owner-gated native release and public-store verification, not just repository PR merges.
Evidence and two self-serve paths checked:
Safe default: Retain the tracker and milestone open with each unmet child and exact next action. Repository preparation is not an App Store release.
Owner action: Start with #39 identity/rights and #43 authorized Apple/account decisions, then enable device qualification. Remaining native implementation and delivery must resume against those decisions.
This is a blocker to this issue's full acceptance contract, not a claim that its unfinished implementation is complete. Repository-only preparation continues through the linked PRs; this issue stays open.
HemSoft commentedon Oct 1, 2026
Updated acceptance blocker, October 1, 2026 EDT
This supersedes the September 27 preimplementation assumptions. Native local saves/resume/UI, original development assets, unsigned CI and packaged privacy inspection are now delivered. The static companion site is prepared but unpublished. Screenshot and release/reporting preparation exists in the open PRs, not as accepted store material.
Native foundation #57 and postmerge delivery, unpublished site #58, draft capture preparation #61, and draft release/reporting preparation #62. The last two PRs remain open; connected review capacity was explicitly refused on #61 and on #62. No purchase or substitute reviewer was used.
Remaining need: Accepted owner-gated signed/public release and its remaining children, not just repository preparation.
Two self-service paths checked:
Safe reversible result: Keep tracker/milestone open with completed engineering distinguished from full release acceptance. Neither unsigned simulator success nor a clean draft is public shipment.
Exact owner action: Start with issue #39 identity/rules/rights and issue #43 authorized account/legal decisions. Restore the required reviewer capacity, then enable signed physical qualification and explicit TestFlight/submission/publication approvals.
This issue remains open. Simulator, browser, fictional-fixture and unsigned evidence do not replace signed physical-device or legal/publication acceptance. CI waits and driver failures are still engineering work, not the owner block stated above. No credentials, private contacts or legal declarations are requested in this public issue.
HemSoft commentedon Oct 1, 2026
Final engineering checkpoint
PR63 at9f33686 and PR62 at9a97876 each passed current required checks and source-bound unsigned native qualification, with1,049 verified files, ten exact resumes/eight games/two empty resets. Original failures remain retained; one independent fresh failed-group retry passed for each source. Root qualification and stacked qualification are engineering evidence, not signed/physical/legal/store acceptance.
Current mandatory connected review explicitly refused root capacity and docs capacity. No substitute, purchase or unsafe merge. PR62 must not merge into its temporary base.
The final live revisit found no owner approval. Two checked routes and missing authority are documented in the earlier acceptance-blocker comment. Exact remaining human action: Start with #39 identity/rules/rights and #43 authorized account/legal decisions. Restore the required reviewer capacity, then enable signed physical qualification and explicit TestFlight/submission/publication approvals.
This issue remains open. No signing/upload/private contact/legal declaration/hosting/TestFlight/submission/publication authority is inferred.
HemSoft commentedon Nov 11, 2026
Held: this step needs App Store Connect access for Third Roll, which the repository doesn't have and an agent can't obtain without a new login.
Checked on 2026-11-11 (merge mission, Chief dispatch 022804d6):
The repository-side preparation for this item is on main (release records, metadata drafts, screenshot automation, privacy audit, unsigned archives). Nothing here spends money or needs a new account, but it does need Franz's App Store Connect session, so later sweeps should skip this issue until that access exists.