feat: require confirmation for state changes

[Saluana]

Summary

• add MCP annotations for all tools, distinguishing read-only/local operations from destructive open-world operations
• require confirm: true for every on-chain transaction, provider-state mutation, certificate revocation/regeneration, and container command execution
• document the confirmation requirement and add MCP discovery coverage

Root cause

State-changing tools had the same presentation as read-only tools and accepted calls without an explicit confirmation field. This made it too easy for an agent to submit a transaction, modify a provider deployment, or execute a command without a deliberate final signal.

Impact

MCP clients can use standard risk annotations to present safer UX. Mutating tools now reject unconfirmed calls at schema validation before any handler or network action runs.

Validation

• npm test — 67 tests passed
• npm exec tsc -- --noEmit — passed
• targeted ESLint — no new errors; repository contains two existing quote-style errors in regenerate-certificate.ts