3.0.0

The auth flows after the sign-in form got their missing states (#781). Sign-up asks for email and password only: the required Name field is gone (the profile starts from the address's local part or the OAuth provider's name, and onboarding asks what to call the person), a password shorter than eight characters is stopped in the browser instead of after a round-trip, the length hint turns into a check once it is met, the terms sentence now sits above "Create account" instead of below the form, and an invitation's pre-filled address (?email=) is read-only with a "Use a different email" control, because editing it quietly produced an account the invitation would not accept. Forgot password swaps the field for a "Check your inbox" panel with "Back to sign in", "Use a different email" and a "Resend link" button on a 30-second cooldown, where before a success banner sat above a still-live form; the login page's "Forgot password?" link carries the typed address (?email=). Reset password checks the recovery session when the page loads and, without one, shows "This link has expired" with a "Request a new link" button instead of a form that only failed after both fields were filled; the page now has a footer, the in-form expiry error links to a new request, and a completed reset lands on /dashboard?password_updated=1 — or /onboarding?password_updated=1 for an account that has not finished onboarding, since the middleware would otherwise re-point /dashboard and drop the query — which shows a "Your password has been updated" status in place of the old silent redirect. /auth/callback now sends a recovery link it cannot use (a failed code exchange, a missing code, or Supabase's own ?error= for an expired or reused link) to /auth/reset-password?error=link_expired instead of the login form's generic error, and the page shows the expired state for that flag even when an older session is still signed in, offering "Change your password in Settings" there because the forgot-password page would bounce a signed-in visitor. Confirm email gains a MailCheck tile, says the link works for one hour, and offers "Resend the email" (new resendConfirmationAction → supabase.auth.resend({ type: 'signup' }), 60-second cooldown that starts on arrival) with "Already confirmed? Sign in · Wrong email? Start over" below; signup now passes next to the confirm page so a resent link keeps an invitation's destination. The resend answers the same whether or not the address is waiting on confirmation and reports only rate limiting, as the reset request already did. The dashboard greeting now uses the profile name ahead of user_metadata.full_name, which only the removed field and OAuth set — without that an email signup would have been greeted by its address even after naming itself in onboarding (#781)

The Privacy Policy and Terms of Service now share one layout, LegalPage in components/legal/legal-page.tsx (#779). An "On this page" list built from each page's sections array sits above the body on phones and tablets and becomes a sticky rail beside it from lg (lg:grid-cols-[14rem_1fr], lg:sticky lg:top-24), so the 14 Terms sections and 9 Privacy sections are one click away instead of a long scroll. Each <section> now carries its bare id as an anchor (/terms#plans-and-billing, /privacy#data-retention) with scroll-mt-24 to clear the sticky header; the heading keeps its ${id}-heading id for aria-labelledby. The body is capped at max-w-[34rem], measured in Chromium at about 72 characters a line (longest 78) where the old max-w-3xl column ran 95–100, while the header stays max-w-3xl. It is deliberately not the 72ch the issue proposed: ch is the width of a "0", about 10.6px in Geist at 16px against an average letter of about 7.5px, so a 72ch column still measured 97 characters a line. Under the "Legal" eyebrow a LegalNav row links Privacy Policy · Terms of Service · Pricing with aria-current="page" on the one being read; before this Privacy never linked to Terms. Pricing appears only with NEXT_PUBLIC_FEATURE_BILLING, like the header and the Terms billing paragraph, because /pricing 404s without it. Each page now keeps a newest-first CHANGES list of { date, summary }: the first entry is the "Last updated" date (so the date cannot move without a summary), and the list renders as a collapsed "Recent changes" disclosure under it, which is what backs the Privacy promise to highlight material changes. The policy wording itself is unchanged. The issue's signed-out profile link needed nothing: the Privacy page now links /settings/account, and /settings is in PROTECTED_PATH_PREFIXES, so the middleware already sends a signed-out reader to login with next (#744, #770).

/pricing shows one Pro price at a time (#778). A segmented Monthly · Annual toggle (PricingProCard, Annual by default) swaps the price and the one subscribe button that goes with it. Before, both prices sat side by side, wrapping to two rows on a phone, and a signed-in free account got two full-width subscribe buttons with nothing to tell them apart. Annual carries a "Save N%" badge worked out from Stripe's two amounts by annualSavingsPercent() in lib/billing/plans.ts. It rounds down, and is left off when the currencies differ or the annual price is not cheaper. The other interval's price stays on screen as a sentence ("Or $8.00 billed monthly."), because Stripe's activation review wants every price visible without a click. A deployment that sells one interval shows that price without a toggle, as before (#774). A signed-in free account now sees "Your plan" on the Free card and a disabled Current plan button, where it used to get a Free card with no action and no status. From sm the two prose feature lists give way to a five-row Feature · Free · Pro table (PlanComparison, rows in PLAN_COMPARISON_ROWS). Its allowance lines are the same constants as the lists, so the two can never state different allowances. Phones keep the lists. The billing terms are <details> items with anchors — /pricing#cancel, #refunds and a new #credits answer explaining how AI credits are spent, reset and not rolled over. They start open so the terms stay readable without a click, and the cancel and refund wording is unchanged. The heading is now the serif h1 under a "Plans" eyebrow, matching the legal pages. ProPlanCard takes its price row as a pricing slot instead of prices/intervals, and the settings page's card is unchanged. The branded 404 for a billing-off install is left to the loading/error issue.

The landing page was reworked for phones and trimmed of repeated content (#777). At 375×667 the hero demo now starts on the first screen instead of a scroll below it: the phone text stack is tighter (py-10, text-base body) and HeroQuestDemo is h-[17rem] with p-3 below sm. The "Feature highlights" section, which pitched Quest Packs, Challenges and Achievements a second time with the same card pattern as the product-path cards, was removed. What it added is now a compact two-column checklist under "How it works": steps and deadlines, Party Quests and AI investigations always, plus comments, deadline reminders, attachments, Guilds and the weekly report only where their NEXT_PUBLIC_FEATURE_* flag is on, so a deployment never advertises something a new account cannot find. The three "How it works" steps now describe the loop without naming those features again. The mid-page signup button was dropped. Below md, a new LandingStickyCta bar (Create a free account + Sign in) slides in once the hero has scrolled away and hides again when the closing section comes into view, so it never covers that section or the footer. The link-less "Remember the progress" card now ends in a RecapPreview thumbnail labelled as a sample, because recaps and achievements have no public page to link to. The product-path grid steps through two columns at sm, with the third card spanning the row. Where billing is on, a line under the hero buttons reads "Everything is free · Pro adds frontier AI models" and links to /pricing. The shared CTA labels and the header's Pricing link already landed with #746 and are unchanged here.

The guild invitation, Party Quest invitation and unsubscribe pages now share one card, components/public/token-card.tsx, instead of three hand-rolled copies that had already drifted (#776). Someone who opens an invitation while signed in to a different account now gets a Sign out button that brings them straight back to the invitation (/auth/logout follows an internal next form field), where before they had to sign out and dig the link out of their email again. Every link that no longer works — invalid, expired, withdrawn, already used, or a deleted Party Quest — offers Go to Questify and Sign in (or, signed in, Go to your guilds / quests) instead of a card with nowhere to go, and so does a broken unsubscribe link. A pending invitation now says how many members the guild or party has and who runs it, and a Party Quest invitation how many of its tasks are done. Once an unsubscribe link has changed something, the page lists the person's other Questify emails with a Turn off / Turn on button each — only the categories this deployment offers — and a "Stop all Questify emails" button while anything is still on, so stopping everything no longer takes eight separate links or signing in. A mail client's one-click unsubscribe still turns off only the one category its link names.

Onboarding was reworked for phones and for the wrong-account case. It now has its own (onboarding) route group, whose compact header carries Sign out and a quiet "Finish setup later" link (the old "Skip setup" footer button, which sat a mis-tap from "Skip for now"); PublicHeader gained a signedInAction slot for it. Each step ends in one footer row — Back · skip this step · Continue — with Continue the only primary button: it stays inside the step's form, while Back and skip are form=-attributed buttons that submit OnboardingNavForms' separate forms, so a half-filled step can still be left without tripping its validation. The Quest Pack step lists "Start from scratch" first, lays the packs out two-up from sm, and its skip now reads "Decide later" instead of repeating the scratch option's label. The avatar is an upload into the avatars bucket, the same flow as /settings/profile — AvatarPicker and saveWithAvatarDraft are now shared by both forms, and the server half lives in lib/profile/avatar-storage.ts — instead of an image-URL field few new users could fill; replacing a photo on a revisited step removes the earlier upload, an external URL stored by the old field is left alone, and when the step fails only after the profile already points at the new upload (the onboarding row could not advance) the action returns avatarSaved so the browser keeps the object instead of cleaning it up. The wizard mounts the app shell's ThemePreferenceSync, because it renders outside that shell: a theme picked on the profile step now repaints the rest of the wizard as soon as the step's revalidation brings the saved preference back, where before it waited for the dashboard. On a 375px phone the step card now starts within 160px of the top: py-6 sm:py-12, space-y-6, the welcome heading on the first step only (after it the step title is the h1 and the card keeps just the description), "Step N of 4" beside the heading, and the list of step titles hidden below sm. (#775)

/settings/billing is where a free account upgrades and a paying one checks its usage. Checkout used to be three pages away — the Plan card linked to /pricing, the only page with an UpgradeButton — and it now starts from the Plan card itself, with a button for each interval Checkout can actually sell, quoting Stripe's price (a failed price read keeps the button and drops the amount). listCheckoutIntervals() in lib/billing/stripe.ts decides which, so a deployment that prices only one interval no longer shows a button that answers 503 from /api/billing/checkout — on /pricing too, which had the same gap — and listProPrices() now quotes each of those intervals on its own instead of returning nothing unless both price ids are set, so that one button keeps its amount and /pricing no longer lists a price column for a plan nobody can buy. isStorefrontConfigured(), its both-or-nothing guard, is gone and Compare plans as a secondary link. The page is two columns from lg: the Plan card and a new AI usage card (AiUsageCard — a Pro balance against its allowance with a meter, or a free account's actions left today, never a credit count, and a plain "could not be loaded" rather than a zero on a failed read) on the left, and the Pro card from /pricing on the right, now shared as components/billing/plan-cards.tsx so the two pages cannot describe different products. A Pro account skips the two Stripe price reads entirely. The sentence about invoices, payment methods and cancellation living in the Stripe billing portal now appears only to an account that has a portal to open, matching the Manage billing button it describes. After checkout, CheckoutReturnStatus re-renders the page with router.refresh() every 2.5s for up to 15s until the webhook's tier lands, then says Pro is unlocked; past the window it offers Check again instead of telling the customer to refresh by hand. It never claims Pro before the server reads it. (#774)

Guilds are quicker to scan and harder to break by accident. /guilds lays each group out as a grid of compact cards (sm:grid-cols-2 lg:grid-cols-3). Each card used to be a full-width ~130px card with one button. A card's name is now a next/link stretched over the whole card, so opening a guild is a client navigation with a card-sized target instead of a full reload from a 36px button. Leave asks once more in place ("Leave Sunday Dinner? This is permanent — you can't be invited back to this guild.", focus on Cancel, Escape backs out, and focus returns to Leave if you back out) — it used to act on one click with no hint that a closed membership is never reopened and guild_members_guild_user_unique allows one row per account per guild, so the owner cannot invite a leaver back. A failed action is reported on the card it came from. A success that moves or removes the card (Accept, Decline, Leave) is announced once above the list and names the guild, since the card is gone by the time the page revalidates. A first visit is one card holding the explainer and the create form; creating the first guild announces it above the list and moves focus to "Guilds you run", since the form goes away as the guild arrives. With a guild, the explainer and the empty "You do not run a guild yet" lines are gone, an empty group is left out, and New guild in the header opens the create form in a dialog on useModalFocus, which hands focus back to that button however it closes. The claim-code form is a "Have a claim code?" disclosure under the list. /guilds/[id] puts the roster on the left and, for the owner, a 320px column on the right from lg (lg:grid-cols-[minmax(0,1fr)_320px]) with Add member, the waiting email invitations and Guild settings. Each roster row shows the name, its status, at most one inline action and a ⋯ menu (OverflowMenu) — before, it was up to four labelled buttons that wrapped to two lines on a phone. An accountless member's inline action is Invite by email, or Claim code while NEXT_PUBLIC_FEATURE_GUILD_INVITES is off. Claim code, Make owner and Remove are in the menu. Make owner opens a confirmation dialog (TransferOwnershipDialog). It used to transfer on one click, and the clicker lost the page's controls at once. A transfer that goes through is announced at the top of the roster ("Riley now runs Sunday Dinner.") and focus moves to the roster heading, since the row's ⋯ button goes with the clicker's ownership; Cancel or a refusal hands focus back to that button. Remove asks in place and says what it costs: an account-backed member cannot be invited back, and an accountless one added again by name starts a new place without the old history. A successful removal is announced at the top of the roster, since the row moves into the collapsed former-members group, and a withdrawn email invitation is announced from a line that outlives the invitations card. A row's result message, its one-time claim code and its invite form now open under that row instead of under the whole list. The claim code and the invitation link (InviteLink) each have a Copy button that says "Copied" and announces it, or says when the clipboard refused. Declined, removed and departed members move under a collapsed "Former members (n)". The two add-person cards are one Add member card with a segmented choice: "By email | By name" with email invitations on (an emailed invitation reaches someone with no account too), "Has an account | Doesn’t yet" with them off. The always-open rename form is gone. The owner renames the guild by selecting its h1 (EditableGuildName, on InlineEditableText like the quest title), still checked against renameGuildSchema before the request goes out. A member no longer sees the "Linking a second account?" claim form on every guild page, since it lives on /guilds. New shared pieces: components/ui/copy-button.tsx, components/ui/confirm-strip.tsx (the second step of a two-step inline confirmation), and an onValueChange prop on SegmentedControl. No Server Action, query or migration changed (#773).

A shared Well Played recap now opens for the person it was sent to. Share recap on /profile/recap/<year> used to hand out that same signed-in URL, which sent a signed-out recipient to the login page and showed a signed-in one their own recap. It now mints a revocable link to a new public page, /recap/<shareId> (app/(standalone), compact header), the first time it is used, and hands that out through the share sheet or the clipboard. The button always says what happened: "Link copied" for three seconds where the clipboard is used, a status line for a share sheet, and the link in a read-only field with a Copy button when the browser refuses both (a share sheet or clipboard write can be refused once the click's activation has gone on minting the link) — before this, a desktop browser without navigator.share appeared to do nothing. Stop sharing beside it revokes the link, and the page then says the link does not work. The public page is read-only: the owner's name and the stats, monthly activity and badges in the visitor's voice ("Ann crushed 3 quests… Their longest streak…"), a sign-up prompt (or, for a signed-in visitor, a link to their own recap), noindex and no-referrer, and a preview image from /api/recap/<year>/og?share=<shareId>; it shows quest titles to no one but the owner. /recap/* is disallowed in robots.ts and kept out of the sitemap and Lighthouse lists like the invitation links. The owner's page also gained previous/next year chevrons (RecapYearNav, from the cached years plus the current one — other years were reachable only from /profile), "Computed {date} · Refresh" above the card in place of a Refresh button at the top and the timestamp at the bottom, with the refresh done as a router refresh that says "Refreshing…" rather than a full GET with no pending state, and three new sections: a twelve-month Active days by month bar chart (each month readable as "March: 4 active days" to assistive technology, the busiest month labelled), Badges earned in {year} with AchievementBadge, and an owner-only Quests you finished list (up to 12, linked, then "and N more"). The hero gradient moved from the -500 to the -700 stops and every line of text on it is solid white: the old pink end measured 3.5:1 even for solid white and the 70% eyebrow 2.4:1; every stop is now 6:1 or better. The AI-written narrative stays with #542 (#772).

/profile is shorter and the email preferences save themselves. The badge gallery shows unlocked badges as compact cards up to four across (sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-4), so the whole catalogue fits in four rows at xl, and folds every locked badge into one collapsed "N more to discover" row that opens to padlocks showing only each badge's rarity — it used to be one full card per locked badge, each reading "Mystery badge / Keep questing to discover this achievement.", about 1,300px of the same sentence on a phone. The header's badges are 32px links to their own card in the gallery (AchievementBadgeStrip's new size and linkToGallery props; quest cards keep the 28px size beside their 28px avatar), where before they were unnamed circles with only a hover tooltip. The three stats stay three across at every width with a smaller figure below sm instead of stacking into three full-width cards, the Archived Themes column appears only when there is an archived theme (the current-theme card spans the row otherwise), and the current year's recap is marked "New" only until a recap exists for it rather than every day of the year. On /settings/notifications the eight categories are grouped under Reminders (with the timezone and quiet hours), Collaboration and Product, each one a switch, and every change is saved as it happens — there is no Save button; a status line says "Saving…", "Saved" or the action's error. Saves post the whole form through the same updateNotificationPreferencesAction and flag-gated parser as before, one at a time, with a change made mid-save sent as soon as the first lands; quiet-hour times save when the field loses focus. The timezone is a <select> instead of free text over a datalist. It lists Intl.supportedValuesOf('timeZone') plus UTC (which V8 leaves out of that list, but the database accepts) and the saved and detected zones (timezoneChoices() in lib/notifications/timezones.ts). A browser that cannot list zones gets the text field back, saved on blur. Under it are "Detected: {zone}", "(not saved yet)" while a detected zone has only been filled in, and a "Use {zone}" button when the saved zone differs from the browser's. The Year Theme half of this issue had already landed with #769/#770: /profile shows the theme read-only and edits happen on /themes (#771).

Account configuration has one home: /settings, with Profile, Appearance, Notifications, Billing and Account sections under a sub-navigation that is a rail from md and a row of tabs on phones. Profile edits the display name and the avatar after onboarding — before this, the only write to either was the skippable onboarding step, so someone who skipped it saw their email as their name for good. The avatar is an upload (held in the browser until Save, then written to the new avatars bucket and handed to updateProfileAction as an object path; a failed save removes the upload, and replacing or removing an avatar deletes the old object). Appearance makes profiles.theme_preference do something: Light, Dark or Match my system now renders, through a questify-theme cookie that a tiny <head> script applies before first paint (lib/theme/), kept in step with the profile row by ThemePreferenceSync in the signed-in shell so the choice follows the account to new devices. A visitor with no cookie stays light; a signed-in account's default system follows the OS, so dark-OS users now see the dark theme. Notifications holds the email preferences that sat ~2,000px down /profile; the unsubscribe page, every email's preferences link and the sign-in return target for unsubscribe links now point at /settings/notifications. A failed profile read on Profile or Appearance shows an error rather than a form prefilled with guesses, which Save would have written over the real name, avatar or theme. Billing keeps its /settings/billing URL. Account shows the sign-in email and adds an in-place password change (changePasswordAction, which handles Supabase's secure-password-change reauthentication by emailing a code and asking for it; accounts with no password login see a note instead), sign out, and account deletion, which now also lists the account's avatar folder page by page and removes it. /profile is now the identity and progress page — header with an Edit profile button, stats, badges, recaps — and shows the current Year Theme read-only with a link to /themes, where it is edited. The account menu's Billing entry became Settings. Changing the sign-in email is not part of this (#770).

The Year Themes hub puts the theme beside its quests. From lg the page is a sticky 320px rail — the theme card with its colour border, progress, a default-size Create a quest for this theme (it was the smallest control on the page) and Edit theme, then the archive — next to the tagged quests at md:grid-cols-2 xl:grid-cols-3; below lg the rail dissolves into the single column as theme, quests, archive, so past years no longer push the quests a screen down on a phone. The always-open "Edit your {year} theme" card between the quests and the archive is gone: Edit theme opens the form in a dialog on useModalFocus (focus moves in, Tab stays inside, Escape or a backdrop click closes, refused while a save is in flight, focus returns to the button), and a save closes it and shows a transient Saved chip beside that button. YearThemeForm takes onSaved / onPendingChange and no longer scrolls the window to the top on success, away from its own message. Each archived year with tagged quests now links to them — "View all N quests" goes to /quests?theme=<id> — where it showed a progress bar over quests it gave no way to reach. The /quests index gained that theme param: a Year Theme id, owned quests only (the same rule as the theme's progress count), applied before the status and ownership chips are counted, shown as a removable "{year} · {title}" chip, named in the filtered empty state ("No completed quests tagged “Ship it” (2025).") and cleared by Show all quests; an id that is not one of the viewer's themes is redirected away like any unknown param, while a theme that merely fails to load keeps the filter under a generic chip. Accent-colour swatches are 44px targets named Sage, Slate blue, Rosewood, Heather, Ochre and Teal (yearThemeColorNames) for their accessible name and tooltip instead of "Use #6b8e7c as the Year Theme accent color"; the theme form and the onboarding step share them as YearThemeColorPicker (#769).

The Quest Packs catalogue shows three packs across at xl and enough of each pack to compare them from the grid. The grid is md:grid-cols-2 xl:grid-cols-3 in the page's default max-w-6xl (it was two ~490px columns for cards that need about 320px), and each card lists its first three task titles as a numbered list with a "+N more" link that opens the preview, in place of a bare "N tasks" count — the task list used to render only inside the preview dialog, so comparing two packs meant open, close, open the next. The bordered two-label filter panel is now one toolbar row: a search field and a category menu with visually hidden labels, and a live result count at the right ("3 of 12 packs" while a filter is on, "12 packs" otherwise). An empty catalogue ("No Quest Packs are active yet", with a link to start a quest from scratch) is told apart from a filter miss, which names the search and offers a Clear filters button; before this both were the same sentence with no way back. A read that fails is told apart from both: the page now carries the failure to the browser as loadFailed and it shows a "Quest Packs are unavailable right now" notice (role="alert", the challenges page's shape) instead of the toolbar and the empty-catalogue copy — it used to swallow the error into an empty list, which would have claimed nothing was active and sent the user off to start from scratch. The preview dialog moved onto useModalFocus like the app's other dialogs — it takes focus, keeps Tab inside, closes on Escape or a click on the backdrop and hands focus back to the control that opened it, none of which it did — and took the #557/#597 shape (pinned header and footer, scrolling body with min-h-0 flex-1 overflow-y-auto) so Start this Quest stays in reach however long the task list is; it should become a use of the shared Dialog primitive once #648 lands rather than grow a fourth hand-rolled focus trap. The filter itself moved to lib/quests/pack-filters.ts (filterQuestPacks(), packCategories(), packCategoryLabel()) so a pack picker elsewhere can reuse it. The New Quest page's pack select is unchanged (#767).

Quest Jams got a compact, grouped index. A card is title, pill, a two-line description, one meta row (theme, joined, finished, dates) and a footer — down from ~340px of pill-plus-sentence, two stat tiles and a "View" label inside an already-clickable card. The footer carries the one thing the viewer can do: a signed-in visitor joins a live Jam from the index in one click (the same quest title and goal the detail panel pre-fills), a signed-out one gets "Sign in to join", and someone already in sees "You're in" with a link to their quest. The list is sorted live → upcoming and grouped under "Live now" / "Upcoming" headings when both exist, with All · Live · Upcoming · Mine chips (?state=) that count what they show; "Mine" appears only signed in. The header is the single Quest Jams h1 — the eyebrow, "Sprint together." tagline and paragraph are gone. The page refreshes itself when a listed Jam starts or ends while it is open, so a card's pill and footer and the chip counts never go stale (#766).

The Start a Quest Jam form shows the card it will put on the index. The card chrome and second heading are gone, the page moved from narrow to default width with the fields on the left and a sticky preview on the right that follows the title, theme, description, duration and start as they are typed, with the computed end underneath. "Starts" is a new optional datetime-local beside Duration — blank means now; a chosen start is sent as UTC, previews the Jam as "Upcoming" and relabels the button "Schedule Jam"; the field is bounded to the next 30 days both in the form and in the validator, and a start that has just passed is sent through for the database to clamp — the input's floor follows a selection that ages past now rather than blocking the submit. The description has a live counter and the submit button is w-full sm:w-auto like every other form (#766).

The Quest Jam page keeps the join panel in reach and the leaderboard honest. The header is above the grid and the join panel is order-first on phones (right under the title, before the leaderboard) and lg:sticky on desktop; the three stat tiles are one meta line — joined, finished, window and a live countdown ("Ends in 2d 4h", "Starts in 3h 30m", "Ended 2 days ago") that ticks every minute, wakes at the Jam's start and end themselves, and when it crosses one while the page is open refreshes the page once so the pill and the join panel catch up. The leaderboard shows the top 10 with "Show all (N)", pins "Your position" above it for anyone with an entry (rank and time if finished, "not finished" if not, with a link to their quest), highlights the viewer's row, and lists everyone who joined but has not finished as a muted secondary list under it — worded that way, not "still sprinting", because an entry whose quest was failed or archived is unfinished too — a Jam with 37 joined and no finisher used to say "No completed entries yet". Rows are flex items-center at every width with the rank riding on the avatar, instead of a three-column grid that stacked to ~110px per row on a phone. QuestJamStatusBadge is one component now rather than a copy in each page (#766).

The New recurring Quest form shows what it will create before you submit it. The page moved from the narrow to the default width with the form on the left and a sticky 320px summary on the right (from lg), which now lists the concrete cycles — "Cycle 1: Sat, Nov 7, 19:00 → Sat, Nov 7, 20:00", then the next week — and updates as the start or duration changes. The preview mirrors ensure_quest_recurrence_cycles() (previewRecurrenceCycles() in lib/quest-recurrences/preview.ts): a start in the past shows the cycle containing now and the one after, and a cycle whose end instant has already passed is left out, as the database does — including an end inside the repeated hour of a fall-back DST change or a skipped spring-forward hour, which are resolved the way PostgreSQL resolves them. Each cycle is shown as the minted Quest will show it — its resolved start, and that instant plus the duration as the end — so a weekly start that falls in a spring-forward gap moves past it and a window spanning a DST change ends an hour earlier or later on the clock, matching the Quest page; the "Ends" line follows the same rule. While the form sits open, the summary re-reads the clock when a shown cycle ends or the week rolls over (msUntilPreviewChanges()), so it never promises a cycle the mint would skip. A start the validator refuses — one skipped by a spring-forward gap — shows a "that start time doesn't exist" hint instead of cycles or an end time. Duration gained 30 minutes, 90 minutes, 2 hours and 3 days plus a Custom minutes field (capped at one week, like the validator; the preview only uses a whole number of minutes in that range, so an out-of-range value typed there shows no cycles instead of breaking the page), with an "Ends …" line under the row; Goal is a three-row textarea like the main Quest form. After creating, createQuestRecurrenceAction sends you to the newly minted current-cycle Quest instead of the generic /quests list, falling back to the list only when no cycle could be read. The submit button is no longer disabled while the browser timezone is detected: a blank timezone is now defaulted on the server to the one saved in notification preferences, or UTC. The template, its cadence and what is minted are unchanged (#765).

The New Quest page puts the AI Coach beside the form. From lg the page uses the default width with the form on the left and the coach in a sticky 400px column on the right whose chat thread fills the column's height, so the draft can be watched landing in the fields; below lg the coach still stacks above the form, and with NEXT_PUBLIC_FEATURE_COACHING_MODE off the page keeps its narrow single column. Accepting a draft no longer unmounts the coach: it collapses to a "Quest drafted by AI Coach" card whose Ask for changes reopens the same conversation (same interview, so no new charge), and a follow-up re-drafts the quest, with Continue then saying it replaces what is in the form — the coaching prompt now tells the model to answer a message after its draft with the complete updated draft rather than a new interview. The model persona is a Runs on {model} chip in the coach card's header that opens the existing picker dialog directly, replacing the separate "Model persona" section and the "change it above" line (the section remains when the coach is off). The answer field starts at three rows, grows to about eight and can be resized, and the send button is labelled "Send" from sm and a 44px target on phones. In the form, a Quest Pack's tasks and the coach's tasks now share one Tasks this quest starts with section directly under Goal, with the pack select behind a Change pack link once a pack is chosen; Public quest is a switch like the Year Theme one, and Save as is a Draft | Active segmented control when creating (editing keeps the full status select). The submit footer is pinned to the bottom of the viewport from lg on this page (QuestForm's new stickyFooter prop; the Edit Quest sheet does not set it) and now carries the result of the last submit: a failed save's message, or for a validation failure — which returns field errors and no message — a line naming the rejected fields, while focus moves to the first of them, opening its section if collapsed. Inputs with an error are aria-invalid and point at their message with aria-describedby (FieldError ids, and DueDateField's new errorId prop). (#764)

/tasks has a real quest list. The 260px column that held a <select> and a three-line progress card is now a sticky, independently scrolling list of every quest the viewer owns or has joined, each row showing its title, done/total and a thin progress bar (a quest's count moves as its tasks do, and keeps that after switching to another quest), a party mark on a Party Quest, and a small filter field. A draft is greyed with "Draft · start it to work on tasks"; a completed or failed quest says so. The page's heading is now the selected quest's title, linked to /quests/{id} and followed by its status badge, replacing the "Quest tasks" eyebrow, the "Task management" heading and the title repeated as a subtitle. Below lg the list is not shown and the quest <select> sits in the header instead. On a Party Quest the workspace now loads the quest's party itself, afresh on every selection, from a new party-only route GET /api/quests/[id]/party (signed-in only; a failed read is a 500, never an empty party), so an owner gets the assignee picker here as on the quest page, and a member's controls start locked — the list says the quest is theirs as a member before the party arrives — and open only on the tasks assigned to their own seat, as #576 requires; Add waits for that seat too, since a member's new task is always assigned to it. If the party cannot be read, or holds no seat of theirs any more, the page says so and the quest's tasks stay read-only. An assignee picked while adding a task is cleared on switching quests, since a seat belongs to one quest. The database (user_can_write_quest_task()) remains the boundary (#763).

Tasks can now be selected several at a time and changed together, and the task list answers to the keyboard. Each row on /tasks and on the quest page has a checkbox that appears on hover or focus, stays visible once anything is selected, and on a touch screen (where nothing hovers) is shown by a new "Select" toggle beside the sort control; turning the toggle off clears the selection. While tasks are selected, a bar pinned to the bottom of the viewport (components/tasks/task-bulk-bar.tsx) offers Complete, Set due, Assign, Delete and Clear. Set due and Assign take their date or seat in the bar itself, and Delete always asks "Delete N tasks? This can't be undone." there before sending anything. Each action is one request per task through the existing PATCH/DELETE /api/tasks/[id] routes, settled together with Promise.allSettled (lib/tasks/bulk.ts), so the tasks that saved stay saved, only the failures are put back, and the bar says how many failed and why while leaving them selected for a retry. The bar only sends an action for the tasks the viewer could change from the row: a party member completes and dates only their own seat's tasks, never sees Assign and cannot Delete (#576), a challenge task is never deleted (#477), and the rest are reported as skipped rather than sent to be refused. A batch and other task writes never overlap, by two rules: while a batch runs (the bar's, or "Complete all"), no other write to an existing task can start — status, the edit form, the inline title, delete, reorder and location check-in are disabled on every row and refused by their handlers — and a batch only starts on an idle list, with no row write (a location check-in included) or reorder still saving and no task open in the full edit form (the bar then says "Save or cancel the task you are editing first.", because that form's Save sends every field it holds and would undo a batch's due date or assignee). Adding a task stays open during a batch, because a new row is in no batch. Every batch, "Complete all" included, folds in only the field it changed rather than the whole row its response carries, and lets an inline rename already out on one of its tasks land first, so a failed bulk delete restores the title that saved. Each lock belongs to the quest it was started on and holds only that quest's list, so a slow or stalled write on one quest never leaves another quest on /tasks unusable. While a batch runs, the investigation poll starts no read and drops any list it was already reading, which could otherwise undo the batch or bring deleted rows back. Clear, the Select toggle and Esc wait while a batch is out, and a task that failed is selected again when the batch settles even if it was unticked meanwhile, so its report and the retry are never lost. A selected task that the search, a status filter or the collapsed completed group hides stays selected, and the bar counts it as "not shown"; actions only ever reach the tasks on screen. Every row write in flight is tracked, not just the latest, which also fixes two rows saving at once clearing each other's busy state. Switching quests on /tasks now closes an open edit form, which used to linger unseen, and a refused location check-in now reports its error instead of failing silently. Keyboard: n focuses the quick-add field, j/k move between rows, x or Space selects the focused row, Enter advances it to its next status, e opens it for editing, Esc clears the selection (or, with a row's menu open, just closes the menu: OverflowMenu now claims the Escape it handles) and ? (or the new keyboard button in the header) shows a cheat sheet (components/tasks/task-shortcuts-dialog.tsx). The shortcuts never fire while a text field, select or editable region has focus, ignore keys aimed outside the task section, leave Space and Enter to whatever button has focus, and pause while any dialog is open — the manager's own, an attachment preview or the quest page's Edit Quest sheet (lib/tasks/shortcuts.ts). "Complete all" in the header stays, under the same write lock. (#762)

Each task row's controls were reworked. Status is now a split control: the main button still advances the task in one click as before, and a chevron beside it offers To Do, In progress, Blocked and Done as the shared status badges, so Blocked can be set by hand for the first time and any status is one click away rather than up to three cycles; a choice the quest's status does not allow (progress on a draft quest) is disabled. The quest owner can reorder tasks by dragging a grip at the left of the row (desktop widths) or with Move up / Move down in the row's "…" menu, which is the keyboard path; the move is saved through the new PATCH /api/tasks/reorder and works on a filtered or searched list without disturbing the hidden tasks; at the edge of the list a row is shown in, Move up / Move down step past the quest's next task, so an open task can still be moved past finished ones folded into the "N completed" group (dragging stays within the shown list). A task write never moves a task on screen: a status change, edit or Complete all response keeps the row's current position, and a failed Delete or Complete all restores only what it changed, so a write that was in flight across a reorder cannot put the old order back; adding a task is idempotent, so a reload that already brought the new task in does not show it twice, and a successful Delete removes the task again in case such a reload put it back. Reordering is offered only while the list is in the quest's order, not sorted by due date, and the sort option formerly labelled "Order added" is now "Quest order". The #n badge follows that order. Investigate is now an "Ask" button with a sparkles icon, labelled from md up, instead of a magnifier that read as search, and Delete moved from beside it into the "…" menu, which a party member, who can never delete, no longer gets at all (#761).

The task list can now be narrowed and searched, and finished work no longer sits between the live tasks. On /tasks and the quest page, a toolbar above the list has a search over each task's title and details (every word must appear, in any order; case and accents are ignored; Escape clears it), the existing sort, and status chips — All, Open (todo), In progress, Blocked and Done — each with a count of what choosing it would show under the current search. Under All, done tasks fold into a collapsed "N completed" group below the list instead of standing as full-height struck-through cards; Done lists them directly. The chip and the search are written to the URL as ?taskStatus=&taskSearch= with replaceState, so a reload or a shared link lands on the same view and leaving the quest leaves them behind; whether the completed group is open is remembered per browser in localStorage, for every quest. A task's #N badge is now its place in the order added, so it names the same task however the list is sorted, filtered or grouped (it used to be its position on screen), and the workspace's Progress box no longer divides by the "Near me" subset. Blocked hides while it would say 0, like the Quests index's rarely used statuses; a filter that matches nothing says so with a Clear filters button (#760).

A task card ends in one row of count chips instead of two or three standing rows. Every card used to close with an "Investigations" toggle and a "Comments" toggle, each in its own bordered row and present at a count of zero, and with attachments on, an "Attach a file · {types}, up to {size}" row as well: on a ten-task list about 700px of empty controls and twenty rules. The foot of the card now shows a small chip, an icon and a count, for each of investigations, comments and attachments only when the task has at least one, and a task with none of them has no footer at all. If the quest's comment counts cannot be read, every task shows a comments chip without a number instead, so a failed count never reads as "no comments" or leaves an archived quest's threads unreachable (CommentCounts.failed). Each chip opens its panel under the row with one click and closes it with a second; one panel is open at a time, so opening comments closes the investigations. The investigations chip still opens itself while one of the task's investigations is pending or running, and when a question fired from the card lands, and shows a spinner while it runs. Starting something new is a + button beside the task's Edit, Investigate and Delete buttons (the same disclosure as the quest toolbar's overflow menu, now shared as components/ui/overflow-menu.tsx; in both, Escape pressed on an item now hands focus back to the menu's button instead of dropping it to the top of the page) holding "Comment", which opens the task's thread with the cursor in the composer, and "Attach a file", which opens the file picker and, once the file is recorded, the attachments panel; the accepted types and size limit are the menu item's description. Each item appears only where it would work: Comment while comments are on and the quest is not archived, Attach a file while attachments are on and the quest takes task writes, and no + at all when neither applies. Asking the model keeps its own Investigate button. An upload in progress or a refused file shows in the footer. Long task details are clamped to three lines with a "Show more" / "Show less" control that appears only when the text actually runs past the clamp, measured at the card's width (TaskDetailsText). The quest's own Discussion moved from below the last task into the quest page's details rail, under the party panel, as a card like the Details card; the task threads stay on their tasks, and archiving still closes both (describeCommentsClosed() in lib/comments/comments.ts is now the one place that says so). Uploading moved out of QuestAttachments into useAttachmentUpload() (components/attachments/attachment-upload.tsx) so a task can upload without rendering the strip; the quest-level strip above the task list is unchanged. The separate TaskComments and TaskInvestigations toggles are gone; TaskInvestigationList is the investigations panel's content (#759).

Adding a task takes one 40px row instead of a panel of mostly optional fields. The create form on /tasks and on the quest page used to show Title and Details side by side, the assignee picker, the "Add location" link, the due date with its standing "Your local time. Due soon means within seven days." line, and an Add button alone on a bottom row at the far right: about 260px on a desktop and 380px on a phone before the first task, on every visit. It is now a title field ("Add a task…") with Add beside it, so Enter in the title creates the task, and between them four icon toggles, one per optional field: due date, details, assignee and location. Each reveals its one field below the row with one click and moves focus into it, and stays highlighted, with "(set)" in its accessible name, while that field holds a value, so a due date or assignee that was filled in and collapsed again is not submitted unseen. On a phone, Add shows only its icon so the row still fits. The location toggle opens the picker straight onto its map (TaskLocationPicker's new defaultExpanded), and "Remove location" hides it again (onRemove). The assignee toggle appears only where the old picker or note did: a quest owner with a party gets the picker, and a party member gets "Tasks you add are assigned to you." The "due soon" rule moved behind an info button beside the due-date label, the same native <details> popover as the cycle-streaks help, and is still the input's accessible description (DueDateField's new hint="popover"; the quest form and the task editor keep the inline line). Every field closes again after a task is created. Validation, the closed-list notice and the party write gates are unchanged (#758).

A quest's owner edits it without the page moving, and fixes a title without opening a form. "Edit Quest" now opens the full editor in a sheet docked to the right edge (components/ui/side-sheet.tsx, max-w-lg, full width on a phone) instead of rendering QuestForm inside the header, where it pushed the links, party and tasks down by the height of an eight-section form and scrolled the owner away from what they were looking at; the sheet takes focus, keeps Tab inside it, closes on Escape or its ✕ and hands focus back to the button, and refuses both while a save is running (QuestForm reports its useFormStatus through a new onPendingChange prop for this, because a state update made inside a form action renders only once the action has finished). A click on the backdrop deliberately does not close it, so a stray click cannot discard a half-edited form. The quest's title and goal are now edited where they stand: clicking either, or Enter on it, swaps it for a field that saves on Enter or when focus leaves and puts the old text back on Escape (in the goal, Shift+Enter adds a line, and goals now display their line breaks); a refused save keeps the draft open with the reason under it, in plain words rather than the database's error text, which is logged instead. An owner whose quest has no goal sees "Add a goal" in its place. Clicking "Edit Quest" or a task's pencil straight from an inline field saves the field and opens the full form on the new value, not the old one, and the form's save waits for that inline save to settle before it sends, so neither the old title nor an older inline request can land over what the form saves (QuestInlineDraftsProvider carries a title or goal still in flight to the sheet and tracks its request; TaskManager does the same for a task title). The sticky mini-header now follows the page's h1 when the inline editor replaces and re-creates it, instead of staying bound to the old node. Task titles in the task list work the same way, sending only { title } to PATCH /api/tasks/:id; the pencil still opens the full form for details, due date, assignee and location. The shared control is components/ui/inline-editable-text.tsx, and PageHeader takes a new heading slot so the editor replaces the h1 rather than sitting inside it. The title and goal save through a new updateQuestInlineFieldAction() rather than updateQuestAction(), which reads the whole edit form and would have written a title-only payload as an unshared quest with no goal or context; it applies the same owner and archived-quest checks. Nothing is editable inline where the full form would refuse it: an archived quest, a challenge task's fixed wording, or, for a party member, a task not on their own seat. Not done here: the sheet is built on useModalFocus like the other dialogs and should become a variant of the shared Dialog primitive once #648 lands (#756).

The quest page's party panel is one row of avatars by default instead of 500–700px of roster administration. PartyQuestPanel used to give every member a bordered box with a role chip, a progress line and a bar, then put the owner's three forms (invite by email, bring in a guild, hand over this quest) on screen expanded on every visit, so "Hand over this quest", a rare and consequential action, carried the same weight as the task list. The default view is now the heading, a "7 members · 1 invitation pending" line, and a strip of avatars (the profile picture or initials) with a ring that fills with the share of each member's assigned tasks that are done, a crown on the owner, and a "+N" chip for the rest once there are more than six (PARTY_STRIP_LIMIT), which keeps the strip on one row in the quest page's 320px rail. Each avatar and the chip is a button: a tap, click or Enter opens one detail line under the strip with that member's name, role and progress (the chip lists the members it hides), pressing it again or Escape closes it, and the same facts are its accessible name and hover title, so a member on a phone or a keyboard, who has no other roster on the page, can still tell who is in the party. Everything else is behind a collapsed "Manage party" section, the same FormSection disclosure the New Quest form uses: a compact member list with an icon-only Remove for each member, the pending invitations with Resend and Revoke, the invite form, the guild picker and the handover. Handing the quest over is now two steps: choosing a member enables "Make owner…", which shows "Make {name} the owner?" with Confirm handover and Cancel (focus moves to Cancel), and only the confirm button submits; changing the selection withdraws the confirmation. A party member's "Leave Party Quest" is a small button in the card header, and every control in the card is size="sm", with the selects and inputs matched to its 36px height. The card keeps id="party", so the owner's "invitation accepted" emails still land on it. Not changed: the server actions, including transferQuestOwnershipAction, and who can see or do what (#754).

The quest page is two columns from lg (1024px) and its tasks start in the first screen. The main column holds the title, a new "3 of 8 tasks" progress bar under it, the goal, the owner's toolbar, then the tasks and the discussion; a 320px rail (360px from xl) beside it holds a new Details card, the reference links (two across instead of a scrolling strip, through QuestImageStrip's new layout="grid"), the party, context and constraints, attendance and the chronicle, and sticks under the app bar with its own scroll. The Details card (components/quests/quest-details-card.tsx) is one definition list of owner, last update, schedule, due date, theme, model, challenge and streak: the dot-separated meta line, the schedule pill, the challenge row and the cycle-streaks box (each a framed block with its own gap, all above the tasks) are gone, and the due-date badge moved out of the title row into it. Once the title scrolls out of view a mini-header pins under the top bar (QuestStickyHeader, an IntersectionObserver on the page's h1; for a signed-out visitor on a phone, whose public header is sticky from md only and scrolls away, it pins at the very top instead, through the new topBarStickyFrom prop) with the title, status, a 120px progress bar with "N/M", and for the owner the status's first transition (Start, Mark Complete, Reopen or Unarchive, through QuestLifecycleActions' new primaryOnly; an attendance quest that cannot be completed yet gets no button rather than "Mark Failed"). The header and the mini-header read the counts from QuestProgressProvider, which the embedded TaskManager updates as tasks change, because the task list never re-renders the page and server-rendered counts would go stale on the first tick; the task section's own progress card is removed, since the header states the same thing. CompleteQuestDialog and NarrativePanel's chronicle offer now render into <body> through a portal, so neither the mini-header's nor the rail's sticky stacking context can put a modal under the app bar. Below lg the page is one column with the rail after the main column, so the tasks come straight after the toolbar instead of below the party panel's forms. The #party anchor in owner emails still resolves, with a scroll margin that clears the app bar and the mini-header; the loading skeleton has the same two-column shape. Not done here: a compact party panel, which is tracked separately, and the back button, which signed-in visitors already lost to a breadcrumb in #743 (#753).

/quests/public can now be searched, filtered by status, sorted and paged, and every public quest is reachable: the page used to read no query params and stop at the 50 most recently updated, so the 51st was unreachable. The header keeps its eyebrow and title and drops the description that restated both; its action slot holds a search field (title or goal, case-insensitive, literal text, so "50%" and "run, walk" find exactly that) and a sort menu (Recently updated, the default; Most progress; Newest). Status chips with counts sit below, reusing the Quests index's QuestFilters in a new index="public" mode that drops the ownership chips and hides any status with no public quests, since nearly all of them are active. Pages are numbered rather than "Show more": 24 quests each, "Showing 25–48 of 60", Previous and Next, and a page past the last redirects to the last. All of it lives in the URL (?q=&status=&sort=&page=, parsed by the new lib/quests/public-index-params.ts), and an unknown or redundant value redirects to the canonical URL as on /quests. The read is the new listPublicQuestIndex(), which replaces listPublicQuests(): because the catalogue spans every user's quests, the filtering, ordering and paging happen in Postgres (one range() read per page, one head count per status chip), and task counts and owner profiles are read for the page's quests only; "Most progress" alone reads every matching quest's id and task counts to rank them, quests with no tasks last. The grid goes four across at xl. Each card clamps its goal to three lines, so one long goal no longer sets its row's height, states its task counts once ("3 of 8 tasks · 38%", or "No tasks yet") instead of three times, and shows "Updated 3 days ago" beside Copy in its footer. A search or filter with no match says what was filtered and offers "Show all public quests"; a failed read now says so instead of showing "No public quests yet." (#752).

/quests can now be searched, sorted and narrowed, and holds four columns of cards or a compact list. A toolbar above the chips has a title search (case-insensitive; the list follows the field after a 300 ms pause, and Enter searches at once, including before the page has hydrated) and a sort menu: Next scheduled (the default), Recently updated, Progress and Title. Beside the status chips sit three ownership chips: Owned, Party (any quest with more than one member, including ones you own, the same rule as the card's "Party Quest" line) and Public, each toggling off when chosen again. Every chip shows how many quests choosing it would list, counted under the other filters, and is at least 36px tall instead of 28px; Failed and Archived are hidden while they would show 0, unless one is the active filter. All of it lives in the URL (?q=&status=&scope=&sort=&page=, parsed by lib/quests/index-params.ts), so reload, back and a shared link show the same list; an unknown or redundant value (?status=bogus, ?page=1, a padded search) redirects to the canonical URL rather than being ignored. The list shows 24 quests at a time with "Showing N of M" and a "Show more" link that extends it in place (?page=N renders the first N×24). The read behind it is the new listQuestIndex(): one narrow select of every quest row the viewer can list (no task data) does the search, the counts and every sort but Progress, and only the quests actually shown go through the per-quest task, party, persona, theme and due-date reads, so a long history no longer pays for task counts on every quest ever made; Progress has to count every matching quest's tasks to rank them, and does, with quests that have no tasks last. The grid goes sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-4, and from lg a card puts its status badge above the title with tighter padding (QuestCard's new compactFromLg), because three- and four-up cards are about 240px wide. A Cards | Rows toggle switches to one line per quest (components/quests/quest-row.tsx: status, title, progress bar with a done count rather than a percentage, scheduled date, party icon, updated time, and a "No activity" marker for a stalled quest, whose Check in and Snooze controls stay on the card layout and the dashboard); the choice is kept per browser in the questify-quest-density cookie, so the server renders it on first paint. A filtered list that comes back empty now says what was filtered ("No completed party quests match “run”.") and offers "Show all quests" instead of "Create a quest", which could not change the result (QuestList's new emptyAction); "Create a quest" remains for an account with no quests, which also no longer shows the toolbar or chips. The header lost its "Your adventures" eyebrow, the page's vertical rhythm tightened from space-y-8 to space-y-5, and "Repeat weekly" is a small outline button like the dashboard's actions (#751).

The dashboard now lists what is due. A "Due this week" section at the top of the main column shows the open tasks due within the next seven days or already overdue, overdue first, each with its quest (linked), the DueDateBadge, and the task row's own status button (Todo → In progress → Done, Blocked → Done) so a task can be advanced or completed without opening its quest. The first eight show; "Show N more" opens the rest in place (up to 50, the function's limit, with a "Showing the 50 soonest" note when it comes back full), because /tasks loads only quests the user owns and could not show a party member the tasks on their own seat. The list reads only tasks on active quests the user can actually write, the same line user_can_write_quest_task() draws: every task on a quest they own, and on someone else's Party Quest only the tasks assigned to their own seat, so the dashboard never shows a button that can only fail. The read is listDueTasks() in lib/dashboard/due-tasks.ts, one call to the new get_my_due_tasks(), and it joined loadDashboardBody(); a failed read shows an error line rather than an empty week, and a quiet week renders nothing. The status button goes through the existing PATCH /api/tasks/:id, so its quest-status and permission gates are unchanged, shows any achievement unlock in the usual toast (kept on screen even when that completion empties the list), and refreshes the page afterwards so a finished task leaves the list and the statistics catch up; until that refresh lands, a finished row stays disabled, because one more click would cycle it from Done back to Todo. The Completion tile now links to /tasks, with the quest card's hover shadow, whenever the user has an active quest: it counts tasks on their own active quests, and /tasks given no ?questId= now opens the most recently updated active quest (pickInitialQuestId() in lib/tasks/types.ts) instead of whichever non-archived quest was touched last, which could be a draft or a finished one. The other three stay unlinked because no page lists exactly what they count: no page lists a streak; Tasks done is a lifetime count that includes archived quests, which /tasks leaves out; and Active quests counts owned quests while /quests?status=active also lists the Party Quests the user belongs to, so a link could open a list that disagrees with the number on the tile. QuestCard no longer repeats its task ratio as a percentage beside the bar: it shows "N open · next due {date}" (or "All done"), from a new next_due_at on QuestSummary that listQuests() reads through the new get_quest_next_due_dates(); a failed read leaves the date off rather than failing the list. Both reads go through functions because tasks.due_at has been withdrawn from direct client reads since #570, and selecting it would have failed every quest list. Not done here: the card's "Open tasks" and "Start" quick actions, which need the title-only link from #750 so the buttons are not nested in an anchor (#749).

The dashboard is two columns from xl (1280px) up, and its greeting is a bar instead of a panel. The greeting spans the top; below it, the "Recently updated" preview takes the main column as one row of four cards (from xl a card puts its status badge above the title and uses tighter padding, through a new QuestCard compactFromXl prop, because at 1280px each card is only about 154px wide), and the statistics (back to 2×2), Up next, cycle streaks and the theme/challenge slot move into a 20rem rail on the right, so a returning user sees their recent quests without scrolling. Below xl the page is the same stack in the same order as before: the rail is display: contents there, so nothing is reordered and tab order matches what is on screen. The grid classes live in components/dashboard/layout.ts, shared with the loading skeleton so the placeholder has the same shape. DashboardBody is split into DashboardRail and DashboardQuests, two Suspense boundaries reading the one promise the page starts, so they resolve together. The greeting bar (WelcomeHero) dropped its "Dashboard" eyebrow and its padding, puts the subtext beside the heading from sm, and is about 64px tall instead of 170; it still owns the page's h1. "Up next" is a small uppercase label beside a calendar icon instead of an eyebrow plus a large title, still an h2 naming its region; the "Recently updated" header lost its "Quests" eyebrow. The cycle streaks' two-line explanation moved behind an info button beside the heading, a native <details> popover. QuestList takes columnsClassName (default two-up, as before), showStartSteps and compactCardsFromXl; its empty state is p-6 sm:p-8 instead of p-12 everywhere it appears, and on the dashboard it adds a "1. Create a quest → 2. Add its tasks → 3. Start it" hint. Not done here: the greeting bar's "N tasks due this week" summary, which needs the due-date read #749 adds (#748).

Every page outside the signed-in app shell now has a site header. components/layout/public-header.tsx is a Server Component that reads the session and draws two variants. The full one has the wordmark linking to /, the public catalogue (Public quests, Quest Packs, Challenges, Quest Jams, and Pricing only where NEXT_PUBLIC_FEATURE_BILLING is on), and Sign in plus Create a free account; a signed-in visitor gets Back to dashboard and an avatar link to /profile instead. It is sticky with a backdrop blur from md up; on a phone it shows the wordmark and Sign in only, and the catalogue links appear from lg, where they fit. The compact one has the wordmark and one action: Sign out for a signed-in visitor, otherwise Sign in (Create a free account above the sign-in form itself). A signed-out visitor's Sign in and signup links carry ?next= back to the page they are on, so signing in from the header of an invitation link or a shared quest returns there; on an auth screen they forward that screen's own next, on the landing page they carry none, and on /notifications/unsubscribe they return to /profile, because that page only works with its ?token=, which is never copied into the login URL. The landing page, /pricing, /privacy and /terms moved into a (public) route group whose layout renders the full header; onboarding, both invitation links and /notifications/unsubscribe moved into a (standalone) group with the compact one; app/auth/layout.tsx renders the compact one in place of its small-caps "Questify" link; and the (app) layout's signed-out branch renders the full one, replacing the Sign in / Create account / Home buttons that /quests/public, /quest-jams and /challenges each drew in a different size. URLs are unchanged. Before this, a signed-out visitor had no way to sign in from the landing page, the word "Questify" first appeared in section two, pricing and the legal pages had only browser-back and a footer as exits, and someone signed into the wrong account during onboarding had no exit but "Skip setup". The legal pages' bottom "← Back to Questify" link is gone in favour of the wordmark. Signup, sign-in and browse buttons now share one vocabulary from PUBLIC_CTA in lib/navigation/public.ts: "Create a free account", "Sign in" and "Browse public quests" replace "Start your quest", "Create your free account", "Start your free quest", "Create account", "Create an account", "Browse quests" and "Explore public quests". Not changed: the Pro card's "Sign up to subscribe", the sign-in card's inline "Create one", and the footer links, which #504 tracks. Rendering is unchanged: every page was already dynamic because the root layout's feedback button reads the session (#746).

Navigating between signed-in pages no longer leaves a blank content column, and a failed page read no longer drops anyone on Next's unbranded error screen. app/(app)/loading.tsx and app/admin/loading.tsx show a skeleton of the shared page header and a card grid inside the shell, so only the content column pulses; the dashboard, quest detail and task workspace get their own loading.tsx that mirrors their real layout. app/(app)/error.tsx and app/admin/error.tsx keep the shell and navigation, show the error digest as a reference (never the raw message) and offer "Try again", which refreshes the route before calling reset() so a failed server read is actually retried. app/not-found.tsx replaces the bare "404 This page could not be found" — /pricing with billing off, a quest that does not exist — with a branded page that links home, under the shared footer. The dashboard now paints its welcome hero and statistics first and streams the theme row and quest preview in behind <Suspense>: the reads moved into loadDashboardBody() (lib/dashboard/body.ts), which the page starts before awaiting the statistics so nothing runs later than it did. Not done here: the quest detail page still awaits its party and attendance reads up front, because the header's owner controls and the task list both depend on them. Sign-in redirects stay real 307s: /profile, /settings and /quests/recurring joined PROTECTED_PATH_PREFIXES (they redirected only from the page, which under a loading boundary can only stream a client-side redirect inside a 200, and a signed-in visitor with onboarding pending is now sent to the wizard from them like from every other signed-in page), and the middleware probes a logged-out /quests/<uuid> request with a one-column RLS read, sending a quest the visitor cannot see to login before the page streams; a failed probe falls through to the page. What remains streamed: a page's own notFound() after its skeleton — a quest or Quest Jam that does not exist for a signed-in viewer, a flag-off page — answers 200 with a noindex tag rather than a 404 (#744).

Every page in the (app) route group now uses one width scale and one header. components/layout/page-container.tsx renders the page's <main> at width="default" (max-w-6xl), "wide" (max-w-7xl) or "narrow" (max-w-2xl, used only by New Quest, New recurring Quest, Start a Quest Jam and the yearly recap) with the same px-4 py-8 padding. Before this, pages picked their own cap anywhere from max-w-2xl to max-w-6xl, and the quest detail page left about a third of the content column empty. components/layout/page-header.tsx replaces five hand-rolled header variants with one serif h1 plus optional eyebrow, description, right-aligned actions and breadcrumb slots. The task workspace on /tasks uses it too. Signed-in visitors to quest detail, Quest Jam detail, a guild page and the yearly recap now get a breadcrumb in place of the back button, because the side bar already links every section that button pointed at. Signed-out visitors to a public quest or a Quest Jam have no app shell, so they keep the back button. /tasks and /quests/public no longer set min-h-screen inside a shell that already fills the viewport, so short pages stop scrolling past a dead strip. The dashboard keeps its greeting hero as the page title for now; the dashboard rework replaces it (#743).

The Challenges page's History is a compact, filterable, pageable list. Each run is one ~52px row — challenge title over "Weekly · Week 40, 2026" (or "Daily · Sep 30"), status over its date, and a ghost "Open quest" — instead of a ~170px card that repeated the prompt and the Challenge Runner pill on every attempt; 24 runs went from ~4,000px to ~1,250px. The subtitle no longer leaks the machine period_key ("Weekly challenge - 2026-W40 - …"): formatChallengePeriodKey() beside getCurrentChallengePeriod() says it as a week number or a UTC date, and returns nothing rather than the raw key for one in neither shape. History was silently capped at the newest 24 runs; it now has All · In progress · Completed tabs that count what they hold (?history=), "Showing 25–48 of 60" with Newer / Show older (?page=), an empty-tab message with a way back to every run, and redirects a non-canonical or past-the-end URL — for signed-in visitors only, since the page is public. listChallengeHistory() takes { filter, offset, limit } and pages by range with an id tie-break, and countChallengeHistory() supplies the tab counts. On "Open now", a challenge the viewer has started or finished folds its constraints and task list behind a "3 tasks" disclosure and shows In progress / Completed in place of the Challenge Runner pill, so the card is mostly its way back to the quest; Start challenge now says what it will create ("Creates a quest with these 3 tasks."), and a refused start renders under the button in the card footer instead of above it (#768).

The unsubscribe page's error state now lets the action that failed be tried again (#776). A failed "Turn on" or "Turn off" of another category, or a failed "Stop all Questify emails", sent the person back to a page that offered only a "Stop {the email's own category}" button and no list, because the redirect carries only the email's own category — so the one thing on offer was not what they had asked for, and a failed "turn back on" of the email's own category got a "Stop" button too. The page now reads the current preferences on status=error the way it does after a change, lists every category (the email's own included, with no headline button to duplicate its row) with the button its current state calls for, and keeps "Stop all" while anything is on. The headline button remains only when that read fails, so a page with nothing to retry from never appears. The route is unchanged.

The sign-in and sign-up pages were tidied up (#780). A failed sign-in that comes back through /auth/callback now says what happened: the callback's three ?error= codes (oauth_denied, missing_code, callback_failed) each show their own message in a destructive alert on /auth/login, where before the page never read error and cancelling Google consent landed on a blank form. The codes and their copy live together in lib/auth/callback-errors.ts, and the route now takes its codes from the same table. The auth tabs read "Sign in | Questify" rather than "Sign in · Questify | Questify": the five auth pages dropped their own "· Questify" suffix and leave the brand to the root title template. Every password field (sign-in, sign-up, both reset fields) is now a shared PasswordInput with a show/hide toggle, a toggle button whose name stays "Show password" while aria-pressed carries the state. Each form focuses its first field on load. Google and Facebook buttons now sit above the email form on sign-in as well as sign-up, under an "or continue with email" divider, so the two pages match; OAuthButtons lost its position prop. The auth column is top-aligned and only as tall as the card, so the footer follows it instead of sitting a full screen below with empty page above it. The legacy /login is a permanent (308) redirect that keeps a safe next, and it is now in AUTH_ONLY_PATHS (as LEGACY_LOGIN_ROUTE), so a signed-in visitor goes to the dashboard in one hop instead of two. Fields only reference their error element in aria-describedby while the error is on screen, and are marked aria-invalid then (fieldA11y in components/auth/field-error.tsx), which clears the dangling IDREFs axe reported; the sign-up password hint stays described throughout. The in-app pages that still carry "· Questify" titles are left for a separate change.

The light-only status chips — achievement rarity badges, Quest Jam status pills, the AI credit warnings and the completed-challenge card — gained dark variants, since dark mode can now be chosen and was never rendered before (#770).

A visitor reading someone else's public quest now sees each task's status the way signed-in views show it. The read-only task list (QuestTaskList) labelled status with a hand-rolled coloured dot and a plain grey word; it now uses the shared TaskStatusBadge, clamps a task's details to two lines (keeping their line breaks) so one long description no longer pushes the rest of the list off the screen, and wraps long unbroken titles instead of overflowing on a phone. Its heading no longer repeats "N/M done", because the quest header's progress bar already states it to every viewer, which is also why TaskManager dropped its own count in #753. Deliberately not added: task due dates, which have belonged to collaborators even on a public quest since #570 (20260914120000_due_date_privacy.sql), so get_quest_with_tasks() never returns them to a visitor. The issue's other half, the header's badge column squeezing a long title on a phone, needed no change: since #743 and #753 the title sits in PageHeader, which puts the status badge on its own row under the title below sm, and the due-date badge moved out of the header into the Details card, so the date-only DueDateBadge variant the issue proposed has nowhere to go (#757).

A draft, completed, failed or archived quest's page now says once why its tasks are locked, instead of twice (three times when archived). The header's lock notice sits beside the Start, Reopen or Unarchive control that lifts it, and the embedded task list repeated the identical sentence about 400px lower; it is now told not to, through TaskManager's new showLockAlert prop (default true), which drops only the notice — the progress and edit controls stay exactly as locked. For an archived quest the header now reads "This quest is archived. Unarchive it to make changes." (describeQuestWriteBlock(), the sentence the server action already refuses with), since the freeze covers the quest's own fields as well as its tasks, and the owner toolbar's separate "Archived quests cannot be edited. Unarchive this quest to change it." line is gone. /tasks is unchanged: it has no quest header, so its task list keeps stating the lock (#755).

Quest lists no longer under-count tasks or party members for someone with a lot of them. listQuests() read every listed quest's tasks, and their party seats, in one request, and PostgREST stops at max_rows (1000) without saying so, so past the thousandth task the cards' counts and progress bars silently came up short. The viewer's own seats were read the same way, so past a thousand of them joined quests dropped out of the list and owned ones lost their role and assigned-task counts. All three reads now page until a short page comes back, and the two per-quest ones send quest ids 100 to an in.(…) filter, which also keeps a long list from producing a request URL too long to send. For the same reason the quest reads no longer list the quests the viewer owns in their id.in.(…) party filter (they already match owner_id), /quests reads joined quests by id 100 at a time instead of in one filter, and next due dates are asked for 100 quests per call. This applies to every caller: /quests, the dashboard preview, the profile page, the theme hub and GET /api/quests (#751).

Quest cards no longer put buttons inside a link. QuestCard wrapped the whole card in an <a>, so the stall banner's Check in, Snooze, suggestion and dismiss controls (and its snooze menu) were interactive content inside a link: invalid HTML, announced by screen readers as one long link, with a click-trap div that had no keyboard equivalent and a check-in dialog whose backdrop click fell through to the link. The title is now the only link, and a stretched ::after overlay (lib/a11y/stretched-link.ts) keeps the whole card clickable. The banner is a sibling raised above that overlay (relative z-10), so Tab reaches the title and then each banner control separately. Its buttons are now 32px tall (h-8, up from 24px), the dismiss target is 32×32 (from about 18px) and snooze menu items are at least 32px. The Quest Jam card on /quest-jams (now components/quest-jams/quest-jam-card.tsx) has the same shape, which leaves room for an inline action later; no Join button is added here. On /quests/public, PublicQuestCard drops the second "View details" link to the page its title already opens. The title is stretched over the card instead, and "Copy to my quests" is outlined (CopyPublicQuestButton's new variant prop), so a grid of a dozen cards no longer shows a dozen solid primary buttons. The quest page keeps the solid button. (#750)

The feedback button no longer covers primary buttons on phones or appears on pages with nothing to give feedback on. It was mounted in the root layout, so every signed-in route drew a fixed bottom-4 right-4 button over the bottom-right of the page, including every onboarding step's full-width Continue, the full-width Join on both invitation pages and the Delete/Cancel row on the profile page, and it showed during onboarding before the user had seen the product. FeedbackButtonGate is gone; a new client FeedbackProvider (components/feedback/feedback-provider.tsx) owns the one dialog and its confirmation toast and is mounted only by the (app) shell (AppShell now takes userId) and the /admin layout, so /onboarding, /guild-invites/*, /party-invites/*, /notifications/unsubscribe and the (public) pages render no feedback control. The floating button is now md-and-up only; below md "Send feedback" is a row in the top bar's account popover (at every width) and in the mobile drawer, and in the admin drawer, all opening the same dialog through useOpenFeedback(). The dialog now takes focus on its Title field when it opens, and on close focus returns to a control that is still on screen (the account-menu button or the drawer toggle, since the menu row that opened it is gone by then, or the floating button) instead of falling to the page behind the overlay. Inside the dialog, the read-only Page URL field became a one-line muted "Sent from …" caption (still submitted with the report), and the Type radios became 44px chip radios in the onboarding profile step's style. Not changed: a signed-in visitor on /pricing or the legal pages, which sit outside both shells, no longer gets a feedback control there (#747).

Dates and times now render in the viewer's own locale and timezone everywhere an instant is shown, and the due badge no longer paints a raw ISO string before hydration. Before this, DueDateBadge first rendered Due · 2026-10-03T18:00:00.000Z and then reflowed; Quest Jam windows, "Updated" on quest cards and the quest header, the yearly recap's "Stats last computed", billing renewal dates and the admin dashboard, audit log and feedback pages were formatted on the server, so an EDT viewer saw UTC; and guild and party invitation expiry was pinned to en-US in UTC. The new client component components/ui/local-datetime.tsx provides <LocalDateTime value dateStyle timeStyle format relative /> and <LocalDateRange start end />: both server-render a deterministic, hand-built UTC string (2026-10-03 18:00 UTC, so it is identical in Node and every browser and never mismatches on hydration), swap to the viewer's Intl rendering after mount, and keep the exact instant on a <time dateTime> element throughout; relative shows "3 hr. ago" with the absolute time as its title and refreshes every minute. Every call site listed in the issue moved onto it, as did the comment thread, task investigations, the admin feedback list and GitHub-issue card (whose prop is now the associatedAt timestamp rather than a pre-formatted label), the narrative panel, the admin user list and the Quest Jam join and admin panels. formatQuestJamDateRange() is gone in favour of QUEST_JAM_WINDOW_FORMAT in lib/quest-jams/queries.ts. Deliberately unchanged: QuestScheduleWindow still renders in the quest's own pinned timezone; labels for UTC calendar periods (the daily and weekly challenge dates, the admin AI-spend month names) stay in UTC because they name a UTC day or month rather than an instant; invitation emails keep their fixed format because there is no viewer zone to read; and numbers formatted with toLocaleString() are out of scope (#745).

safeInternalPath() now refuses a path containing ASCII control characters (#776). The WHATWG URL parser strips tab and newline before it resolves, so /\t/attacker.example passed the old // check and then resolved to https://attacker.example/ in new URL() and in the browser — an open redirect through /auth/callback?next=… and the login and signup next parameters. Spaces are still allowed, because a decoded search query can carry one.

The recap Open Graph image no longer renders any user's stats by user id. /api/recap/<year>/og?uid=<id> read the recap and display name through the service-role client for anyone who had (or guessed from another page) an id, and the owner's recap page put that id in its metadata. The image is now served for a share link through get_shared_well_played_recap(), so it exists only while the owner shares that year and stops when they revoke it, or for the signed-in owner from their own session; the route uses no service-role client, and a ?uid= request is treated as an unauthenticated one (401). A preview already cached by a chat app from an old ?uid= link keeps its image until that app refreshes it. A recap's share link can only be written by the sharing function, so a revoked link can never be re-pointed at someone else's recap (#772).