feat: upgrade groq-js to latest version

[kbrabrand]

Description

Upgrade groq-js to latest version (minor bump) to get improvements and bugfixes into groqd.

Type of Change

• New feature (non-breaking change which adds functionality)

It should be backwards compatible, but a dep bump is still more than a bugfix.

How Has This Been Tested?

I've run the automated tests after upgrading groq-js to latest, and they all still pass.

[changeset-bot]

🦋 Changeset detected

Latest commit: 9eb2c84

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
groqd	Minor
website	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@kbrabrand is attempting to deploy a commit to the formidable-labs Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Pull request overview

Updates the workspace to use a newer groq-js version, refreshing the lockfile and recording a release note for groqd.

Changes:

• Bump groq-js from ^1.1.9 to ^1.26.0 in packages/groqd (devDependency).
• Update pnpm-lock.yaml to reflect the new dependency graph/resolutions.
• Add a Changesets entry marking a groqd minor release for the dependency update.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
pnpm-lock.yaml	Regenerates lockfile with groq-js@1.26.0 and related dependency resolution changes.
packages/groqd/package.json	Updates the groq-js version range used by groqd during development/tests.
.changeset/purple-pumas-occur.md	Adds a release note for a groqd minor bump tied to the dependency upgrade.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

groq-js is a devDependency here and (in this repo) appears to be used only under src/tests/** (e.g. src/tests/mocks/executeQuery.ts). If the goal is to ship groq-js improvements/bugfixes to groqd consumers, this change won’t affect runtime installs; consider either (a) clarifying the PR/changeset as a dev/test-only upgrade, or (b) moving groq-js to dependencies/peerDependencies if it’s intended to be part of the public runtime surface.