3.18.0
Released
Features
The mobile app collects evidence on a done task of a quest that asks for it: a photo from the camera or the library, resized and re-encoded before it is uploaded, with the caption the AI writes arriving live; and a location check-in at the task's place that asks for consent once, uses location only while the app is open, and sends a single reading for the database to judge — the phone shows "checked in" or how far off, never coordinates. The submitter and the quest's owner can remove a piece of evidence (#1017).
A recurring Quest's cycle that lapsed with some of its tasks done now reads Partial instead of Missed — on the
/questscards and rows, inside?template=, on the quest page and its sticky header, and on the mobile app's Quests and Today tabs and quest page. Before this, a day with two of three tasks ticked looked exactly like a day never opened, and only the progress bar told them apart.questStatusDisplay()in@questify/coretakes the quest'scompletedTasksand returns the newpartialdisplay status, shown in the brand tint (a newaccentBadge variant on both clients); a caller that has not counted the tasks still gets Missed. Display only: a partial cycle is still afailedrow, still breaks the cycle streak, and the/questsstatus chips still count stored statuses (#1076).The mobile app asks the AI about a task and reads the answers: a task's Answers screen lists every investigation, pinned first, with the answer rendered as Markdown, who answered, what it cost and the question asked; a question asked there appears at once and settles live as the worker writes it. Ask about this task has the web's starters, question, reference links and cost note, runs on the quest's model, and shows the web's own words when the plan, the balance, the daily cap or a link refuses it. A finished answer can be pinned or unpinned for the whole party, and on a recurring Quest the earlier cycles' answers follow, with the last one offered in Ask before paying for another. A task with answers carries a chip on the task list ("2 answers", or "Answering…") that opens them, and the task sheet offers Answers or Ask about this task (#1016).
The mobile app creates and edits quests: New Quest with a title, goal, a quick list of up to ten first tasks or a Quest Pack, a due date, context and constraints, reference links, a schedule on the phone's own date and time picker, the Year Theme, the model persona, and draft or active, public and evidence; and Edit Quest on the owner's quest, with the statuses the quest may move to. A quest made on the phone is the same rows as one made on the web with the same inputs. Changing the schedule of a recurring Quest's cycle asks whether it is for this cycle or this and all future ones, and the owner can delete a quest from its page after confirming. A quest whose model the owner's plan no longer covers, or that was retired, keeps it until the owner picks another, as on the web. The app's dialogs and sheets now stop at the screen's height and scroll their content, so every Quest Pack stays reachable (#1014).
With recurring Quests on, the mobile app creates them and changes them as the web does: New recurring Quest with daily, weekday, weekly or every-few-days cycles, a start and length, the tasks each cycle starts with, when a cycle is complete and, with guilds on, the guild whose roster joins every cycle, and the web's summary of the cycles it creates. The owner of a cycle can open the recurring Quest's settings to change its schedule or pause and resume it, and edit the tasks future cycles start with, optionally applying them to the current and next cycle too. The Quests tab's New button offers a quest or one that repeats on a schedule (#1014).
The people who work a quest can work its tasks in the mobile app: add them, tick their status, edit a task's title, details, status and due date, assign it to a party seat, move it up or down and delete it, with the web's status chips, search and folded completed tasks. A party member works only the tasks on their own seat, a challenge's tasks keep their wording, and a write the database refuses is undone with the web's words in a toast (#1015).
Working a quest's tasks in the mobile app takes touch: the owner drags a task by its grip to reorder, a swipe right completes a task or reopens a finished one, a swipe left deletes it after asking, and a long-press selects tasks for a bar at the foot of the page that completes, dates, assigns or deletes them together, keeping only the ones that could not be changed selected with the reason. "Complete all" finishes every task the viewer may work. Each gesture is also a screen-reader action (#1015).
The mobile app's Tasks tab lists every quest the person works, their own and the Party Quests they sit on, in a picker that drops from the top of the screen, with the chosen quest's working task list below. It folds a recurring Quest's cycles into one row, opens the quest the web would, and follows
/tasks?questId=and?task=links, which also open that task. The task list gains the Pinned chip, which lists tasks holding a pinned answer and lets the search find those answers' words, and, behindEXPO_PUBLIC_FEATURE_TASK_HISTORY, a task's history in its sheet (#1015).A quest's owner can change its status from the mobile app as on the web: Start, Mark Complete (which counts the tasks again and asks whether to mark the unfinished ones done), Mark Failed, Reopen, Unarchive and Archive, with the web's words when the database refuses a move. Party members and the owner can read, post, edit and delete the quest's Discussion; a completed quest's Chronicle shows on its page, and its owner can write or rewrite the story, share it with a link and stop sharing; and Share Quest sends a public quest's link through the phone's share sheet (#1013).
Opening a quest in the mobile app shows its page as the web does, read-only for now: the title and status, progress and goal, the tasks, the party with each member's assigned tasks, and the Details card (owner, schedule, deadline, Year Theme, model, challenge, streak and every cycle of a recurring Quest), then Context and Constraints. A party member sees what a party member sees on the web, a visitor to a public quest sees no party or deadline, a quest that is not there or not yours shows the web's "This path leads nowhere", and a quest that could not be loaded says so with Try again. The task list updates while the page is open when anyone in the party changes a task (#1013).
Fixes
The mobile task sheet's "Changed by" line, behind
EXPO_PUBLIC_FEATURE_TASK_HISTORY, now shows who last changed a task: it read the stamp fromtasks, whose column allowlist withholds it, and now reads it throughget_tasks_with_deadlines()as the web does (#1015).Saving a quest's edit that the database refuses no longer shows the database's own error text; it says the quest could not be saved (#1014).
Changing or archiving a quest that the database refuses no longer shows the database's own error text: a move the lifecycle does not allow reads "That is not a valid transition for this quest.", an attendance quest completed too early says every member must confirm first, and anything else says the quest could not be updated or archived (#1013).
Technical changes· 29 entries for database, tooling, CI, tests and docs
Database
task_evidencejoined thesupabase_realtimepublication, so the mobile app hears a photo's caption arrive instead of polling; Row Level Security and the table's SELECT grant keep each event to the submitter and the task's quest party, andsupabase/tests/realtime_publication.sqlpins the publication's exact list (#1017).task_investigationsjoined thesupabase_realtimepublication, so the mobile app hears an investigation claimed, answered or refunded instead of polling; Row Level Security and the table's SELECT grant keep each event to the task's quest owner and party, andsupabase/tests/realtime_publication.sqlpins the publication's exact list (#1016).
Tooling & Configuration
The web's evidence module (
lib/evidence/evidence.ts: the bucket's limits and path, the row mapping, caption and check-in copy, the RPC payload schemas and error copy) moved whole to@questify/core/evidence/evidence; the web re-exports it. The mobile app addsexpo-image-picker,expo-image-manipulator,expo-locationandexpo-file-system, itsapp.jsoncarries the camera, photo-library and when-in-use location copy, andEXPO_PUBLIC_FEATURE_LOCATION_CHECKINSmirrors the web flag (#1017).The investigation credit range (
ai/investigation-pricing), the Ask dialog's starters, limits and cost-note sentences (ai/investigation-ask), the answer card's fallback, cut-short and usage lines (ai/investigation-card), the earlier-cycle history's shapes, page and counts (tasks/investigation-history) and the pin payload, refusals and copy (tasks/investigation-pins) moved fromapps/webto@questify/core; the web's Investigate dialog, task card, history lib and pin route use them. The mobile app addsreact-native-marked8.3.2 (pure JavaScript on the installedreact-native-svg; no rebuild), and its API client sends a JSON body (#1016).A quest's create and edit arguments and their refusal copy (
quests/write), the persona selection (ai/persona-defaults, now including how a quest's persona is chosen and when a stored one is kept) and the recurring Quest settings copy (quest-recurrences/settings) moved fromapps/webto@questify/core; the web's quest actions call the same builders as the app. The mobile app adds@react-native-community/datetimepicker(a native module, so dev builds need a rebuild) and mirrorsNEXT_PUBLIC_FEATURE_TASK_EVIDENCE(#1014).A recurring Quest's create and settings arguments, how a saved template reads back, the start-retry rule and every refusal's copy (
quest-recurrences/write), the form's choices and summary copy (quest-recurrences/form) and the cycle preview (quest-recurrences/preview) moved fromapps/webto@questify/core; the web's recurrence actions, queries and form use them. The mobile app mirrorsNEXT_PUBLIC_FEATURE_GUILDS(#1014).The task payload schemas (
tasks/payloads), the reorder maths (tasks/reorder), the task routes' refusal copy (tasks/write), the status picker's order and the task list's write rules (tasks/permissions) moved fromapps/webto@questify/core; the web's task routes and TaskManager use them, and the mobile app writes tasks with them (#1015).The bulk-action rules (
tasks/bulk, withbulkPermissionsOf()andcompletableTasks()) moved fromapps/webto@questify/core, and the web's TaskManager and bulk bar use them. The mobile app addsreact-native-gesture-handler(Expo SDK 58's 3.3, which also replaces the 3.4 that Expo Router brought in) andreact-native-reorderable-list0.18.2 under a rootGestureHandlerRootView, so a dev client built before this needs rebuilding (#1015).The
/tasksQuest list's rules (tasks/quest-list), theget_my_active_quests()mapping and pinned counts (tasks/workspace), and a task's history mapping and sentences (tasks/events) moved fromapps/webto@questify/core, and the web's/taskspage, sidebar and task history use them (#1015).The comment rules (
comments/comments) and the Quest Chronicle's reading and link helpers (quests/chronicle) moved fromapps/webto@questify/core, and the Chronicle's substitute-model notice and the status refusal copy (describeQuestStatusError()) are new there; the web imports them with no other change in behaviour. The mobile app mirrorsNEXT_PUBLIC_FEATURE_NARRATIVE_MODEandNEXT_PUBLIC_FEATURE_QUEST_COMMENTS, and makes its first call to a web route handler with its access token (#1013).A party seat's shape, the viewer's own seat and the party panel's member names and progress labels moved to
@questify/core/party-quests/members; the web imports them from there with no change in behaviour. The mobile app mirrorsNEXT_PUBLIC_FEATURE_MODEL_PERSONASasEXPO_PUBLIC_FEATURE_MODEL_PERSONAS(#1013).
Tests
Task evidence on the phone is covered without a device: the photo flow (permission, resize target, JPEG re-encode, the upload payload, a refused row removing its object, a failed upload), the check-in (the call payload is exactly the task and two coordinates against a reading that carries more, each permission and services state, consent read and write), the reads with signed URLs, Remove's order and refusals, the sheet's gate, and the section's states, consent dialog, verdict, revert and Realtime binding;
app-config.test.tsfails on any background-location mode, permission, entitlement, task or call; the publication test gains the table (#1017).Task investigations on the phone are covered from the shared words to the screen: the cost note for a paid, free, short-balance and fallback persona, the history page and counts, the pin refusals, the screen's reads with their access, not-found, failed and soft paths, asking through the Bearer route with each refusal's copy, the pin's read-then-update and its Postgres codes, the answer counts, and from the real
app/route the empty state, each answer state, a Realtime hint settling a question, pin and unpin with the refusal put back, earlier cycles with retry and Show older, and Ask; the Ask sheet's starters, link cap and checks, cost notes and refusal; the task list's chip, row action and sheet button; and the publication test's new assertions (#1016).New and Edit Quest are covered from the shared builders to the screens: a test that the phone's
create_quest()arguments equal the web's for the same inputs, the form's conversions and field errors, each edit path (archived, status moves, a cycle's schedule and both scopes) and delete (the Quest Jam block, the file clean-up), the form's states, and the sheets from the realapp/(#1014).Recurring Quests on the phone are covered from the shared builders to the screens: a test that the phone's create and settings arguments equal the web's for the same inputs, keeping a template's guild, the start retry, the task and pause writes, the form's choices and summary, the task editor, and the three sheets and their entry points with the flag on and off (#1014).
Working a quest's tasks on the phone is covered from the shared rules to the screen: who may do what, a test that the phone's task rows equal what the web's routes write for the same payloads, each gate and refusal, the list's filters, the optimistic tick, delete and order with their reverts, and the task sheet (#1015).
The task list's gestures and batches are covered: a drop sending the whole order from a filtered list and from the completed group, a refused drop put back, swiping to complete, reopen and delete, who gets a grip or a delete, selecting by long-press, action and button, a selected task a filter hides, each bulk action with its partial failures and skips, a batch holding every other write, and "Complete all" for an owner and a member. The drag list and swipeable row are replaced in
jest.setup.tsby plain views whose callbacks the tests fire (#1015).The Tasks tab is covered from the shared rules to the screen: the workspace read with its cycle mint and pinned counts, the pinned answers shaped for search, the history read, the quest page's pinned read for collaborators only, and from the real
app/route the quest it opens, the picker's search, Party Quests and folded cycles,?questId=and?task=links, Pinned counts in the picker, and the empty and failed states; the Pinned chip and the history in the sheet, with its flag on and off (#1015).The quest page's writes are covered: the status changes and their refusal copy, comment paging and writes, the Bearer client, writing and sharing a Chronicle, and the owner's toolbar, the Chronicle panel, the Discussion and the screen for the owner, a party member and a visitor (#1013).
The quest page's read is covered for each viewer, a failed quest or party read, a missing quest, a bad id and each optional read failing alone; its parts and the screen are covered from the real
app/directory, including not-found, Try again, a failed refresh, the Realtime re-read and the way in from the Quests tab (#1013).
Documentation
docs/mobile/evidence.mdcovers task evidence on the phone — the gate, the photo pipeline, what a check-in sends and what is stored, consent, live captions and Remove;docs/mobile/architecture.mdmarkstask_evidencejoined to Realtime and the when-in-use rule,docs/mobile/quests.mdthe sheet's Evidence,docs/ops/feature-flags.mdthe two mirrors, andAGENTS.mdthe rules (#1017).docs/mobile/investigations.mdcovers asking about a task on the phone, live answers, rendering, pins, earlier cycles and the task list's chip;docs/mobile/architecture.mdmarkstask_investigationsjoined to Realtime,docs/mobile/quests.mdthe Answers entry points,docs/mobile/routes.mdthe Answers screen, andAGENTS.mdthe rules (#1016).docs/mobile/quests.mdcovers creating, editing and deleting quests on the phone, anddocs/mobile/routes.mdmarks the New and Edit Quest sheets built (#1014).docs/mobile/quests.mdcovers recurring Quests on the phone,docs/mobile/routes.mdmarks their three sheets built, anddocs/ops/feature-flags.mdrecords the app's recurrence and guild mirrors (#1014).docs/mobile/quests.mdcovers working a quest's task list on the phone (#1015).docs/mobile/quests.mdcovers dragging, swiping, selecting and the bulk bar on the phone, and the batch as the second way a task's status changes (#1015).docs/mobile/tasks.mdcovers the Tasks tab: its read, which quest it opens, its links and the quest picker;docs/mobile/quests.mdcovers the Pinned chip and task history, anddocs/mobile/routes.mdthe/taskslinks (#1015).docs/mobile/quests.mdcovers the quest page's writes: status actions, the Discussion, the Chronicle and sharing (#1013).docs/mobile/quests.mdcovers the quest page: its reads and which ones fail it, not-found against a failed read, who sees what, and when it reads again.docs/mobile/routes.mdmarks/quests/[id]built (#1013).