[Blind-Striker]

The README test badge was stale. It showed 1168 passed, from 2025-07-25: the Gist-based badge action has been getting HTTP 401 since then (expired GIST_SECRET), and continue-on-error hid the failure. The README also still used the archived localstack-nuget-badge-lambda endpoint instead of BadgeSmith.

This PR

• CI posts each build-and-test leg's counts to BadgeSmith (api.localstackfor.net), on pushes to master only, using BadgeSmith's own update-test-badge action. As in opencode-sdk-dotnet, the action is checked out at the commit the live deployment runs (bc7ed07) and used by local path. It is signed with the organization secret TESTDATASECRET, which this repository can already read. BadgeSmith's badge-smith-github-org-secrets table already maps localstack-dotnet to a testdata key, and the Aspire integration posts with it.
• Removed the Gist action (.github/actions/update-test-badge), BADGE_GIST_ID and the per-OS file names.
• All three README copies (still byte-identical) take the package and test badges from BadgeSmith. The test badge links to BadgeSmith's test-result redirect.
• quality-gates.md now describes the BadgeSmith post instead of the Gist.

Verification

• The new package badges render 3.0.0 through shields.io.
• The test badge shows "no results" until the first master push after merge posts results. Before this PR, BadgeSmith returned 404 for this repository.
• GIST_SECRET and the Gist itself can be retired after merge.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None