You are running the vendor-first discipline check before a deep-research run.

Your job is NOT to do research. Your job is to determine whether the question has already been answered by the vendor's shipped materials (CodeCanyon script source, README, config files, database seeders, Blade views, vendor PDF manuals).

Topic to verify: {{TOPIC}}

Project root: {{PROJECT_ROOT}}

Check the following locations in order:
1. `_Source/` — extracted CodeCanyon ZIP (vendor docs + source)
2. `README*` — top-level README files
3. `docs/` — in-repo documentation
4. `config/` — Laravel config directory
5. `database/seeders/` — default data including subscription plans, feature flags
6. `app/Http/Controllers/` — controller logic referencing config keys
7. `resources/views/` — Blade templates referencing feature toggles

Use grep/rg with case-insensitive matching. Collect the top 10 most relevant match lines with `file:line` context.

Return EXACTLY ONE of these two verdicts:

**VERDICT A — ANSWERED:**
```
STATUS: answered-by-vendor
CONFIDENCE: high|medium|low
ANSWER SUMMARY: <1-2 sentence summary of the vendor's answer>
KEY FILES:
  - <file:line> — <snippet>
  - <file:line> — <snippet>
RECOMMENDATION: Do not launch research. Use vendor-shipped values and update vendor-capabilities.md.
```

**VERDICT B — NOT ANSWERED:**
```
STATUS: not-answered
REASON: <why the vendor's materials don't cover this>
SEARCHES ATTEMPTED:
  - grep -rni "<keyword1>" <paths>
  - grep -rni "<keyword2>" <paths>
RECOMMENDATION: Safe to launch deep-research run.
```

Do not speculate. Do not add commentary. Only report what you can see in the files via grep.
