feat: upgrade SST from v3 to v4.3.6

[PavolJediny]

Summary

• Upgrades SST from v3.17.19 to v4.3.6 (Pulumi AWS provider v6 → v7 under the hood)
• Regenerates sst-env.d.ts files with new biome-ignore-all directive added by SST v4
• Cleans up unused transitive dependencies (@aws-sdk/client-dynamodb, mnemonist, obliterator) from lockfile

Notes

• No code changes required — project uses only SST components without direct @pulumi/aws usage
• All SST component APIs are unchanged in v4: sst.aws.Function, sst.aws.StaticSite, sst.aws.Dynamo, sst.aws.StepFunctions, sst.x.DevCommand
• Default Lambda runtime changed to nodejs24.x in v4, but the project explicitly sets nodejs22.x via $transform
• SST issue #6564 (missing lambda:InvokeFunction permission for Function URLs) was fixed in v4.2.6 — the manual aws.lambda.Permission workaround in infra/api.ts can be removed in a follow-up
• No deployed state exists, so no sst refresh migration is needed

Post-Deploy Monitoring & Validation

No additional operational monitoring required: this is a dependency version bump with no deployed state. Verify with pnpm sst dev after merging.

---

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: purple-technology/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 599b4abd-7a0a-4117-9bd7-3aa1d9b95174

📥 Commits

Reviewing files that changed from the base of the PR and between 594abe4 and 996e523.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (8)

• domains/transaction/sst-env.d.ts
• packages/core/sst-env.d.ts
• packages/sst-extensions/sst-env.d.ts
• packages/trpc-api/sst-env.d.ts
• packages/tsconfig/sst-env.d.ts
• pnpm-workspace.yaml
• sst-env.d.ts
• web/sst-env.d.ts

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Upgraded SST framework dependency from 3.17.19 to 4.3.6
  • Applied lint ignore directives to auto-generated type definition files across packages

Walkthrough

This pull request adds a lint-ignore directive (/* biome-ignore-all lint: auto-generated */) to multiple auto-generated TypeScript environment type definition files across the repository's package structure. Additionally, the SST framework version in the workspace catalog is updated from 3.17.19 to 4.3.6. These changes introduce no modifications to exported declarations, functional logic, or runtime behavior.

🚥 Pre-merge checks | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The pull request title does not include a task ID (e.g., PTT-123, MTE-123) as required by the specifications, starting with 'feat:' instead.	Prepend the task or issue ID to the title, e.g., 'PTT-168 feat: upgrade SST from v3 to v4.3.6' to comply with naming requirements.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/upgrade-sst-v4

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can use OpenGrep to find security vulnerabilities and bugs across 17+ programming languages.

OpenGrep is compatible with Semgrep configurations. Add an opengrep.yml or semgrep.yml configuration file to your project to enable OpenGrep analysis.