Highlights
What this release added
- Sprint 43 (Milestone 9) closed with full phase coverage (0-8), including explainable autonomy decisions, follow-up suppression intelligence, and explicit user controls/kill-switch behavior.
- Deep research flow is now action-oriented in chat with `/research` and `/research-quest`, structured output (`Summary`, `Sources`, `Recommendations`, `Suggested quests`), and explicit research-to-quest confirmation.
- Sprint 43 closeout artifacts are now canonical and linked across milestone docs (`SPRINT_43_COMPLETION.md`, testing guide/report, backlog, roadmap, milestone README).
Fixes
What this release corrected
- Upgraded default OpenAI model routing to `gpt-5.1-2025-11-13`, set deep research model to `o4-mini-deep-research-2025-06-26`, and retained Pokee as fallback for deep research continuity.
- Enforced strict Sprint 43 value-gate checks by wiring CI workflows to `pnpm analytics:sprint43:value-metrics:ci` for automatic pass/fail KPI gating in pipeline runs.
- Added synthetic signup regression monitoring with hourly automation (`tests/e2e/signup-synthetic.spec.ts`, `.github/workflows/synthetic-signup-hourly.yml`).
- Removed stale Sprint 43 planning references and consolidated milestone-closure tracking into completion/test artifacts and backlog carryover entries.
- Documentation refresh after `v0.42.0` release: core setup, deployment, rollback, API, and testing docs now match current scripts and architecture.
- Upgraded Next.js toolchain to `16.1.5` (`next`, `eslint-config-next`, `@next/eslint-plugin-next`) to remediate `CVE-2025-59472` / `SNYK-JS-NEXT-15105315` from `next@15.5.10`.
- Updated `revalidateTag` usage for the Next 16 cache API and pinned production builds to webpack (`next build --webpack`) to avoid a Turbopack `_document` prerender failure.
- Forced transitive webpack resolution to `5.104.1` (via pnpm overrides and root dev dependency) to remediate `CVE-2025-68157` and `CVE-2025-68458` (`SNYK-JS-WEBPACK-15235969`, `SNYK-JS-WEBPACK-15235959`) in the Sentry bundler path.
- Pinned personalization service `aiohttp` to `3.13.3` to resolve the Snyk high/medium advisory set reported against `aiohttp@3.13.2`.
Known issues
What remained constrained
- Sprint 43 strict value gates remain below target in production strict mode (`multimodal adoption`, `memory retention lift`, `integrations per connected user`) and are tracked as explicit KPI carryover work.
- Build/E2E logs may still include non-blocking Tailwind config path warnings in local runs.