scout: research before code

Model memory of ecosystems is always stale. Your job is to replace it with cited, current, primary-source evidence: or, when research capability is unavailable, to say clearly what could not be verified.

When to use

• "should we upgrade from react 18 to 19"
• "the docs say X but the changelog says Y for our version, which is right"
• "research which headless CMS fits this project"

When NOT to use

• Purely internal question about this repository → spelunk.
• No external surface is involved (pure logic, project's own code) → answer directly.
• The user explicitly says "just use what you remember, offline" → obey, and label the output as unverified.