v1.3.1 — Conditional project discovery prompts

What changed

Bug fix: anti-hallucination prompts now adapt to scanner results

When the project scanner finds no page objects or utilities (e.g., your naming conventions don't match the default patterns), the LLM prompts no longer include "do NOT invent page objects" with an empty list. Previously, this confused the model into creating POM classes inline inside test specs.

Now the prompts adapt:

• Artifacts found → "MUST reuse existing page objects listed above. Do NOT invent new ones."
• Nothing found → Neutral best-practice guidance (use accessible selectors, data-testid, etc.)

Documentation: Project Structure Discovery

The README now documents:

• What the scanner discovers (page objects, utilities, test coverage)
• Default auto-detection patterns and how to override them
• Configuration reference for pom_patterns, utility_patterns, and project_context_budget
• Diagnostic tip: check Action logs for Discovered: X page objects... to verify detection

If you're seeing missing POMs or incorrect imports

Add these inputs to your workflow:

- uses: autospec-ai/action@v1
  with:
    test_directory: 'e2e/tests'                        # where your tests live
    pom_patterns: '**/*.po.ts,**/pageobjects/**/*.ts'  # match YOUR naming convention
    utility_patterns: '**/helpers/**/*.ts'

Check the Action logs for Discovered: X page objects, Y utility files — if the counts are 0, your patterns don't match the defaults.