Highlights
What this release added
- Added connector-aware smart quest suggestions so opted-in Calendar, Gmail, and Google Drive MCP activity can create attributed next-action prompts with acceptance/follow-through telemetry.
- Repositioned `/journey` as the daily "Today" cockpit: sidebar hierarchy now puts Today before Trials, and the page now uses a decision-first command surface, weekly pulse cards, and a capped next-move queue instead of duplicating full management dashboards.
Fixes
What this release corrected
- Confirmed the production scheduler hosting plan with owner, credentialing, monitoring, fallback, and scale-exit criteria before pilot scaling.
- Recorded release-owner signoff for manual assistive-technology certification and the legal stable/GA review waiver, clearing two P0 security/compliance blockers from the active backlog.
- Added a legal counsel review packet and tightened privacy-policy copy so AI interaction, security, breach-notice, deletion, backup-retention, analytics, and cookie-consent disclosures do not overpromise before counsel approval.
- Lazy-loaded LogRocket only after optional analytics consent so the session-replay package is not initialized or loaded before the user opts in.
- Removed legacy Journey dashboard clutter from the default route, including inline achievements breakdowns, enterprise upsell previews, activity analytics, and hidden chat/dashboard modules.
- Deleted orphaned legacy Journey dashboard modules for progress overviews, points breakdowns, streaks, activity feeds, cohort insights, intelligent reminders, and AI goal recommendations so unsupported retrospective/heuristic surfaces no longer ship as hidden code.
- Sanitized AI-generated quest snippets on Journey so markdown and internal conversation/auto-insight artifacts are not shown in the daily action list.
- Fixed the client-side release version source so upgrade toasts and release UI use the generated Wizzo package version instead of falling back to stale `v0.21.2`.
- Added a manual assistive-technology certification packet and made the high-contrast/reduced-motion settings controls verifiable before human screen-reader signoff.
Known issues
What remained constrained
- _None yet_