Release 1.9.0: daily reviews, complete History and easier refresh

[Muawiya-contact]

One Concept 1.9.0

Release develop → main, including #197, #198 and version preparation #199.

What’s new

• Daily review practice keeps learning useful when available new lessons are exhausted; reviews count toward streaks without inflating unique lessons learned.
• Complete History through bounded pages, with search across loaded lessons and cached pages available offline.
• Pull-to-refresh and accessible refresh buttons across learning screens.
• Clearer offline notices and profile details that remain readable at larger text sizes.
• A version-matched one-time What’s New card using the existing per-device dismissal.

Architecture and operations

Shared content supply extends beyond the initial catalog. Portable subject/curriculum definitions, editorial publication gates, durable generation claims and protected health reporting provide the foundation for future subjects. Existing five subjects remain in use. New content still requires curriculum planning and editorial approval.

Merge readiness

• Local production export created; archive index is readable. Full restore remains untested and cloud restoration was deferred by the owner.
• Owner reports generation paused; production migrations 0011–0015 independently verified and recorded through release: record verified 1.9.0 production migrations #201.
• fix: verify backend rollout before publishing production OTA #202 separates Railway deployment from mobile publication and tests the revision guard. The release has a matching 1.9.0 What's New card and retains runtime 1.3.0.
• Required human approval and owner decision to merge main. No production merge is performed by this preparation.

After the owner merges

1. Railway auto-deploys main; keep generation paused until the API and workers run the new main revision.
2. Verify deployed commit, API health and daily learning/review behavior. Native gestures, large-text/device checks remain manual acceptance work.
3. Run Actions → Release → Run workflow, select main, and provide the full verified commit SHA as backend_revision. This confirms operator verification; the workflow does not query Railway health itself.
4. The guard checks main/ref/revision before publishing production and preview OTA, then creating the release and dispatching the native-gated APK workflow. Do not merge another release during publication.

Merging this PR deploys the backend but does not automatically publish the mobile update. Follow RELEASING.md and docs/CONTENT_OPERATIONS.md. The backup was not restored or uploaded; migrations updated the existing production database directly.

Validation

Release preparation: Node 24 typecheck, all 39 unit tests, Android/iOS/web exports and whitespace checks passed. #198’s corrected History browser contract passed 120-record paging, retry, offline restart/detail and sign-out fencing. #197 records backend PostgreSQL/concurrency/year-of-learning coverage; those backend tests were not rerun for the version/card-only preparation. Nine release-guard cases, shell syntax and workflow YAML/wiring checks passed. Physical-device checks remain outstanding.

App version 1.9.0; native runtime remains 1.3.0. Preserve all commits with a merge commit. Railway deploys main automatically; mobile release publication is a separate verified dispatch.