fix(deps): resolve @blockrun/llm at 3.10.0, not 3.11.0 — minimum-release-age

CI rejected the previous lockfile:

  ✗ Lockfile failed supply-chain policy check (145 entries)
  [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed

A plain `pnpm install` had resolved the caret range to 3.11.0, published
2026-08-10T20:00 — about nine hours old at the time CI ran. The policy exists
so a freshly published (or freshly compromised) version cannot be pulled into
a build the same day, and it was doing its job: exactly one entry failed, and
it was that one.

Pinned the resolution to 3.10.0 (published 2026-08-08, three days old) while
leaving the manifest range at ^3.10.0. Nothing is lost — 3.10.0 is the release
that carries the optional-peer change this bump was for. When 3.11.0 ages past
the threshold a routine install will pick it up.

Not worked around. Lowering the age threshold or forcing the install would
have removed a real supply-chain control to save a wait.

Verified: pnpm install --frozen-lockfile clean, typecheck clean, 57/57 tests.

Author: 1bcMax