v2.2.5: Batch Queue Safety Guards & Automatic Backup Snapshots

What's Changed in v2.2.5

🛡️ Batch Queue Safety Protections (gsc index-batch clear)

Flagged on Reddit r/ruby by community member @kantorcodes1:
gsc index-batch clear previously cleared the entire pending batch queue immediately with zero confirmation. In an autonomous AI agent, cron job, or pipeline script, an accidental clear could permanently drop hundreds of queued URLs waiting to be indexed.

• Interactive Confirmation (TTY): Prompts with Are you sure you want to clear N pending URLs from the batch queue? [y/N]: before purging. Defaults to abort unless explicitly confirmed.
• Script / Agent Protection: In non-interactive environments (pipes, subshells, CI/CD, AI agents), gsc index-batch clear halts safely with exit code 1 unless --force (or -f, -y, --yes) is explicitly provided.
• Automatic Safety Backup Snapshot: Before records are dropped, an automatic timestamped JSON snapshot is saved to ~/.gsc/backups/queue_backup_<TIMESTAMP>.json, ensuring queued URLs can always be reconstructed.
• Enhanced CLI & Docs: Added clear safety guard explanations in gsc index-batch terminal status and README.

📦 Binary Assets

• Standalone Binary: dist/gsc (1,381 KB) — Zero dependencies, standalone executable.
• RubyGem: gsc-cli-2.2.5.gem — Published to RubyGems.org.