feat: map the Systems Manager response members from the 1.74.0 gap report

[danielabbatt]

Rebased onto main on 2026-09-29 (main builds as 1.70.147). Merges as 1.74.8.

Before merging, retarget the base to main. Base branches are not auto-deleted in this repo, so GitHub will not retarget for you, and merging into the old base leaves the work off main (what happened to #413). Merge only after #417 is on main, with a merge commit; do not squash, rebase or click Update branch.

Stacked on #417, in the chain that starts at #415

Base is feat/map-organizations-members. Merge #415, #416 and #417 first (merge commits), then retarget this to main. Changelog label 1.74.8 assumes that order.

What

The second per-area batch from gap-report-v1.74.0.md: 19 Systems Manager members the spec documents that the models lacked.

Model	Added
SmVppAccount	13 fields the API returns beyond id/vppServiceToken, incl. ParsedToken (new SmVppAccountParsedToken: OrgName, HashedToken, ExpiresAt)
SmProfile	PayloadTypes
SmTrustedAccessConfig	TimeboundType

One correction (breaking)

ModifyNetworkSmDevicesTagsAsync was declared as Task<List<SmDevicesCheckinRequest>>, the request type. The API returns [{id, serial, wifiMac, tags}], none of which the request type has, so every device came back as an empty object. It now returns Task<List<SmDevicesModifyTagsResponse>>.

CheckinNetworkSmDevicesAsync and LockNetworkSmDevicesAsync also return the request type, but their {ids} response does bind to it, so they are left alone.

Not in this PR

Seven DeviceLiveTools* members my area filter caught belong to LiveTools/General and will land with that batch.

Verification

dotnet build Meraki.Api.slnx -c Debug   Build succeeded, 0 Error(s), 6 pre-existing CS0618 warnings
Meraki.Api.Test (Data namespace)        Total: 34, Errors: 0, Failed: 0   (4 new in SmMemberTests)
Meraki.Api.Test (Workflows)             Total: 12, Errors: 0, Failed: 0

Edited files kept their BOM state. No code outside Interfaces/Data referenced the changed method.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 6 complexity

Metric	Results
Complexity	6

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[danielabbatt]

Looks good