Merge 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.

Test Coverage

Please ensure your changes are adequately tested:

1. My changes are covered by tests (unit, integration, or e2e tests as appropriate).

If you're unable to add tests or if coverage is partial, please explain why below:

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 versioned 0.19.0 documentation with major reorganization (auth, data model, deployment, project/CLI/TS), a revamped tutorial with executable patches, and supporting site updates (sidebars, components, versions).

• Docs (v0.19.0):
  • Add comprehensive, versioned docs across auth (incl. hooks; Discord/Slack; social/email/username), data model (entities, operations, CRUD, Prisma schema), deployment (Wasp Deploy for Fly/Railway, self‑host, CI/CD, env vars), project config (client/server, Vite, CSS, testing), CLI/TypeScript/TS-config, telemetry, and introductions.
  • Update sidebars and versions to include 0.19.0.
• Tutorial:
  • Overhaul tutorial content with patch-based steps; add “Tutorial Action” components and a new tutorial-actions-executor package with tests.
• Site infra:
  • Add supporting docs components (env var tables, tags) and related content/assets.

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