Questify

4.5.0

Released

Features

  • Challenge runs now carry a persona and a deadline, and fail when the deadline passes. Starting a challenge on /challenges (web) or the phone's Challenges screen offers a "Runs on …" choice of the models your plan covers, opening on the one your most recent quest used; the dashboard's one-tap Start uses that one too. The run's quest is due when the challenge's day or week ends, and its card on the dashboard, /quests and the phone's Quests tab now shows the persona and "Due …" like any other quest — every quest with a due date shows it on its card now. Once the period ends unfinished, the quest is closed as Failed within 15 minutes (or on your next dashboard, /quests, /tasks or /challenges visit), its tasks can no longer be ticked, and /challenges History lists it under a new Failed tab, dated by when it ended. You can still reopen and finish it, but a late finish does not count as a completed run or earn Challenge Runner. A challenge's due date cannot be moved; the Edit Quest sheet shows it fixed and says why. Periods still end at UTC midnight, as /challenges has always shown (#1187).

  • The weekly review card ("Your week") can now be put away, and puts itself away once its advice was taken. It has a dismiss button on the web dashboard and on the phone's Today tab, and a review dismissed on one is gone on the other and on every device. The card also stops showing as soon as the quest it told you to focus on is completed or archived. Before this the card stayed at the top of the dashboard for eight days whatever happened, still recommending a quest that was already finished. A review that is neither dismissed nor acted on shows for the same eight days as before, and next Sunday's review appears as usual. A dismissed review cannot be brought back; its notification stays in the bell and the Inbox (#1207).

  • Archived quests were hidden from view by default. On /quests and the phone's Quests tab the All chip lists every status but Archived, and its count and the Owned / Party / Public counts under it leave archived quests out; the Archived chip still counts and lists them, and a recurring Quest whose newest cycle is archived is shown by a cycle that is not, or only under Archived when every cycle is. When All comes up empty but archived quests match, the empty state says how many and offers Show archived with the search, theme and ownership kept — "No quests outside the archive." when nothing narrows it, rather than the new-account welcome. The public catalogue (/quests/public and the phone's Discover list) does the same: All reads status <> 'archived' and its count leaves them out, while the search and chips stay up as long as any public quest exists, archived ones included (publicQuestCount()), so a catalogue whose only public quests are archived still shows its Archived chip, with "No public quests outside the archive." and Show archived in place of "No public quests yet". The dashboard's Recently updated and the Year Theme hub's tagged-quest grid leave archived quests out too (listQuests()'s new excludeArchived option), and a theme whose tagged quests are all archived says so with a link to them instead of "No quests carry the theme yet". /tasks, /api/quests and the profile page are unchanged, and nothing about an archived quest itself changed: it is still frozen and can still be unarchived. The rule is core's listedUnderAll() and hiddenArchivedCount() in @questify/core/quests/index-params, so both clients follow it (#1190).

Design

  • The phone app's tab bar is now the platform's own. On iPhone it is the system tab bar, which from iOS 26 floats as translucent Liquid Glass, inset from the screen's edges with rounded corners and content scrolling underneath; the tabs show SF Symbols, filled once selected. On Android it is Material 3's bottom navigation, with the same lucide icons as the web and the selected tab in a primary-coloured pill. Lists still end clear of the bar, the task list's bulk-action bar sits above it instead of under it on iPhone, the offline notice clears Android's taller bar, and the Inbox badge, the "N unread" label and Android's back-to-Today are unchanged. Tab labels now follow each platform's own text-size rules in place of the app's 1.3× cap. Each tab still loads nothing until it is first opened. It needs no new native code, so it ships as an over-the-air update (#1218).

Fixes

  • On the phone's Today tab, the arrow beside the weekly review's "Focus next week" quest no longer hangs off the edge of its box when the quest's title runs to two lines: the title wraps and the arrow stays beside it, inside the box. The other toggles that put a label beside a chevron (the task list's "N completed", the Tasks picker's "N other cycles", an answer's "From earlier cycles" and the Ask sheet's reference-link and attachment toggles) now wrap a long label at large text sizes instead of letting it run past the edge (#1216).

  • On iPhone the Inbox no longer hides its newest notification behind the "Inbox" title. The list now starts below the header and ends above the floating tab bar, as the other tabs' lists do, and its "could not load" and "not turned on" messages sit below the header too (#1217).

Technical changes· 11 entries for database, tooling, CI, tests and docs

Database

  • 20270115120000_challenge_deadlines.sql gives a challenge run a deadline and closes it when the deadline passes. quest_challenge_attempts gains ends_at, when the run's period closes (UTC midnight after a daily key, seven days after an ISO week's Monday, from the new challenge_period_ends_at(); null for a key in neither shape), written by set_quest_challenge_attempt_derived_fields() and never by a client, and lapsed_at, which only the sweep sets (guard_challenge_attempt_lapsed_at() refuses a client write). start_quest_challenge() is now (uuid, text, uuid default null): the third argument is the persona, refused with 42501 unless user_can_use_model_persona() covers it, and the quest's due_at is the run's ends_at; the two-argument signature is dropped and the new one granted to authenticated only. guard_challenge_quest_due_at() refuses a client move of a challenge quest's due_at (23514). close_lapsed_challenges(_now, _owner_id) closes every active challenge quest whose run is past ends_at and unfinished as failed with quests.lapsed_at, and stamps lapsed_at on every such run whatever its quest's status, without moving updated_at or last_activity_at; it runs every 15 minutes as the close-lapsed-challenges pg_cron job and for the caller from ensure_quest_recurrence_cycles(). A run never completes once its period has closed, whether or not the sweep has reached it yet: the derived-fields trigger, sync_quest_challenge_attempt_completion() and the Challenge Runner check in award_quest_completion_achievements() all skip a run with lapsed_at or one whose quest finished at or after ends_at. get_quest_next_due_dates() is recreated to also return the quest's own due_at. The migration backfills ends_at on every run (with the run's row triggers off, so a run whose quest was soft-deleted does not abort it) and due_at on every challenge quest without one, then closes the runs already over. Proven by supabase/tests/challenge_deadlines.sql, with the run's close and its visibility in rls.sql, the new signature in function_execute_grants.sql and its intentional definer grant in supabase/advisor-allowlist.txt (#1187).

  • 20270114120000_weekly_review_dismiss.sql adds weekly_reviews.dismissed_at, readable by the review's owner, and dismiss_my_weekly_review(review_id), granted to authenticated only, which stamps it on the caller's own delivered review. The function is idempotent and keeps the first time, and answers false for another person's review, one still queued or an id that names nothing. The table stays SELECT-only for signed-in users, so the function is the one way a client changes a review. Hiding the card once the focus quest is finished needed no schema. Proven by supabase/tests/weekly_review_dismiss.sql, with the access rule in rls.sql, the grant in function_execute_grants.sql and the intentional definer grant recorded in supabase/advisor-allowlist.txt (#1207).

Tooling & Configuration

  • A submitted mobile build now reaches testers without a console step. apps/mobile/eas.json submits the Android build to Play's internal track as a rolled-out release (releaseStatus: completed, was draft), so internal testers get it as soon as Play has it instead of waiting for someone to open the console and roll the draft out; the track is still internal, and promoting to production stays manual. apps/mobile/app.json declares ios.config.usesNonExemptEncryption: false, which writes ITSAppUsesNonExemptEncryption into the iOS build, so TestFlight stops holding each build on the export-compliance question; the app uses only the system's HTTPS and Keychain. That key changes the native fingerprint, so it arrives with the next iOS build and builds made before it take no update published after it. src/app-config.test.ts pins both (#1026).

  • Named the App Store Connect app record in apps/mobile/eas.json (submit.production.ios.ascAppId), so EAS Submit sends an iOS production build to TestFlight without asking which app it belongs to. Before this an iOS submission from CI had no app to target, which is why MOBILE_AUTO_SUBMIT could not be turned on. The value is the record's public numeric Apple ID, not a credential. Nothing is built or submitted by this change: iOS builds still wait on vars.MOBILE_IOS_BUILDS, and the signing credentials and App Store Connect API key live in EAS (#1026).

Tests

  • Stopped quest_recurrence_concurrency.sql failing when it ran on a minute boundary: the every-minute enqueue-event-reminders pg_cron job mints every owner's due cycles, and when it landed between the file's committed fixture and its eight callers it minted both cycles first, so every caller reported 0. The file now pauses that job with cron.alter_job() and resumes it at the end (#1187).

  • Pinned challenge deadlines (#1187): challenge_deadlines.sql covers the grants and the cron job, the period close for daily, weekly and malformed keys (ISO week 1 of 2027 included), a start refused for a persona above the plan with nothing left behind, the quest's persona and due date, a start without a persona, the fixed due date, the client-proof lapsed_at, the sweep's exact reach (future, finished, hand-failed, deleted and ordinary overdue quests), per-owner scope, idempotence, untouched timestamps, a reopened run staying open, a late finish — after the sweep or before it — not completing the run or earning Challenge Runner, the run's triggers all enabled after the backfill, the entry point closing the caller's runs and get_quest_next_due_dates() returning the quest's due date. A signed-in Playwright spec, e2e/challenge-start.spec.ts (behind NEXT_PUBLIC_FEATURE_MODEL_PERSONAS, skipped without a Supabase stack like every signed-in spec), starts a challenge on a chosen persona and checks the quest's persona and due date, the fixed field in Edit Quest, the dashboard card, and the next start opening on that persona. Core's challenges.test.ts and state.test.ts, the web's challenge action, queries, page, start form, history and quest card tests, and the phone's challenge loaders, persona choice, screen and quest card tests cover the rest.

  • Pinned the weekly review's put-away rule (#1207): latest.test.ts covers a dismissed review, a focus quest in each status, a focus quest that is gone and a row read before the columns existed; the web's queries.test.ts and the phone's load.test.ts check that the latest review is read with its dismissal and focus status and never filtered in the query; actions.test.ts and write.test.ts cover the dismiss write's success, refusal and bad input; and the card tests on both clients cover the optimistic hide, the rollback with its message and the next review showing after a dismissal.

  • Pinned the archived rule: quest-index.test.ts covers All's list and counts, the total, the ownership counts under Archived, a recurring Quest with an archived newest cycle and one with every cycle archived, a search and a template's list; index-params.test.ts the empty-state wording; public-index.test.ts the catalogue's count and wording; queries.test.ts and queries-reads.test.ts that listQuests({ excludeArchived }) and the public catalogue's All read add neq('status', 'archived') and nothing under a status filter; the /quests and /quests/public pages, ThemesView, the dashboard and theme loaders, the phone's Quests tab and public catalogue and public-load.test.ts the rest. The web coverage floors for statements and lines rose from 96.4 to 96.5 (#1190).

  • Moved the mobile tab bar's tests to the native bar (#1218): under Jest it is the host components react-native-screens renders, so test/native-tabs.ts reads each tab's item from them and taps one by sending the host's tabSelected event. navigation.test.tsx covers the five tabs in order, their SF Symbols, labels and test IDs, moving between them, and a tab mounting only on its first visit; inbox-tab.test.tsx reads the badge from the Inbox item; screen-footer.test.tsx covers the bar sitting above a bottom inset the scroll view already leaves room for.

  • Pinned the weekly review's focus link against a long title (#1216): today-extras.test.tsx holds the link to its box and lets the title, not the arrow, give way.

  • Pinned tab screens clear of the header and tab bar (#1217): src/navigation/tab-insets.test.ts walks every file under app/(app)/(tabs)/ and the components they import, and fails on a vertical ScrollView, FlatList, SectionList or ScrollViewContainer without contentInsetAdjustmentBehavior, unless an // inset: <why> comment says it is not under the header (the dialog body and the auth forms' frame say so); inbox-screen.test.tsx checks the list and the error and flag-off states. docs/mobile/routes.md names the rule.