Sync from upstream

[Genyus]

Description

Describe your PR! If this PR closes an issue, use “Fixes #(issue_number)" syntax so GitHub will auto-close it when merged.

Select what type of change this PR introduces:

1. Just code/docs improvement (no functional change).
2. Bug fix (non-breaking change which fixes an issue).
3. New feature (non-breaking change which adds functionality).
4. Breaking change (fix or feature that would cause existing functionality to not work as expected).

Update Waspc ChangeLog and version if needed

If you did a bug fix, new feature, or breaking change, that affects waspc, make sure you satisfy the following:

1. I updated ChangeLog.md with description of the change this PR introduces.
2. I bumped waspc version in waspc.cabal to reflect changes I introduced, with regards to the version of the latest wasp release, if the bump was needed.

Add a regression test if needed

If you did a bug fix, make sure you satisfy the following:

1. I added a regression test that reproduces the bug and verifies the fix.

If you're unable to add a regression test, please explain why.
This likely indicates that our current testing setup needs improvement.

Update example apps if needed

If you did code changes and added a new feature, make sure you satisfy the following:

1. I updated waspc/examples/todoApp and its e2e tests as needed and manually checked it works correctly.

If you did code changes and updated an existing feature, make sure you satisfy the following:

1. I updated waspc/examples/todoApp and its e2e tests as needed and manually checked it works correctly.

Update starter apps if needed

If you did code changes and updated an existing feature, make sure you satisfy the following:

1. I updated starter skeleton as needed and manually checked it works correctly.
2. I updated basic starter as needed and manually checked it works correctly.
3. I updated todo-ts starter as needed and manually checked it works correctly.
4. I updated embeddings starter as needed and manually checked it works correctly.
5. I updated saas starter as needed and manually checked it works correctly.

Update e2e tests if needed

If you did code changes and changed Wasp's code generation logic, make sure you satisfy the following:

1. [] I updated e2e tests as needed and manually checked they are correct.

---

Note

Adds the kitchen-sink example app (auth, CRUD, jobs, websockets, streaming), updates SDK/server/web-app templates (env, routes, middleware, UI), tweaks Docker/env handling, and introduces Playwright e2e tests.

• Example App (kitchen-sink):
  • New full-featured app with Tailwind-based UI, layout, routes, and feature pages.
• Auth:
  • Email signup/login with verification and password reset; custom/manual signup flows.
  • OAuth providers added: Google, GitHub, Slack, Discord.
  • Auth hooks (before/after signup/login/email verified) and profile UI.
• Jobs / WebSockets / Streaming:
  • Async jobs (pg-boss) with uppercase-text example and schedules.
  • WebSocket chat feature with client/server integration.
  • Streaming API endpoint and test page.
• CRUD & DB:
  • CRUD for Task with update/delete, Prisma schema updates (enums, votes, requests), seeds, and Prisma setup hook.
• SDK/Server/Web App Templates:
  • New operations, API namespace/routes, middleware config, router generation, env validation, and UI components.
  • Improved server env handling (NODE_ENV defaulting) and package peer deps.
• Docker/Infra:
  • Dockerfile robustness (ensure node_modules path), workspace/package updates.
• Tests:
  • Playwright e2e tests for auth (incl. email), CRUD, custom APIs, jobs, WebSocket chat, streaming, serialization.
  • Snapshot updates across build/compile/migrate golden projects.

^{Written by Cursor Bugbot for commit 3b2034a. This will update automatically on new commits. Configure here.}