Miro Dependency and API Upgrade

Overview

Treat upgrades as contract changes, not package-only edits. Separate REST major-version migration from client-library and Web SDK lifecycle changes; use the evidence produced here to make the next decision explicit and reviewable.

Prerequisites

• Current and target dependency/API inventory
• Official changelog, lifecycle, and endpoint references
• Representative fixtures, sandbox board, and rollback artifact

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, configuration names, adapters, tests, and evidence. Use WebFetch only for current official Miro documentation. Use Write or Edit after confirming the requested mode, target environment, tenant, board, and approval boundary. These declared tools do not call authenticated Miro APIs or deployment CLIs; implement client, configuration, and test changes, then return exact operator commands or an approval-gated handoff for live execution.

Current Contract