Integration test: rule evaluation against Supabase data

Supabase RLS policies on the test instance must allow the test service role key to insert and delete rows in scenario_rules and scenario_prompt_history. If the test project uses the anon key, ensure RLS policies are relaxed for the test tables or use the service role key exclusively for seeding/teardown. Use unique test-run prefixes (e.g., UUID-based chapter_id) to prevent parallel CI runs from interfering with each other. Cooldown window testing requires inserting scenario_prompt_history rows with specific created_at timestamps — use Supabase's ability to insert with explicit timestamp values.

Define a helper function seedRules(List

Integration tests using flutter_test connecting to a real Supabase test project. Place tests in test/integration/scenario_rule_engine_integration_test.dart. Use setUpAll() to initialize Supabase.initialize() once with env-var credentials. Use setUp()/tearDown() for per-test data seeding and cleanup.

Test scenarios must include: (1) single matching rule returns correct result; (2) multiple rules, highest priority wins; (3) cooldown active blocks best match, lower-priority non-blocked rule selected instead; (4) cooldown active, no alternative rule → COOLDOWN_ACTIVE reason code; (5) no rules for chapter → NO_MATCHING_RULE; (6) rules exist but all inactive → RULE_INACTIVE; (7) trigger_conditions partially met → NO_MATCHING_RULE with correct partial-match metadata. Run integration tests separately from unit tests via a dedicated test command (e.g., flutter test test/integration/).