ci: example/go.mod + go.sum drift fails Go Mod Tidy on main

[intel352]

Context

Surfaced while shipping #553 (W-Diagnose-540 diagnostic test). The Go Mod Tidy CI check has been failing on main since at least 2026-05-05; the failure cascades and skips Build / Lint / Test on the main ci.yml workflow.

Recent CI runs on main (all failure):

SHA	Created
3c7bfa66	2026-05-05T10:30
439ee149	2026-05-05T08:19
9810d3c1	2026-05-05T08:19
dd24abcb	2026-05-05T08:19
e2c582be	2026-05-05T01:14

Diagnosis

Running cd example && go mod tidy produces a 29-line diff in example/go.mod and 58 in example/go.sum — drift on indirect AWS-SDK-v2 modules where the recorded versions do not match what go mod tidy resolves transitively (e.g., aws-sdk-go-v2 v1.41.5 recorded vs. v1.41.6 resolved; smithy-go v1.24.3 vs. v1.25.0; etc.).

Requested

Land a small tidy-only PR that runs go mod tidy in example/ and commits the resulting diff. The change is mechanical and unblocks all subsequent PRs against main.

Reference

• Failing job: https://github.com/GoCodeAlone/workflow/actions/runs/25371397452/job/74395535468
• PR test(plugin): diagnostic test for manifest schema strictness (workflow#540) #553 (where this surfaced; merged via admin-override since the failure pre-exists on main and is unrelated to the diagnostic test).