Update to SQL Copilot

{
  "description": "Create reproducible SQL test fixtures, expected outputs and cross-engine equivalence checks.",
  "included_files": [],
  "name": "test-sql-logic",
  "skill_md_contents": "---\nname: test-sql-logic\ndescription: Create reproducible SQL test fixtures, expected outputs and cross-engine equivalence checks.\n---\n\n# Test Sql Logic\n\n**Trigger:** Create reproducible SQL test fixtures, expected outputs and cross-engine equivalence checks.\n\n## Workflow\n1. Identify query invariants and edge cases: missing keys, duplicates, NULL, zero rows, dates at boundaries, ties, skew and unexpected cardinality.\n2. Construct minimal sample rows with expected answers; use the target dialect when possible.\n3. Distinguish unit fixture tests from production-data verification and version-dependent optimizer checks.\n4. Run tests only if a SQL execution tool is available; otherwise give copyable setup/assertion SQL and mark unexecuted.\n5. Explain how to compare totals, unique keys, exact rows and numerical tolerance for precision differences.\n\n## Critical standard\nSQLite fixture results do not prove validity on Snowflake, BigQuery, Databricks or SQL Server.\n\n## Evidence and execution\nOnly say \"executed\", \"passed\", \"observed\", \"optimized\" or \"deployed\" when a connected tool returned evidence for that claim. An SQL draft, a textual review, or local fixture proof alone is not production validation. Never ask the user to paste passwords or raw confidential records.\n\n## Supporting references\n- Read `../../references/testing-method.md` when relevant.\n- Read `../../references/reconciliation.md` when relevant.\n\n## Return\nFixture DDL/rows, assertions, commands if run and evidence status.\n"
}