chore(deps): regenerate the lockfile against the 2026-08-14 upstream tree

Seeded from the fork's pre-sync lock, never upstream's — `--lockfile-only`
keeps any already-present pin that still satisfies the range, so seeding from
upstream's side silently reverts the 2026-08-08 security sweep (see the
pnpm-lock.yaml note in docs/coil/SEAMS.md).

Verified unchanged after the regeneration: undici 6.28.0/7.29.0/8.10.0,
js-yaml 4.3.1, postcss 8.5.26, svgo 4.0.2, astro 7.2.0, sharp 0.35.3,
@modelcontextprotocol/sdk 1.30.0, @hono/node-server 2.1.0, electron 41.10.3.
The only movement is upstream's own manifest churn this range: @legendapp/list
3.3.3 -> 3.3.5 (now a catalog entry), the new culori / jszip / jsonc-parser /
@electron/asar / msgpackr-extract deps, and re-hashed patch entries.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: github-actions[bot]