4.3.0
Released
Features
A task's status button now completes it in one click or tap instead of moving it to In progress first, so ticking off a task no longer takes two. This holds on the quest's task list, the dashboard's Today and Due this week lists, the
Entershortcut (the shortcuts sheet now reads "Complete the task, or reopen a done one") and the mobile app's status button, which now agrees with its swipe right. Todo, In progress and Blocked tasks all go straight to Done, and a done task's button reopens it to Todo. In progress and Blocked are still one click away in the web task row's status menu and in the mobile task sheet, and the stall check-in's "I'm on it" reply still marks a task In progress. The rule isnextTaskStatus()in@questify/core/tasks/types, which both clients call, and a draft quest's tasks still cannot be completed (#1113).
Fixes
The dashboard no longer leaves a large blank gap between Today and Recently updated on wide screens. When the right-hand column (stats, Your week, Up next, streaks, theme) was taller than the left, the extra height was split between Today's row and the row below it, so Today's row stretched; the grid's last row now takes all of it (
xl:grid-rows-[auto_auto_1fr]onDASHBOARD_GRID_CLASS), and the loading placeholder, which shares the class, matches. Narrower screens are unchanged (#1180).A Party Quest no longer marks itself completed while unassigned tasks are still to do or in progress. It used to close as soon as every assigned task was done, while the page kept showing it as Active, so the next change to a task failed with "This quest is marked completed" (#1181).
Reopening a quest whose tasks are all done now keeps it open: starting, ticking or assigning a task no longer closes it again straight away. It completes again when you finish its work, and its completion time is the new one rather than the first (#1181).
When a change to a task completes the quest, the quest page now shows it at once: the status badge, the lifecycle buttons and the locked task list update without a reload. A change refused because the quest has closed refreshes the page too, on the web and in the app, and the web no longer reports that refusal as "Only the quest owner can reassign tasks" (#1181).
Technical changes· 13 entries for database, tooling, CI, tests and docs
Database
20270110120000_party_quest_completion_rule.sqland20270110130000_completion_statement_checks.sqlchange when a quest completes itself (#1181).quest_task_list_meets_completion()is the rule: for a Party Quest inall_assigned_tasks, every assigned task must be done and no unassigned task may still betodoorin_progress(an unassignedblockedone does not hold it open); otherwise every task must be done.sync_quest_completion()uses it. The row triggers ontasksandquest_party_membersare replaced by statement triggers with transition tables, which pass each quest their statement touched tosync_quest_completion_unless_already_finished()with the task list and member count as they stood before the statement, under the quest's row lock; a quest closes only when that statement is what finished its work, so a reopened quest stays open until the work is finished again, and one statement that inserts several done tasks or adds several members is judged as a single change.set_quest_completed_at()clearscompleted_atwhen a quest leavescompleted(it is kept through archiving),complete_quest()and the attendance close leave the stamp to it, and the one quest in production still carrying a finish time while active was cleared. The new functions are revoked from clients;sync_party_quest_completion_from_task()and_from_member()are dropped;supabase/tests/party_quest_completion_rule.sqlandrls.sqlcover them.
Tooling & Configuration
The
/auth/*pages (login, signup, forgot and reset password, confirm) now serve<meta name="robots" content="noindex, follow">from their layout instead of the root layout'sindex, follow, androbots.txtno longer disallows/auth/*. Every public page links the login and signup forms, so Google kept finding them and, unable to crawl them, reported them under "Blocked by robots.txt" while the pages themselves asked to be indexed; crawlable withnoindex, they are reported as excluded by the tag and kept out of search./api/*and the token-bearing/party-invites/*,/guild-invites/*,/recap/*and/chronicle/*stay disallowed (#1169).The Android build is wired to Firebase so it can get a push token:
apps/mobile/google-services.json(Firebase projectquestify-c10fb, packageco.questify.app) is committed and named byandroid.googleServicesFile, and theexpo-notificationsplugin draws Android notifications with a new white-on-transparentnotification-icon.png, rendered from the web'sicon.svgbyscripts/render-icons.mjs, tinted the brand gold. Both change the native fingerprint, so they reach phones in the next store build, not an OTA update; Android push also needs the FCM V1 key uploaded to EAS (#1183).
Tests
components/dashboard/layout.test.tspins the dashboard grid'sauto auto 1frrows atxlunder the rail's two-row span, and that the stacked layout belowxlkeeps implicit rows (#1180).The task status tests now expect one click or tap to complete a task:
nextTaskStatus()'s core tests, the web's status button, Today, Due this week, task manager and bulk-bar tests, the mobile Today, task list, offline-queue anduseTaskStatustests, the Playwright due-dates spec and the Maestrotoday-tickflow, which ticks a task once instead of twice (#1113).robots.test.tsreplaces the robots cases insitemap.test.tsand pins the whole disallow list, so a token route cannot be dropped by accident, and that nothing under/authis disallowed;auth/layout.test.tspins the auth layout'snoindex, followand that no auth page setsrobotsof its own, which would replace the layout's (#1169).supabase/tests/party_quest_completion_rule.sql(33 assertions) pins the completion rule, that only the write that finishes the work closes a quest (after a reopen, an assignment, a done task added, a done task deleted or a member joining leaves it open), that a statement writing several rows is judged as one change (two done tasks inserted at once into an empty quest close it; two members joining at once can), andcompleted_atthrough completing, reopening, archiving and unarchiving; each change was reverted in turn and caught.rls.sqlchecks that the new helpers are private and that the "already finished" read takes the quest lock. The task route tests cover the status reported after a write and a 42501 refused because the quest closed; the web task manager tests replace the "every task done" re-read with the server-reported one, and the mobile tests check that a refused write re-reads the quest (#1181).The mobile recurring Quest form's settings test holds the clock before its first cycle ends, as the create test beside it already did; it named a start of 2026-11-16 09:00 Toronto time and failed for everyone from 10:00 that day, when that cycle ended and "After that" had nothing left to name (#1181).
app-config.test.tschecks thatandroid.googleServicesFilenames agoogle-services.jsonregistered for the app's own package and that the notification icon and colour are set;assets.test.tschecks the icon is a 96² transparent PNG (#1183).
Documentation
docs/mobile/today.mdanddocs/mobile/e2e.mddescribe the one-tap tick and drop the note that a Todo task needed two taps (#1113).The
add-public-routeskill and the production Lighthouse test's comment describe the/auth/*pages as servednoindexrather than disallowed inrobots.txt(#1169).docs/schema.mddescribes the new completion rule, the "only the write that finishes it" check andcompleted_atfollowing the status;docs/mobile/today.mdnotes that a refused tick re-reads the tab (#1181).docs/mobile/release.mdgains the Firebase step for Android push (thequestify-c10fbproject,google-services.json, and the FCM V1 service account key uploaded to EAS) and a checklist line for it;docs/mobile/push.mddescribes the Firebase config and the notification icon (#1183).