Questify

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 Enter shortcut (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 is nextTaskStatus() 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] on DASHBOARD_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.sql and 20270110130000_completion_statement_checks.sql change when a quest completes itself (#1181). quest_task_list_meets_completion() is the rule: for a Party Quest in all_assigned_tasks, every assigned task must be done and no unassigned task may still be todo or in_progress (an unassigned blocked one does not hold it open); otherwise every task must be done. sync_quest_completion() uses it. The row triggers on tasks and quest_party_members are replaced by statement triggers with transition tables, which pass each quest their statement touched to sync_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() clears completed_at when a quest leaves completed (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.sql and rls.sql cover 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's index, follow, and robots.txt no 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 with noindex, 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 project questify-c10fb, package co.questify.app) is committed and named by android.googleServicesFile, and the expo-notifications plugin draws Android notifications with a new white-on-transparent notification-icon.png, rendered from the web's icon.svg by scripts/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.ts pins the dashboard grid's auto auto 1fr rows at xl under the rail's two-row span, and that the stacked layout below xl keeps 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 and useTaskStatus tests, the Playwright due-dates spec and the Maestro today-tick flow, which ticks a task once instead of twice (#1113).

  • robots.test.ts replaces the robots cases in sitemap.test.ts and pins the whole disallow list, so a token route cannot be dropped by accident, and that nothing under /auth is disallowed; auth/layout.test.ts pins the auth layout's noindex, follow and that no auth page sets robots of 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), and completed_at through completing, reopening, archiving and unarchiving; each change was reverted in turn and caught. rls.sql checks 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.ts checks that android.googleServicesFile names a google-services.json registered for the app's own package and that the notification icon and colour are set; assets.test.ts checks the icon is a 96² transparent PNG (#1183).

Documentation

  • docs/mobile/today.md and docs/mobile/e2e.md describe the one-tap tick and drop the note that a Todo task needed two taps (#1113).

  • The add-public-route skill and the production Lighthouse test's comment describe the /auth/* pages as served noindex rather than disallowed in robots.txt (#1169).

  • docs/schema.md describes the new completion rule, the "only the write that finishes it" check and completed_at following the status; docs/mobile/today.md notes that a refused tick re-reads the tab (#1181).

  • docs/mobile/release.md gains the Firebase step for Android push (the questify-c10fb project, google-services.json, and the FCM V1 service account key uploaded to EAS) and a checklist line for it; docs/mobile/push.md describes the Firebase config and the notification icon (#1183).