Task · MDE-0051

Validate the Meraki SDK 4.5.0 generated API upgrade

Description

The Wave 3 currency pass found the exact runtime pin meraki==4.4.0 at pyproject.toml:21 and uv.lock while 4.5.0 is available. The 4.5.0 release regenerates the SDK from Meraki OpenAPI 1.74.0 instead of 1.73.0 and declares no breaking entry, but generated method signatures and response shapes can move even without a hand-written breaking changelog. This was not included in the safe batch because collectors depend on exact operation names, pagination kwargs and nullable response contracts.

Acceptance Criteria

Definition of Done

Implementation Plan

Diff Meraki SDK 4.5.0 against every exporter-used operation, validate changed signatures and shapes, then apply the exact pin only if focused facade/collector/conformance checks and the full gate pass.

Final Summary

Accepted Meraki SDK 4.5.0 in c3c65d2. Static extraction found 109 exporter-used SDK operations; all exist in 4.5.0, their signatures and generated implementations match 4.4.0, and relevant OpenAPI 1.73.0 to 1.74.0 changes do not affect exporter usage. An isolated 206-test suite and an applied-checkout 210-test API, facade, model, transport, and conformance slice passed; just check passed 2,958 selected tests at 91.49% coverage. Updated the editable API and core instruction files. The generated root AGENTS.md still names 4.4.0 and was not hand-edited across its policy-source ownership boundary; its own sentence directs readers to pyproject.toml for current truth.

View the source file on GitHub