ami-data-validatorlisted

# Skill: Push Data Validator When invoked, act as a Data Architect to ensure any structural changes in code don't break existing data definitions. ## Workflow 1. **Identify Data Definitions:** - Scan the codebase (using grep or file searches) to identify where data definitions exist (e.g., ORM models, raw SQL queries, database connection configurations, schema files). - Search for any related documentation (e.g., `docs/` or `.md` files) to understand the data model and its intended usage. 2. **Cross-Check with PR Changes:** - **Review Diffs:** Analyze the diffs of the current PR to identify any modifications to data definitions (e.g., database schemas, ORM models, core API payloads). - **Validate Consistency:** For any modified data definition, ensure that **all related queries, connections, and usages** structurally match the new changes. - **Verify Deprecations:** Explicitly confirm that no columns or fields were dropped/renamed without corresponding updates in all associated queries. - **Temporal Data Flow & Compatibility:** - **In-Flight & Cached Data:** When modifying or dropping schema fields, verify backward/forward compatibility with serialized data in transit (message queues, cached payloads, or persistent records). - **Boundary Enforced Gating:** Ensure data modifications do not rely on 'de-facto gating' (e.g., assuming callers already send valid payload shapes). Enforce strict validation at model/API entry boundaries. - **Two-Ph