[chore]: update lockfile

[seanmcguire12]

why

• recent lockfile change was left out of a previous commit

what changed

• ran pnpm i & added the lockfile

---

Summary by cubic

Regenerated pnpm-lock.yaml that was missed in a prior commit to align with current workspace dependencies. This removes stale entries and ensures reproducible installs in CI and local dev.

^{Written for commit c0e79fe. Summary will update on new commits. Review in cubic}

[changeset-bot]

⚠️ No Changeset found

Latest commit: c0e79fe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

Architecture diagram

sequenceDiagram
    participant Dev as Developer Machine
    participant CI as CI Pipeline
    participant Repo as Repository
    participant Pkg as Package Registry

    Note over Dev,Pkg: Lockfile Regeneration Flow

    Dev->>Dev: Run pnpm install
    Dev->>Pkg: Fetch dependency metadata
    Pkg-->>Dev: Resolved versions & integrity hashes
    Dev->>Dev: Generate pnpm-lock.yaml
    Dev->>Repo: Commit updated lockfile

    CI->>Repo: Checkout code
    Repo-->>CI: pnpm-lock.yaml
    CI->>Pkg: Verify dependencies match lockfile
    Pkg-->>CI: Integrity confirmed
    CI->>CI: Install dependencies from lockfile

    alt Lockfile out of sync
        CI->>CI: Fail with lockfile mismatch error
    else Lockfile in sync
        CI->>CI: Proceed with build & tests
    end

Loading

_{Re-trigger cubic}