devrites-source-drivenlisted

# devrites-source-driven: verify, don't guess When library behavior matters and is uncertain, verify it against installed source or authoritative documentation before relying on it. ## When to trigger - You're about to rely on an API signature, default, config key, or behavior you're not sure of. - The docs in memory might be stale (the project pins a different version). - Tests can't easily prove the assumption, but it drives the implementation. - An error message points at framework behavior you don't fully understand. ## How 1. **Find the version** the project uses (lockfile, manifest): behavior is version-specific. 2. **Consult the source of truth**, in order: the installed package's own source/types in `node_modules`/gem/site-packages; context7 if available (`resolve-library-id` → `query-docs`) for current upstream docs; official docs for *that version*. 3. **Confirm the specific fact:** the signature, the default, the edge behavior, not a general impression. 4. **Return it** with fact, version, and source. The root orchestrator records accepted evidence in `decisions.md` or `evidence.md`; a leaf agent never writes the workspace. ## Delegate broad research When the question is an *area* (a library surface, unfamiliar subsystem, or migration guide), the **root orchestrator** uses the fresh-context dispatch contract in [`agents.md`](../devrites-lib/reference/standards/agents.md) to give one bounded question to `devrites-evidence-scout`. Wait for and va