When a PR changes only test files (selectors, spec files, framework
utilities), the AI analyzer was returning no tags — causing no E2E tests
to run. This fixes the gap with a mix of deterministic hard rules and
improved AI tooling.

Hard rules added:
- test-framework-infra-change: core Detox primitives (Assertions,
  Gestures, Matchers, Utilities, EncapsulatedElement, fixtures/,
  config/) → run all tests
- test-spec-tag-extraction: smoke/regression spec files changed with no
  app code changes → extract tags directly from the spec's import line
  and run only those (targeted, no AI needed)

Existing hard rules updated to return SelectTagsAnalysis directly so
targeted rules can also return partial results.

AI improvements:
- findImporters now searches tests/ in addition to app/, so the AI can
  find which spec files import a changed selector or flow file
- System prompt clarified: tests/selectors/, tests/flows/,
  tests/locators/, tests/page-objects/ changes DO require Detox tags;
  only wdio/ and tests/performance/ are exempt

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…ctors/locators

Non-deterministic AI results for shared test infra changes (e.g. wallet.flow.ts)
led to inconsistent tag selection across runs and missed regressions like #30950.

Adds a new hard rule `test-shared-infra-impact` that runs before AI and produces
the same result every time:

1. Detect changed files in tests/flows/, tests/page-objects/, tests/selectors/,
   tests/locators/ (when no app code also changed)
2. Grep for the changed filename in tests/smoke/ and tests/regression/ to find
   direct spec importers
3. Resolve one level of indirection for intermediate utility files that are not
   specs themselves
4. Extract tags from all affected spec files and return them

Uses execFileSync with an argument array (no shell interpolation) and -F
fixed-string matching — no regex injection risk.

For PR #30917: finds 150 affected specs and selects 13 tags deterministically,
which would have caught the syntax error regression introduced by the barrel
import that caused #30950.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…oning output

Hard rules are deterministic and need no AI provider. Previously, all provider
availability checks (Anthropic, OpenAI, Gemini) ran before hard rules were
evaluated — wasting time and producing noisy warnings in CI.

Fix: evaluate hard rules in index.ts immediately after collecting changed files,
before any provider check. If a rule fires, output and return with no API calls.

Also tighten the reasoning string for test-shared-infra-impact: previously it
embedded all 150+ affected spec file paths, making CI logs unreadable. Now
reports a concise count instead, with the full spec list still visible in
the structured console logs above.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- Bug 1: extend extractTagsFromSpecFile regex to match tags.js imports
  with explicit .js extension (\/tags(?:\.js)?['"])
- Bug 3: extend findSpecFilesImporting step 1 to also grep in
  tests/page-objects/, tests/flows/, tests/selectors/, tests/locators/
  so selector → page-object → spec chains are resolved correctly
- Bug 4: test-shared-infra-impact returns null (not empty result) when
  no tags found, allowing test-spec-tag-extraction to run next
- Bug 5: test-shared-infra-impact now unions tags from directly-changed
  spec files alongside transitively-affected spec files

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…alse positives

Grepping for a bare stem (e.g. 'index', 'utils') matches anywhere in file
content — comments, variable names, strings — pulling in unrelated spec files.
Prefix the search pattern with '/' so it only matches import paths like
from './TokenSelectors' or from '../../selectors/TokenSelectors'.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>