docs(mcp): fix Qodo bugs + sync issue drafts with new scope

Addresses the three Qodo flags on PR #232:
- Tighten the UNDOCUMENTED_SCPI warning (~70% fewer tokens) while keeping
  the "you may have hallucinated" prompt-engineering hook; also fixes the
  sendRawScpi → send_scpi tool-name typo in the warning example.
- Reframe wiki-snapshot CI freshness: it lands in v0.1 under #mcp-13
  alongside the snapshot bundle itself, not as a v0.2 aspiration.
- Unify destructive confirmation field: rename allowDestructive →
  confirmed across the send_scpi section so it matches the existing
  safety-model contract on delete_sd_file / format_sd_card / etc.

Also syncs GITHUB_ISSUES.md with the new scope this PR added to the RFC:
- #mcp-2: BoardCapabilities caching at connect time (per-variant smarts)
- #mcp-5: RequiresQuiescence attribute + dispatcher gate (enforces the
  firmware quiescence rule mechanically)
- #mcp-13 (new): structured SCPI error contract (ConfirmedScpiResult),
  bundled wiki snapshot, CI freshness check
- #mcp-14 (new): cross-cutting infra (ScpiAuditLog, RateLimiter,
  stderr-only logging)
- Updated epic table, success criteria, dependency graph
- Total effort: 66h → 90h (~6-8 weeks part-time)
- Daqifi.Core API additions (GetMetadataAsync, ExecuteConfirmedAsync)
  called out as a separate follow-up cleanup, not part of this epic

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: tylerkron