chore(maintenance): simplify deepsec setup

[chaliy]

What

• Pin DeepSec to 2.1.2 and remove the tracked pnpm lockfile for the scanner workspace.
• Ignore regenerated DeepSec lockfiles while keeping DeepSec config/context tracked.
• Refresh the site performance timeline from existing benchmark result artifacts.

Why

• DeepSec is a maintenance scanner, not shipped runtime code, and its lockfile churn adds noisy dependency tracking.
• Site data should include all checked-in benchmark results.

Verification

• just pre-pr
• cargo deny check
• npx pnpm@10.11.1 --dir site run build
• cd .deepsec && npx deepsec@2.1.2 --version
• pnpm deepsec scan --project-id bashkit passed during maintenance; process remains blocked by DeepSec's bundled Codex binary ENOENT/SIGKILL on this machine.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	bashkit	7b00c00	Commit Preview URL Branch Preview URL	Jul 04 2026, 10:33 PM