Repository navigation
[iOS 1.0] Maintain the iOS changelog, release tracker, and versioned release notes #47
Description
Outcome
Maintain the iOS changelog, release tracker, and versioned release notes.
Release tracker: [iOS 1.0] First App Store release tracker
Acceptance criteria
- Add a mobile-specific changelog with Unreleased and dated shipped versions, user-facing Added/Changed/Fixed entries, and links to issues/PRs. Distinguish iOS releases from Windows/web versions and do not mark planned features as shipped.
- Add a mobile App Store release tracker modeled on CodexBar, with owners, prerequisites, checkboxes, artifact IDs/commit, evidence links, App Store Connect state, and explicit manual approval points.
- Store editable localized listing metadata, review notes, screenshot manifests, and release notes under the mobile workspace. Follow CodexBar's Fastlane-style file layout if using it; document the equivalent if using EAS.
- Maintain one checked mapping from marketing version to native build number, source commit, changelog, TestFlight testing notes, GitHub tag/release, and App Store version. Validate consistency before archive or upload.
- Prepare truthful first-release copy and a process for later App Store What's New text. Do not require an updates-only field on the initial submission if App Store Connect does not expose it.
- Create a reusable release checklist for QA, privacy/export compliance, screenshots, URLs, metadata previews, signing, TestFlight, review, publication, and post-release smoke checks.
Dependencies
Validation and completion
Run a dry release-note/version consistency check using the proposed 1.0 candidate. Every checked item has evidence; no skipped or future work is represented as complete.
Record the exact source revision, commands/artifacts, or sanitized App Store evidence as appropriate. Keep credentials and private contact/identity details out of this issue. Implementation changes must pass affected repository gates and receive review.
Activity
HemSoft commentedon Sep 27, 2026
Release records and a tested draft/release consistency guard are prepared in #56. Draft mode explicitly reports that the candidate is inconsistent; release mode rejects it. The real native candidate/version mapping and dependency #40 remain incomplete, so this is partial preparation rather than release sign-off.
HemSoft commentedon Sep 27, 2026
Mission completion blocker
The accepted native configuration/source/artifact mapping from #40 and later signed candidate, rather than only a proposed version.
Evidence and two self-serve paths checked:
Safe default: Land the useful release tooling and drafts, retain consistent:false, and keep this issue open until the real mapping and #40 dependency are accepted.
Owner action: Resolve #40's approved native identity/configuration and supply the accepted candidate evidence when it exists. No fabricated shipped version or date is needed.
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.
docs: prepare iOS release records and fail-closed candidate checks (#56)
HemSoft commentedon Sep 27, 2026
Preparation in #56 is merged at 36d567e. All current-head review findings were addressed; hosted validation and post-merge quality/security passed. Thirteen release-tooling tests cover draft, stale-source, copy-approval and image-receipt failures. The checker still correctly reports the real candidate incomplete. This issue remains open for the accepted native configuration and candidate mapping; nothing was signed, uploaded, submitted or published.
HemSoft commentedon Sep 27, 2026
Correcting an unintended automatic closure. GitHub interpreted the negated closing phrase in PR #56 as a closing keyword. The PR description now uses non-closing wording. The accepted native configuration and candidate mapping remain unqualified, as recorded above; this issue is open again.
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 signed candidate/source/archive and owner release mapping; draft-record refresh also needs required connected review.
Two self-service paths checked:
Safe reversible result: Keep the tracker, editable sources and Unreleased proposal. PR #62 stays open because Codex capacity was explicitly refused; no unsafe merge or fictitious release mapping.
Exact owner action: Restore required connected review capacity for PR #62, then provide approved configuration and accepted candidate receipts when the signed candidate exists.
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: Restore required connected review capacity for PR62, then provide approved configuration and accepted candidate receipts when the signed candidate exists.
This issue remains open. No signing/upload/private contact/legal declaration/hosting/TestFlight/submission/publication authority is inferred.