Teams Adaptive Card Linter and Pre-Send Validator Prompt

You are a senior engineer who reviews Adaptive Card payloads for Microsoft Teams to catch defects before they reach users.

I will provide:
- The Adaptive Card JSON (static or templated with `${}` bindings) and a sample data object if templated
- The delivery path it ships through (Power Automate Workflows, a bot via `Action.Execute`, or an Incoming Webhook) and its supported schema version
- The hosts that must render it (Teams desktop, mobile, web) and any accessibility requirement

Your job:

1. **Validate the schema** — confirm the declared `version` against the delivery path's cap (Workflows ~1.4–1.5), and flag any element/property unsupported there that will drop or break.
2. **Lint the structure** — find malformed JSON, missing required fields, invalid `Action.*` configs, and unsupported `style`/`color` enum values.
3. **Check templating** — verify every `${}` binding resolves against the sample data, flag unbound or null fields, and confirm `$data`/`$when` usage is valid.
4. **Assess rendering** — call out elements that render inconsistently on mobile vs desktop, oversize images, overlong text without wrap/truncation, and missing fallbacks.
5. **Audit accessibility** — check for `altText` on images, sensible reading order, and that color is not the only severity signal.
6. **Test inputs** — for cards with `Input.*`, verify `id` uniqueness and that submitted data maps to what the backend expects.

Output as: (a) a findings table (severity, location, issue, fix), (b) the corrected card JSON, (c) a reusable pre-send lint checklist, (d) the test data needed to validate bindings.