Wizzo v0.50.0 Release Notes
Released Jun 2, 2026Public Beta
Highlights
- Added the first v0.50 Today/Journey command-center slice: Journey now promotes one transparent Today plan with due, time, label, priority, source, and recent-behavior signals plus accept, snooze, complete, and chat handoff telemetry.
- Added structured connector context to the v0.50 Today/Journey command center so connector-created quests carry safe connector labels and the Today plan can explain Gmail, Calendar, GitHub, or Drive provenance without exposing raw connector event IDs.
- Added contextual chat tool guidance so the tool menu can recommend web search, deep research, document analysis, code execution, or image generation from the current draft, Journey or voice handoff state, and attached files while preserving explicit confirmation gates.
- Added the first Microsoft 365 connector implementation slice with source-specific Outlook Calendar and OneDrive registry entries, least-privilege Graph scope policy, Pro-preview gating, and attribution/retention guardrails for connector-derived suggestions.
- Added Microsoft 365 OAuth connection lifecycle support for Outlook Calendar and OneDrive, including signed consent state, token/profile persistence, settings-panel connect/disconnect controls, and local token deletion after the final Microsoft 365 source is disconnected.
- Added Microsoft 365 live Graph read support for scoped Outlook Calendar event metadata and selected OneDrive item metadata, including token refresh, sanitized activity provenance, and source-attributed suggestion inputs without event bodies, file contents, or download URLs.
- Added the Microsoft 365 OneDrive selected-file UX so users can preview and confirm a OneDrive or SharePoint file for source-backed suggestions while Wizzo reads metadata only.
- Added the Personalization Control Center in Settings so users can inspect safe recommendation signals from goals, quest labels/time estimates, memory keys, connectors, and feedback, then down-rank or restore noisy signals without exposing raw memory values or connector content.
- Upgraded the managed OpenAI primary/search/document-analysis defaults to `gpt-5.5`, with updated model registry metadata and GPT-5.5-oriented chat prompt guidance.
- Reworked first-run quickstarts and the Pro upgrade path around a first meaningful win, with privacy-safe activation and checkout-intent telemetry.
- Extended Journey voice check-ins into review-first follow-through actions: save an edited transcript to an existing quest, create a follow-up quest draft, or hand off to chat.
Fixes
- Removed the LogRocket session-replay integration, public app ID, CSP allowlist entries, and third-party replay package in favor of first-party, consent-gated client telemetry for product health signals.
- Rebuilt the active and future backlog around the `v0.50.0` milestone so the active queue contains only release-confidence, core-loop, AI, connector, personalization, onboarding, voice, and launch work needed for Wizzo 0.5.
- Restored the `v0.50.0` CI path by hardening MCP connector settings against incomplete automation snapshots, fixing Work Connectors contrast, and aligning Pro billing E2E assertions with current upgrade copy.
- Added the v0.50.0 release readiness gate, including a Release Approval Attachment Template and `pnpm validate:v050-readiness` coverage for activation, Today/Journey, chat tools, memory, connectors, voice, billing, production promotion, rollback, and 24-hour monitoring evidence.
- Updated the release-research validator so promoted Microsoft 365 connector implementation work can live in Active Backlog without breaking `pnpm validate:production`.
- Removed stale TechWeek-specific defaults from the public first-run quest prompts.
- Expanded voice Journey evidence to track accepted quest updates and explicit follow-up quest creation in addition to transcript completion, chat handoff, and return-session behavior.
- Realigned the billing-tier production validator with the current first-win Pro upgrade copy.
- Hardened production scheduler telemetry ingestion and share-nudge sweeps so optional monitor, alert-processing, and community-nudge failures are logged as degraded scheduler responses instead of hosted `500` responses, with summary counts included for scheduler evidence.
- Hardened the Personalization Control Center against incomplete control snapshots so Settings remains available during hosted accessibility checks and legacy/mock payloads.
- Made the release announcement persistent until users open the release notes or dismiss that version, instead of auto-expiring before the update can be read.
- Removed the normal assistant-message card background from active chat so Wizzo replies read on the page canvas like a native conversation, while preserving the small Wizzo avatar marker.
- Reframed Vault Security as Locked Notes, moved private-note status into the profile/settings cluster, and hardened encrypted private-note handling with verifier checks, portable salt metadata, API rejection of plaintext private notes, and safer client logging.
- Fixed Locked Notes privacy toggles in Trials so the current note content is encrypted or restored with the privacy change, optimistic privacy changes roll back on persistence failure, and synced preview/production quest schema columns that caused quest APIs to return hosted `500` responses.
- Hardened Trials against stale locally stored quest IDs so Locked Notes privacy actions fall back to the current server quest record when possible, and otherwise explain that the quest must be refreshed or recreated before privacy can change.
- Fixed the `/api/quests/[questId]` compatibility route so quest updates pass the actual quest ID to the legacy task handler instead of returning false `404` responses for valid Locked Notes updates.
- Kept actionable chat-generated suggestions visible during active conversations while still hiding empty suggestion modules, moved persistent release announcements away from mobile bottom CTAs and auth routes, and made achievement-feed parsing tolerate malformed summary payloads.
- Restored hosted `master` release-confidence checks after the v0.49.0 release, redeployed production to the scheduler fix, reran Production Scheduler green, and retired the obsolete legacy Snyk commit-status bridge while keeping the repo-owned Snyk scan and monitor workflows.
- Added the v0.50.0 launch packet and 24-hour post-release monitor so release approval, GitHub release copy, production promotion, rollback ownership, marketing handoff, and closeout evidence are ready before the release tag.
Known issues
- _None approved at tag time._