Skip to content

docs: define Android modernization and staged delivery plans - #1

Open
MphoCodes wants to merge 6 commits into
mainfrom
codex/android-modernization-spec
Open

MphoCodes wants to merge 6 commits into
mainfrom
codex/android-modernization-spec

Conversation

@MphoCodes

@MphoCodes MphoCodes commented Oct 19, 2026 •

Copy link
Copy Markdown
Owner

AceTimeTracker's timer, manual timesheets and progress screens use disconnected data contracts. This documentation defines the general personal-goals direction, incremental Compose migration, data-preservation/reminder contracts and one-PR-per-task delivery sequence. iOS remains deferred.

The owner approved the Android product/technical specification and P1 plan on 19 October 2026. P1's two assigned deliverables are now verified and ready for review/integration:

Final P1 settings are compile37/target36/min27. Independent exact-head review found no confirmed code blockers. Lint retains204 warnings and0 errors, including legacy native-GIF alignment warnings for release-stage review. Authenticated Timesheet focused-field visibility was not verified without credentials and remains explicit in PR#5; P2's isolated harness now names the follow-up check. These checks do not claim the product redesign, account/data/timer correctness or full release validation complete.

The P2 plan is proposed for owner review; its implementation has not started. It creates two PRs: (1) authenticated routing, idempotent profile bootstrap and session guards, then (2) reliable profile/photo editing and verified sign-in-email changes. It includes a default-Firebase demo harness, meaningful fake/emulator tests, preserved legacy root fields, explicit Keep/Set profile patches and abandoned-auth-attempt reconciliation. P2 waits for plan review; the full Android goal continues through P11.

Validation:

  • Whitespace, local Markdown targets, code fences and placeholder checks passed.
  • P2 dependency/CLI/runtime artifacts and OOB behavior checked against publisher metadata/tagged source; no P2 build is claimed.
  • Plan self-review and independent review findings addressed.
  • A git merge-tree simulation combined docs with the verified Task2 head (which includes Task1) without conflict; the diff from the verified code consists only of docs. No branch/index/checkout/PR merge occurred.

Docs head: 14961a2ca36a09bc5257fd63dcb5e9b8141ed2f4. Review/integration order: #1, #4, #5, rechecking bases at integration time. All remain open/unmerged. No production-service change or publication.

@MphoCodes MphoCodes changed the title docs: define Android modernization scope and staged PR roadmap docs: define approved Android modernization scope and P1 plan Oct 19, 2026
@MphoCodes
MphoCodes marked this pull request as ready for review October 19, 2026 09:48
@MphoCodes MphoCodes changed the title docs: define approved Android modernization scope and P1 plan docs: define Android modernization and staged delivery plans Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant