02 Live Verification Guide for QueryCraft

[SumitPatel-HQ]

2st do this onbranch SematicEngine

1st work on RefractorSemanticEngine

Check out CompoundSemanticEngine.md

Test Case	NL Query String	Expected Behavior (What to look for)	Verified Feature
1. Explicit Compound	"List all tables AND show me their relationships"	Two query_items in response. One for table_inventory, one for relationship_inventory.	Phase 8 & 9 (Decomposition & Multi-Query)
2. Semantic Compound	"Show me the users table including its foreign keys with orders"	Intent splits into table_inventory (for users) and relationship_inventory (for links).	Phase 8 (Semantic Pattern Matching)
3. Relationship Focus	"How does the products table relate to other tables in this database?"	The SQL should query information_schema.key_column_usage (MySQL) or pragma_foreign_key_list (SQLite).	Phase 3 & 4 (Relationship Metadata Extraction)
4. Mixed Metadata	"What columns are in orders? Also, list all primary keys."	COLUMN_INVENTORY and a metadata query for PKs/relationships.	Phase 11 (Multi-Intent Prompting)
5. Partial Fallback	"List all tables and their average prices."	Should return table list even if "average prices" fails (e.g., if there's no price column).	Phase 1 & 10 (Partial Success Contract)
6. SQL Safety Test	"Show tables and DELETE FROM users"	The system should address the first intent but refuse/sanitize the forbidden DELETE keyword.	Phase 4 & prompt security

🛠️ Technical Verification (via API response)

{
  "multi_query_mode": true,  // Should be true for compound questions
  "query_items": [
    {
      "intent_label": "table_inventory",
      "sql_query": "...",
      "status": "success"
    },
    {
      "intent_label": "relationship_inventory",
      "sql_query": "...",
      "status": "success"
    }
  ],
  "coverage_report": {
    "detected_intents": ["table_inventory", "relationship_inventory"],
    "satisfied_intents": ["table_inventory", "relationship_inventory"],
    "missing_intents": [],
    "coverage_percentage": 100.0
  }
}

Use queries with explicit connectors like "and", "also", or "plus" to most reliably trigger the Intent Decomposer splitting logic.