Questify

2.10.0

Released

Features

  • Populated the public quest browser with five polished, in-progress Questify Team quests spanning a side-project launch, fitness habit, language learning, annual reading theme, and one-week feature shipment. The curated owner cannot sign in and its static quests stay out of user stall metrics, while anonymous visitors can inspect 43 realistic tasks and their progress; the underlying examples also preserve Quest Pack provenance and a Year Theme tie-in (#505).

Fixes

  • Prevented system-owned Auth accounts such as the public quest curator from resolving as Party Quest invitees, avoiding accepted members that can never sign in or participate (#512).

  • Documented the two Stripe Dashboard customer-email settings required for subscription payment receipts and cancellation notices, including their per-account/per-mode scope and sandbox delivery restriction (#501).

  • Kept AI-coached quest creation from failing when a model returned an overlong task: concise task titles are now stored separately from detailed instructions, legacy string tasks are normalized safely, and the full generated context is preserved in task details (#497).

Technical changes· 1 entry for database, tooling, CI, tests and docs

CI/CD

  • Made the production Lighthouse audit share the release health check's configurable PRODUCTION_HEALTHCHECK_URL origin, defaulting to canonical https://www.questify.co instead of the redirect-only apex domain that made every target fail preflight with HTTP 307, and extended its stable public-page coverage to the production-only /pricing surface (#508).