v2.6.1

[2.6.1] - 2026-06-30

Fixed

• Confirmation token retry loop — Router schemas now expose confirmation_token as an optional top-level argument, giving MCP clients a valid schema slot for the token returned by confirmation-required responses (#34)
• Confirmation payload drift on retry — Confirmation tokens now preserve the originally confirmed arguments, tolerate associative key reordering, and restore the confirmed payload before executing the gated action while still rejecting changed payloads and reordered lists (#34)

Tests

• Added regression coverage for schema exposure, two-step confirmation retries, nested associative argument reordering, and confirmed payload restoration