4.0.0
Released
Features
The mobile app keeps a tick made offline: a task's status (Today's cycles, Due this week, the task list's button and swipe), an answer's pin and marking notifications read now work with no connection, show at once with a small "Waiting to sync" mark and a count on the offline banner, and are sent in order when the connection returns. Each is written only if nothing changed it meanwhile — otherwise the other change stands and a toast says so — repeated taps on one task are sent as one change, a change already sent locks its task or pin until the server answers so a lost reply can never lose a later tap, a change over a week old is dropped with a note, and signing out with changes still waiting sends them first or asks before discarding them (#1027).
The mobile app works offline for the daily loop: Today, the Quests tab, a quest's page and the Tasks tab keep what they last read on the phone, show it with no connection under an "Updated 3 hr. ago" line, and read again as soon as the connection returns. A banner says you are offline, and every action that needs a connection — saving a quest or task, a status tick, an upload, a comment, an invitation, a setting — is turned off with "Needs a connection" rather than failing; a screen with nothing saved says so instead of spinning. What the phone keeps is the signed-in account's own quests and tasks, never the Inbox or an investigation's answers, and it is wiped at sign-out (#1027).
The mobile app has its icon, Android adaptive icon and splash screen, the same scroll-and-sparkle mark as the web's browser tab (#1026).
With the mobile app installed, questify.co links open it: quests, tasks (including a link to one task), the Today tab, notifications, settings, profile and recaps, Year Themes, Quest Packs, Challenges, Quest Jams, Guilds, party and guild invitations, and the confirm-your-email and reset-password pages. A link opened signed out signs in and then lands on its screen. The landing page, pricing, legal pages, patch notes, admin, the web's sign-in flows, shared Chronicles and recaps, and email unsubscribe links still open the browser, and without the app every link opens the web as before (#1025).
The mobile app carries a quest's files: the quest's own attachments above its task list and a task's in its sheet (with a paperclip chip on the task's row), listed with a thumbnail, size and who added them. Any party member attaches a file from the phone's files or a photo from its library — a photo is saved again without its location tag before it is sent — within the same types and 10 MB the web allows; a picture opens in the app and any other file in the phone's browser sheet on a short-lived link; the uploader and the quest's owner can remove one. Asking the AI about a task can now tick the task's files and the quest's into the question, each priced as a link is, and an answer names the files its question carried ("Attached: site-map.pdf"), or "a removed file" for one deleted since (#1017).
The mobile app takes attendance on a quest that completes when everyone checks in: the quest page shows how many of the party have confirmed, each member's check-in and note, and lets you check yourself in — or, as the owner, a member without an account or one who has left the guild — once the quest has started. Another member's check-in appears live, the last one completes the quest, and "Mark Complete" is not offered until then, as on the web (#1017).
Confirming attendance on the web now says why it was refused — the quest is not available, does not use attendance, has not started yet, or that member is not yours to confirm — instead of one generic line for every refusal (#1017).
The phone's New Quest has the AI Quest Coach behind
EXPO_PUBLIC_FEATURE_COACHING_MODE: "Draft it for me" turns a title into a draft that fills the form for review, with the coach's tasks and their details, and a routine becomes the recurring Quest form (with "Create it once instead") when recurring Quests are on, created with the draft's persona. A refusal shows in the route's words, and a substituted model is named with what was charged (#1018)The phone's New Quest has the AI Coach's interview: "Start interview" (or "Suggest a quest for my theme") opens a full-screen interview that asks one question at a time, with earlier answers editable as corrections, "Looks good / Change it" under a proposed list, "Draft it now", Start over, and Continue filling the one-off or recurring form; "Ask for changes" continues the same interview, charged once, and "Try the interview instead" follows a draft that failed (#1018)
The mobile app's Inbox tab lists your notifications behind
EXPO_PUBLIC_FEATURE_IN_APP_NOTIFICATIONS, newest first with older ones loaded as you scroll, in the web's words, with an unread badge on the tab that rises while the app is open. A notification stays unread until you tap it — which opens its quest, or the Today tab for a weekly review — or press "Mark all read"; a deleted quest and a Year Theme check (not on the phone yet) say so instead (#1019).Behind
NEXT_PUBLIC_FEATURE_PUSH_NOTIFICATIONS, the worker sends push notifications through Expo beside every email it sends, and for the weekly AI review, the theme check and an investigation's answer, and Settings → Notifications gains a push switch per category. A finished investigation now also appears in the notification bell and the phone's Inbox, linking to the task's answers. Phones register with the app in #1020's second part (#1020).Behind
EXPO_PUBLIC_FEATURE_PUSH_NOTIFICATIONS, the mobile app receives push notifications: after the first quest made on the phone it offers push once per account, with the system prompt shown only after "Turn on"; a tapped push opens the quest, the task's answers, Today or the Inbox, whether it launched the app or found it open; Android lists one notification channel per kind; the app icon's badge follows the unread count; and signing out stops the phone hearing that account. The You tab gains Settings → Notifications, with this phone's state and the one thing to do about it (Turn on, Turn off, or Open settings when the system refused), a push switch per category, and the timezone and quiet hours every push waits for (#1020).The mobile app manages a Party Quest: on the quest page the owner invites by email (with the link to share when the email could not be sent), resends and withdraws pending invitations, removes a member, brings a guild's roster in and hands the quest over, each irreversible step behind a confirm, and a member leaves the party; while an attendance quest's roster is fixed only the handover is offered, as on the web (#1021).
A party invitation link opens in the app at
questify://party-invites/<token>, with the web page's words for every state: someone signed out signs in or creates an account with the invited address — with a password or Google, Facebook or Apple — and comes straight back to the invitation, through the confirmation email too; someone signed in as another address is offered to sign out; the invited account joins and lands on the quest (#1021).The mobile app has Guilds behind
EXPO_PUBLIC_FEATURE_GUILDS, from the You tab: the list in the web's three groups (accept or decline an invitation, leave a guild after a confirm), a new guild opening ready for its people, a claim code linking an account to its roster place, and a guild's page — the roster with its former members folded away, and for the owner adding people by email or by name (or, with email invitations off, inviting an existing account in-app), a roster place's own email invitation, claim codes shown once with Share, handing the guild over and removing a member each behind a confirm, withdrawing a pending invitation, renaming, and deleting once the guild's name is typed. A guild's push now opens its page (#1021).A guild invitation link opens in the app at
questify://guild-invites/<token>with both guild flags on, in the web page's words for every state, saying first when accepting claims a roster place; signing in or up from it comes back to it, as from a party link (#1021).The mobile app has Discover in the Quests tab: public quests to browse with the web's search, status chips, three sorts (Most progress included) and numbered pages, each copied into your own quests from its card or its page; a public quest's page lists its related quests with
EXPO_PUBLIC_FEATURE_SEMANTIC_SIMILARITYon; and the Quest Packs catalogue, with search, categories and a preview, whose Start this Quest opens New Quest with the pack chosen, its name and description filled in (#1022).The mobile app's Discover adds Challenges and Quest Jams: today's and this week's challenge to start or continue, with History's tabs and pages; the Quest Jam index with Live, Upcoming and Mine and a one-tap Join on each card; a Jam's page with its countdown, the join panel and the leaderboard (your position, Show all, and who has not finished); and Start a Jam, with a preview of its card. A Jam joined on the phone is on the web's leaderboard (#1022).
The mobile app's You tab has the web's settings: Profile with your picture (chosen from the photo library, cropped square and stripped of its metadata) and display name, Appearance (light, dark or your phone's, applied at once and saved to your account), Notifications with every email switch by the web's flags, quiet hours, the weekly AI review and the theme check alongside push, and
/profilewith your stats and every badge (#1023).The mobile app's You tab has Account and Billing. Account changes your password (with the emailed code when your session is old), hands a copy of your data to the phone's share sheet as the same JSON file the web downloads, and deletes your account through the web's flow — what blocks it, an optional reason, your email typed back — then signs the phone out. Billing, behind its flag, shows your plan, its status and renewal date, and what Pro includes, read-only: it shows no price and offers no purchase or link (#1023).
The mobile app has Year Themes: this year's theme with its progress, setting and editing it with the named swatches, Create a quest for this theme, its tagged quests and past years' themes in the Quests tab, and, with the theme AI on, the quest slate and the quarterly theme check, which re-reads while it is being written. The Today tab's theme card and a theme-check notification now open it in the app (#1024).
The mobile app has the Well Played recap:
/profilenow shows the Year Theme cards and a button per recap year (this year's marked New until opened), and each opens the year's recap — the stats, active days by month, the year's badges, the quests finished and the highlights, recomputed on every open and pull, with the earlier and later years beside it. Share recap hands the public recap web page to the share sheet under your display name, never your email, and Stop sharing retires the link (#1024).The mobile app reads a quest's Chronicle aloud behind
EXPO_PUBLIC_FEATURE_CHRONICLE_LISTEN: Listen plays the narrator's reading when one has been written, which keeps playing with the phone locked or another app open and shows on the lock screen with Play and Pause, and otherwise the phone's own voice reads it sentence by sentence; the sentence being read is highlighted, a pending reading is checked for every 15 seconds, a file that will not play hands over to the phone's voice, and "Phone voice" switches voices mid-story from the same sentence (#1024).
Fixes
A refused Year Theme save on the web showed the database's error text; it now says the theme could not be saved, or that only this year's theme can be changed (#1024).
Security
GET /api/me/exportaccepts the mobile app'sAuthorization: Bearertoken as well as the session cookie, through the shared request client, and refuses with the shared{ error, code }body; a Bearer token that does not verify is a 401 even with a cookie present (#1023).
Technical changes· 72 entries for database, tooling, CI, tests and docs
Database
quest_attendancejoined thesupabase_realtimepublication, so the mobile app hears a party member check in — and the quest completing on the last check-in — instead of waiting for a refresh; its only read policy keeps each event to the quest's owner and party, even on a public quest, andsupabase/tests/realtime_publication.sqlpins the publication's exact list (#1017).notificationsjoined thesupabase_realtimepublication, so the mobile Inbox and its tab badge hear a notification arrive — or one marked read on another device — without a refresh; its only read policy keeps each event to the person it is for, and the web bell is unchanged (#1019).Push notifications got their schema:
push_tokens(written only throughregister_push_token(), which moves a token that changed hands and keeps ten per person, anddetach_push_token(), which removes a named token from whoever holds it),push_ticketsfor receipts, one*_pushpreference per category backfilled from its email setting, apushchannel beside the email on the deadline reminder, event reminder, weekly digest, stall digest and email outbox queues with a push claim each, andnotification_push_deliveriesfor the weekly AI review, the theme check and the newinvestigation_finishednotice, which is written when an investigation someone asked finishes. A push is never sent twice, waits for quiet hours, and is written only for someone with a registered phone;export_my_data()lists the phones but never their tokens (#1020).
Tooling & Configuration
The mobile app names its Expo organization (
owner: questify-12529572-canada-incinapps/mobile/app.json), so EAS builds, submissions and updates go to the organization'squestifyproject rather than whichever personal account the CLI is signed in as;docs/mobile/release.mdsays where the project id and the CI robot token come from (#1026).apps/mobiledeclares@babel/plugin-transform-react-jsxitself: NativeWind's Babel preset names that plugin as a string, which Babel resolves from the app's own folder, so a release build's bundle step failed wherever pnpm had not hoisted it (#1028).The worker answers every investigation with a fixed stub when
AI_E2E_STUB_ANSWERSis on, through the real claim, credit and Realtime path, so the mobile end-to-end flows can watch an answer arrive without a provider; it refuses to start with the flag against anything but a local Supabase.pnpm --filter mobile e2estarts a second local stack beside the developer's (projectquestify-e2e, every port moved up by 1000, the web app on 3100 and the stubbed worker), makes release-style builds for the iOS simulator and an Android emulator without touchingapps/mobile/.env.local, runs the Maestro flows and stops everything (#1028).The mobile app reads Today, the Quests tab, a quest's page and the Tasks tab through TanStack Query (
@tanstack/react-query, with@tanstack/react-query-persist-clientand@tanstack/query-async-storage-persister), one client per account undersrc/offline/query-provider.tsx, saved to@react-native-async-storage/async-storagewith the four families opted in, quest pages capped at 20, a seven-day age and a buster of the cache schema, app version and update id;@react-native-community/netinfodrives TanStack'sonlineManageranduseIsOnline(), andButtongainsrequiresNetwork. Both native modules change the fingerprint, so they need a new build. Jest maps TanStack to its CommonJS builds and installs AsyncStorage's mock andtest/fake-network.ts(#1027).The mobile app is set up for release:
apps/mobile/eas.json(development, preview and production profiles, build numbers kept by EAS, production submitting to Play internal testing),expo-updateswith afingerprintruntime version and an update URL only when the build names an EAS project, the@sentry/react-native/expoplugin and Sentry's Metro serializer (debug IDs), Sentry releases namedquestify-mobile@<version>+<build>with the build asdistand the EAS profile as environment (EXPO_PUBLIC_SENTRY_ENVIRONMENT), andexpo-splash-screen,expo-updatesandexpo-application;apps/mobile/scripts/render-icons.mjsrenders the icon set from the web'sicon.svg(#1026).The web serves
/.well-known/apple-app-site-associationand/.well-known/assetlinks.jsonfrom the newAPPLE_TEAM_IDandANDROID_CERT_SHA256values (404 until set or when malformed), outside the middleware; the allowlist they publish is@questify/core/links/app-links, which the app'sapp.json(associated domains and a verified intent filter), route map and incoming-link rewrite (app/+native-intent.tsx) read too (#1025).The quest attachment rules moved whole from
apps/web/src/lib/attachments/attachments.tsto@questify/core/attachments/attachments— the bucket's limits, types and path, the select, the row mapping and the record schema — with the grouping by task, the choice of which rows get a thumbnail URL and the files a question may point at added as pure helpers; the web re-exports it and itsqueries.tskeeps only the client call.investigationAttachedLine()joined@questify/core/ai/investigation-card. The mobile app addsexpo-document-picker(no permission, no config plugin) and theEXPO_PUBLIC_FEATURE_ATTACHMENTSmirror ofNEXT_PUBLIC_FEATURE_ATTACHMENTS(#1017).New
@questify/core/quest-attendance/attendanceholds the attendance rules both clients share: the confirm schema (moved fromapps/web/src/lib/quest-attendance/validators.ts, which re-exports it), the select, the panel's words, when check-ins are open, whether attendance holds back completion, anddescribeAttendanceError(); the web's panel, quest page and action use it (#1017).What a client does with an AI Quest Coach draft — a routine's description, the recurring form's defaults, the card's and hand-off's words, the fallback notice, and when a failed draft offers the interview — moved to
@questify/core/ai/coach-draft, which the web's coach components now read;EXPO_PUBLIC_FEATURE_COACHING_MODEmirrorsNEXT_PUBLIC_FEATURE_COACHING_MODE(#1018)Reading an AI Coach reply (the draft withheld and normalized, question or proposal, its lists) moved to
@questify/core/ai/coach-reply, the JSON payload scan to@questify/core/ai/json-payload, and the interview's openings, corrections, answered-turn pairing, progress and words to@questify/core/ai/coach-interview; the web's coach module and chat read them from core (#1018)The notification inbox's shape, columns and row mapping moved from
apps/web/src/lib/notifications/inbox.tsto@questify/core/notifications/inbox, joined by each kind's sentence and where it leads (describeNotification(), which the web's notification item now renders), the unread badge and its label, and the words; the web's relative time ("3 hr. ago") moved to@questify/core/dates/relative-time, with a short English fallback whereIntl.RelativeTimeFormatis missing.EXPO_PUBLIC_FEATURE_IN_APP_NOTIFICATIONSmirrors the web flag in the app (#1019).The worker reads
NEXT_PUBLIC_FEATURE_PUSH_NOTIFICATIONS(copied from Vercel by the release workflow), the optionalEXPO_ACCESS_TOKEN(in.env.example, the worker env and the dev TUI's managed keys),PUSH_POLL_INTERVAL_MSandPUSH_RECEIPT_INTERVAL_MS; the push switches' list, words and parser are@questify/core/notifications/push-preferences, and the outbox email payload schemas are exported for the push messages (#1020).The mobile app adds
expo-notifications(its config plugin with no background delivery) andexpo-device, the publicEXPO_PUBLIC_EAS_PROJECT_ID(read insrc/env.ts, copied toextra.eas.projectIdbyapp.config.ts, and written bypnpm dev:tui -- mobile-envfrom the root.env), and thePUSH_NOTIFICATIONS,EVENT_REMINDERS,DEADLINE_REMINDERS,WEEKLY_DIGEST,PARTY_EMAILS,TASK_ASSIGNMENT_EMAILS,GUILD_INVITESandYEAR_THEME_AIflag mirrors. New@questify/core/notifications/push-channels(the Android channels, which the worker's names are now tested against) andnotifications/push-device(the phone's push states and the primer's words), andparseDeliverySettings()is the timezone-and-quiet-hours half of the web's notification form parser, now shared with the phone (#1020).The party invitation rules both clients use moved to
@questify/core/party-quests/invitations(the token, the pending-invitation select, the preview's mapping, the error passthrough and the link page's words) and the newparty-quests/panel(who sees which party control, the roster lock, and the invite, guild and handover messages); the web's panel, actions and invitation page read them from core. Local Supabase Auth allowsquestify://auth/callback?next=**, so a sign-up started on an invitation link returns to it; the hosted project needs the same redirect URL (#1021).The guild rules both clients use moved to
@questify/core/guilds/*:validators(moved whole from the web),invitations(the token, the pending select, the preview's mapping, the error passthrough and the link page's words),roster(the row shapes, the list's groups, the roster split, each row's actions and the remove and leave prompts) andcopy(every guild write's message and the screens' words). The web's guild actions, components and invitation page read them from core, unchanged (#1021).The public quest catalogue's URL contract moved to
@questify/core/quests/public-index, with the progress ranking, status chips and page words beside it, and the Quest Packs filter to@questify/core/quest-packs/cataloguewith the catalogue's named columns and words; Copy to my quests' words arequests/copy-public. The web's catalogue, cards, related list, pack browser and copy action read them, unchanged. The app mirrorsNEXT_PUBLIC_FEATURE_SEMANTIC_SIMILARITYasEXPO_PUBLIC_FEATURE_SEMANTIC_SIMILARITY(#1022).Challenge periods, the daily and weekly pick, the named columns and History's URL contract and paging moved to
@questify/core/quest-challenges/challengesandhistory; the Quest Jam window, countdown, leaderboard lines, index filter and validators to@questify/core/quest-jams/jams,index-filterandvalidators, with the start, join and refusal words of both. The web's challenge and Jam pages, cards, panels and actions read them, unchanged. The guild screens' focus read moved toapps/mobile/src/data/use-focused-read.tsfor the new screens to share, and keeps a refresh's previous result only for the same read, so a new tab or page that fails says so (#1022).The avatar upload rules, the profile and theme schemas and their words, the badge catalogue and gallery, the email preference row and switch words, and the weekly review and theme check settings moved to
@questify/core(profile/avatars,profile/settings,achievements/*,notifications/email-preferences,weekly-review/settings,year-themes/alignment-setting); the web's settings pages, forms, actions and profile page read them, unchanged (#1023).The billing vocabulary and plan features (
billing/plans, moved whole with its test), the subscription summary and renewal line (billing/subscription), the export file name, the deletion blockers and every account-settings and change-password word moved to@questify/core(account/*,auth/change-password); the web's account and billing pages read them unchanged. The app addsexpo-sharingand anEXPO_PUBLIC_FEATURE_BILLINGmirror; a dev build made before this must be rebuilt (#1023).The Year Themes hub's split and words, the theme form's words and refusals, the slate's words and refusals, and the quarterly check's types, headline, card state, verdict offers and words moved to
@questify/core(year-themes/hub,form,slate,alignment); the web's hub, form, editor, slate, check card and actions read them unchanged (#1024).The Well Played recap's rules (row mapping, badges, months, years, share path, names, named columns) and words moved to
@questify/core(recap/recap,recap/copy), and Chronicle narration's planning, timing, voice choice, pending poll and Listen words toquests/narration; the web's recap page, card, chart, year navigation, share controls, profile page, reading view hooks and voice toggle read them unchanged. The mobile app addsexpo-audio(playback only: no microphone string, noRECORD_AUDIO, no background recording; iOS background modeaudioand Android's media-playback foreground service) andexpo-speech(#1024).
CI/CD
.github/workflows/mobile-e2e.ymlruns the mobile Maestro flows on the self-hosted Mac nightly ondevelop, by hand, and on a pull request labelledmobile-e2e, one run at a time and with no secrets; a preflight lists everything the Mac is missing in one message, and a failed run keeps its JUnit reports, screenshots and logs. It is not a required check (#1028).The E2E job no longer fails when the runner's Ubuntu apt mirror cannot be reached: Playwright's browser download and its system packages are separate steps, the packages are retried, and if apt still fails the job continues with the runner image's packages (only fonts were missing) under a warning (#1103).
.github/workflows/mobile-build.ymlasks EAS for production builds of the mobile app on a release merge tomain— submitted to TestFlight and Play internal testing onceMOBILE_AUTO_SUBMITis set — publishes the release's JavaScript as an over-the-air update and uploads its source maps to Sentry, and builds a preview for a pull request labelledmobile-buildor on demand; every job stands down until the EAS project exists (#1026).CI's build job now exports the mobile app and checks the bundle (
apps/mobile/scripts/check-bundle.mjs): it fails on a provider or Stripe key, a JWT whose role is notanon, a server-only secret's name, a model id or the AI Coach's prompts, read as bytes, UTF-8 and UTF-16, and refuses a missing or empty bundle (#1018)The mobile bundle check no longer depends on how Hermes happens to pack its strings:
@sentry/conventionsshipsgpt-4-turbo-previewas an attribute example, which matched only when the string before it ended in punctuation, so it is now excused as that exact literal (DEPENDENCY_LITERALS) while every other model id still fails the build (#1021).
Tests
Maestro end-to-end flows cover the mobile app's critical paths on a real build: sign-up through the confirmation email and every onboarding step, sign-in, ticking a task on Today, New Quest, an Ask answered through the worker and Realtime, the deep links a push opens, accepting a Party Quest invitation signed out, and deleting an account, each followed by a check on the database.
e2e/flows.test.mjs, inpnpm --filter mobile test, fails when a flow's text, id or variables stop matching the app, so a renamed label fails its own PR (#1028).The web task list's "opens the next Quest's completed group after a switch" test now waits for the group and the hit's answers to open, rather than asserting the render after the new Quest's tasks arrive, which failed intermittently on a loaded CI runner (#1103).
The mobile app's replay queue is covered by
queue.test.ts(coalescing, order, expiry, the overlays, a replay stopping at the first change with no answer, which stays locked, and a sent change locking its task or pin),replay-writes.test.ts(the compare-and-set applied, a conflict, a refusal, no answer; a pin set again after the tap; Mark all read up to its moment),queue-store.test.ts,sign-out.test.tsandsync-copy.test.ts, and on screen by a tick made offline sent as one change on reconnect, two ticks sent in the order made, a conflict put back with its toast, and a queue restored after a restart with a week-old change dropped (#1027).The mobile app's offline suite restores what an earlier session saved and renders Today, the Quests tab and a quest's page with the network off, then checks the reconnect read, the nothing-saved state, a refresh that fails, a Today read that reaches nothing, a stale bundle, the sign-out wipe and a status tick turned off;
persistence.test.tscovers the saved families (a failed refresh saved as its last answer), the 20-page cap, the buster and the wipe, a Return in a field offline sends nothing, andonline-only.test.tsfails on any screen or component that imports a network action without turning its control off offline (#1027).The mobile config test holds the app's version to the root
package.json, refuses build numbers inapp.json, and checkseas.json's profiles, channels and Sentry environments, the fingerprint policy, the update URL with and without a project, the icon, splash and Sentry plugin; an asset test checks the icon set's sizes and that the iOS icon is opaque; the workflow tests pin the mobile build's triggers, label gate and production-only update and submit;apps/mobile/scripts/eas-build-summary.test.mjschecks the job summary's build links against eas-cli 26's--jsonoutput and that it never fails the run (#1026).Core suites cover the allowlist, both association files, the intent filter data and the console-value parsers; web suites cover both files configured, unset and malformed, the middleware leaving them alone, no Vercel or Next redirect reaching them, and the redirects case; the app's suites hold
app.jsonand the route map to the allowlist, and cover the incoming-link rewrite, the widened return paths and the signed-out round trip (#1025).Mobile Vitest covers picking a file from Files and the library (the metadata strip, the name a photo gets, each refusal in core's words before and after the read), the upload's object and row and the cleanup of a refused row, the five-minute URL, the remove order and its refusals, and the quest read's grouping and thumbnail signing; Jest covers the strip (each state, both sources, the viewer and the browser, Remove behind a confirm), the task list's wiring with the flag on and off, the Ask sheet's files and their cap, and the Answers screen naming a question's files. Core covers the new helpers and the "Attached:" line (#1017).
Core covers the attendance schema, window, completion filter and each refusal's words; the web action covers each refusal; mobile Vitest covers the attendance reads (gated, soft on failure) and the confirm call; Jest covers the panel's states and the quest page — the check-ins, the Realtime binding, an owner confirming an accountless seat, and "Mark Complete" held back until everyone is in.
realtime_publication.sqlgains four assertions forquest_attendance(#1017).Covered the AI Coach on the phone: the seed request's body and every refusal, the hand-off into the one-off and recurring forms (start time, bounds, persona), the card, New Quest from the real routes with the flag off, a one-off and a routine draft, and core's draft helpers and words; the bundle check's rules have
node:testcases run by the mobiletestscript (#1018)Covered the phone's coach interview: the turn request and each refusal, the conversation's transitions (a failed turn's rollback, a correction chain, Draft it now, Start over), the shared session, the interview screen's states, and New Quest from the real routes starting an interview, continuing Draft it for me's interview, the theme interview, a routine and the coach address with no conversation; core covers the moved reply reader and interview pieces, and
apps/web's request-scoped and browser Supabase client factories gained the tests that keep its function coverage over its floor after the coach's parsers moved to core (#1018)Covered the phone's Inbox: the list and count reads (core's columns, paging, a failure kept apart from an empty inbox), marking read (only
read_at, only unread rows, ids checked), the screen's states, taps, notes, Mark all read and its rollback, Realtime re-reads and paging, and the tab badge from the real routes; core covers every kind's sentence and target and the relative-time fallback;realtime_publication.sqlpinsnotificationsin the publication and its own-row read policy (#1019).The recurring Quest settings tests for a suggested start that went stale pin the clock to the morning they describe, so they no longer fail once the real date passes the slot they expect (#1019).
supabase/tests/push_notifications.sqlcovers token access, registering, moving and capping tokens, detaching, the push preferences, every queue's push row and claim (preference, quiet hours, no phone, at most once, one per event), the in-app push queue, the investigation notice, tickets and receipts and the export, andrls.sqlpins the push tables' access rules and the token RPCs' grants; the worker covers the Expo client, every push message, the deliverer's retry rules and the receipts loop; the web covers the push switches, their action and loader; core covers the push preferences and the new inbox kind (#1020).The app's push rules have Vitest suites for registering, reconciling (pending detaches, another account's token, revoked permission, rotation), sign-out, the primer, where a tap leads and the preference reads and writes, and Jest suites for the push host's taps and primer, Settings → Notifications in each state, the icon badge, and the You tab's link and sign-out order;
app-config.test.tschecks the notifications plugin adds no background mode, the EAS project id reaches the config only when set, and onlysrc/push/native.tsasks for permission (#1020).Core suites cover the invitation preview mapping and the party panel's gates; the app's Vitest suites cover the party reads and writes (the invitation through the Bearer route, every refusal's words), return paths and the callback carrying them, and Jest suites cover the party panel for the owner, a member and a locked roster, and the invitation link in each state, including sign-in with a return path landing back on it (#1021).
Core suites cover the guild invitation mapping and the roster's rules (groups, the split, each row's actions with invitations on and off); the app's Vitest suites cover the guild reads (not found, a failed read, the owner's invitations read softly) and every write — the Bearer invitation, the in-app invite's three refusals, an answer already standing after a no-op update — and Jest suites cover the guild list and page for an owner and a member, and the guild invitation link in each state, including the flags off and sign-in landing back on it (#1021).
Core suites cover the progress ranking, the public chips, the empty and range lines and the copy refusal; the app's Vitest suites cover the public catalogue's reads (counts, a page, the progress path, past the last page, failures) with every
selectheld to named columns, related quests, the pack catalogue and the copy, and Jest suites cover the Discover hub, the public catalogue (chips, paging, sort, search, copy, empty and failed), Copy and Related on a visitor's quest page, and the pack catalogue's filters, preview and Start into New Quest (#1022).Core suites cover the challenge pick, periods, History counts and paging, run dates and start refusals, and the Jam countdown, next boundary, leaderboard lines, index chips and refusals; the app's Vitest suites cover the challenge and Jam reads (every challenge
selectheld to named columns, cycles minted first, soft lists, not found) and the start, join and start-Jam writes, and Jest suites cover the hub's way in,/challenges(start, a refusal, Continue, History's tabs and pages, failures), the Jam index (chips, groups, Join), a Jam's page (join, panel states, your position, Show all), the start sheet, and the Jam clock's wake at a window boundary, including one that falls just before a minute tick. A web test covers the participants read (#1022).Core suites cover the badge gallery, the email preference mapping, groups and words, the weekly review parser and the profile and theme schemas; the app's Vitest suites cover the profile reads, the save pipeline (upload, row, replaced and refused objects), the avatar picker, the theme write, the new notification reads and writes and the one-at-a-time switch saver, and Jest suites cover the You root, Settings → Profile, Appearance, the email switches with flags on and off, and
/profile(#1023).The export route's tests cover the Bearer and cookie callers and a token that does not verify; core suites cover the subscription pick, renewal line, deletion blockers, export file name, password-login check, and hold the app's billing words to no price, no link and no purchase; the app's suites cover the password flow and its code step, the export (shared, unavailable, refused, unwritable), deletion's order and refusals, the billing read, and the Account and Billing screens, rendering each plan on iOS and Android with nothing to press and nothing for sale (#1023).
Core suites cover the hub split and progress, the check's view, card state and verdict offers, quarters and the counted headline, and the form's and slate's refusals; the app's suites cover the hub read (including a failed check read kept apart from "no check yet"), the theme save, slate and check writes, the hub screen with and without a theme, the editor, the slate behind its flag, the check card and its re-reads, New Quest's
?theme=, and the Today and Inbox routes to the hub. A recurring-quest preview test no longer fails once its first cycle's end has passed (#1024).Core suites cover the recap's mapping, names, bounds and paragraph in both voices, and narration's story matching, poll and toggle hint; the app's suites cover the recap read (extras failing on their own) and the sharing write, the recap screen's sections, sharing, stopping, refusals and years,
/profile's theme cards and recap buttons, the narration route read and the phone-voice choice, Listen with the narrator (background mode, lock screen, highlight, lock-screen pause, finishing), the phone's voice sentence by sentence, the fallback when the file will not play, the pending re-ask and 15-second poll, a URL near expiry, the voice toggle mid-story, release on leaving, and the expanded native config's audio permissions (#1024).
Documentation
The mobile epic's close-out:
docs/mobile/README.mdindexes every mobile document and says what is still open (store builds, a push on a real phone, in-app purchase #1095, Sign in with Apple setup #1056); the architecture record is marked accepted and records the three app-only checks left as accepted residuals, each with an issue to decide it (#1105, #1106, #1107);docs/ops/feature-flags.mdexplains that the app's flags live in the EASproductionenvironment and reach phones with the next OTA update; andAGENTS.md,add-env-flagandprecommit-gatedescribe the mobile app as built (#1004).docs/mobile/e2e.mddescribes the mobile end-to-end flows: what each proves, how a run works, why the driver reads the confirmation email, the stub answer, running it by hand, the Mac's one-time setup and adding a flow;docs/cicd.mdadds the workflow, andAGENTS.mdand theopen-prskill ask a mobile PR that changes a flow's path to update the flow and carry themobile-e2elabel (#1028).docs/mobile/offline.mdgained the replay queue — what queues and why, coalescing, order, compare-and-set and server wins, refusal versus no answer, the waiting marks and badge, the week limit and the sign-out question — with Decision 9 indocs/mobile/architecture.mdand theAGENTS.mdrule updated (#1027).New
docs/mobile/offline.mddescribes what the phone keeps and why only those reads, the keys, limits and sign-out wipe, the connectivity rule, online-only actions and their guard test, with Decision 9 indocs/mobile/architecture.md(reads cached on the phone, writes need the network, no sync engine) and the rule inAGENTS.md(#1027).New
docs/mobile/release.mdis the app's release runbook — one-time EAS and store setup, each release, when a change ships as an OTA update or needs a new build, the store listing, privacy answers, review notes and demo account, source maps, and the console checklist — withdocs/cicd.md→ Mobile builds, thecut-releaseskill's mobile steps and theAGENTS.mdrule beside it (#1026).New
docs/mobile/universal-links.mdcovers the association files, the console values and where to find them, and how to verify links;routes.mdrecords which web paths open the app and why the rest do not, andauthentication.md,party.md,architecture.md,api-endpoints.md,.env.example,AGENTS.mdand the core README follow (#1025).docs/mobile/attachments.mdis new;architecture.md,quests.md,investigations.md,evidence.md,docs/api-endpoints.md(attachmentIdsin the investigations request),docs/ops/feature-flags.md,AGENTS.mdandpackages/core/README.mdpoint at it (#1017).docs/mobile/quests.mdgains an Attendance section;architecture.md(Decision 5 joined),docs/quest-attendance.md,docs/ops/feature-flags.md,evidence.md,attachments.md,AGENTS.mdandpackages/core/README.mdfollow (#1017).Added
docs/mobile/coach.md(the AI Coach on the phone: the gate, the request and its refusals, the hand-off, the bundle check) and pointedquests.md,architecture.md,api-endpoints.md,feature-flags.md,cicd.md,AGENTS.mdand theprecommit-gateskill at it (#1018)docs/mobile/coach.mdgained the interview;routes.mdlists/quests/new/coach, andquests.md,AGENTS.mdand the core README point at it (#1018)Added
docs/mobile/inbox.md(the Inbox: the gate, the reads, live updates, marking read, where each kind leads);routes.mdmarks/notificationsbuilt, andarchitecture.md(Decision 5 joined),docs/ops/feature-flags.md,AGENTS.mdand the core README point at it (#1019).docs/notifications.mdgained a Push section (the channel on each queue, at most once, quiet hours, preferences, receipts, what each push says and opens, adding a push);docs/schema.md,docs/ops/feature-flags.md,docs/mobile/inbox.md,AGENTS.mdand the core README follow (#1020).New
docs/mobile/push.mdcovers the app's half of push: the gate, the primer, registration and reconcile, sign-out, taps, channels, the badge, Settings → Notifications and testing on a phone;docs/notifications.md,docs/mobile/architecture.md,docs/mobile/inbox.md,docs/mobile/routes.md,docs/ops/feature-flags.mdandAGENTS.mdpoint to it (#1020).New
docs/mobile/party.mdcovers the phone's party panel, the invitation link and return paths;docs/mobile/authentication.mdlists the third redirect URL, andquests.md,routes.md,AGENTS.mdand the core README point to it (#1021).New
docs/mobile/guilds.mdcovers the phone's guild list and page, the writes, invitations both ways, claim codes and the guild invitation link;party.md,push.md,routes.md,AGENTS.mdand the core README point to it (#1021).New
docs/mobile/discover.mdcovers the Discover hub, the public catalogue's reads and named columns, Copy to my quests, related quests and the pack catalogue;quests.md,routes.md,docs/ops/feature-flags.md,AGENTS.mdand the core README point to it (#1022).docs/mobile/discover.mdcovers Challenges and Quest Jams — their reads, columns, writes and why their screens read on focus rather than through Realtime — with the phone checks;routes.md,AGENTS.mdand the core README follow (#1022).New
docs/mobile/you.mdcovers the You tab: the profile and picture pipeline, appearance, the notification switches and/profile;push.md,routes.md,AGENTS.mdand the core README point to it (#1023).docs/mobile/you.mdcovers Account and Billing,architecture.mdDecision 7 records the read-only billing decision and points to the in-app purchase follow-up (#1095), andapi-endpoints.md,feature-flags.md,AGENTS.mdand the core README list the Bearer export and the new modules (#1023).New
docs/mobile/themes.mdcovers Year Themes on the phone;today.md,inbox.md,routes.md,AGENTS.mdand the core README point to it, andtoday.mdnotes that the weekly review is the Today card on both clients (#1024).New
docs/mobile/story.mdcovers the recap and Listen on the phone;architecture.mdrecords thatquest_narrationsstays out of the Realtime publication (the phone polls like the web), andyou.md,quests.md,routes.md,docs/ops/feature-flags.md,AGENTS.mdand the core README point to it (#1024).