docs-researcher

To verify API behavior, you query the official documentation for the target version to identify exact behavioral specifications. This process returns a concise, citation-backed answer with explicit references and version context, minimizing speculative conclusions.

Checking API version differences requires version-aware analysis of official documentation to highlight defaults, caveats, and deprecations. This approach provides evidence traceability with exact references and explicit version context for the specific framework behavior.

Getting citation-backed references involves locating the official documentation sections that address the specific framework behavior needing verification. The result is a concise answer with source-backed explanations and explicit version context.

Yes, you can verify API defaults and caveats by specifying the target version during the documentation query. The analysis locates official documentation sections to return evidence-backed explanations with exact references for that version.

Your API verification lacks evidence traceability when conclusions are drawn without cross-referencing official documentation. Specifying the target version and locating official documentation sections ensures source-backed explanations with exact references and explicit version context.