fix(deps): update dependency three to ^0.184.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
three (source)	^0.183.0 → ^0.184.0

---

Release Notes

mrdoob/three.js (three)

v0.184.0

Compare Source

---

Configuration

📅 Schedule: (in timezone America/Sao_Paulo)

• Branch creation
  • "on thursday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
frontend	Ready	Preview, Comment	Jun 12, 2026 12:19am

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (1021 entries)...
✗ Lockfile failed supply-chain policy check (1021 entries in 7.4s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 9 lockfile entries failed verification:
  @ai-sdk/react@2.0.201 was published at 2026-06-11T15:56:44.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  @posthog/core@1.32.3 was published at 2026-06-11T08:51:49.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  @posthog/types@1.386.3 was published at 2026-06-11T08:52:24.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  @vercel/functions@3.7.1 was published at 2026-06-11T15:24:29.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  ai@5.0.199 was published at 2026-06-11T15:56:45.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  caniuse-lite@1.0.30001799 was published at 2026-06-11T09:52:10.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  enhanced-resolve@5.24.0 was published at 2026-06-11T14:06:10.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  posthog-js@1.386.4 was published at 2026-06-11T13:35:22.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)
  posthog-node@5.36.17 was published at 2026-06-11T08:52:06.000Z, within the minimumReleaseAge cutoff (2026-06-11T00:13:11.066Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.