docs: add VerifierAgent pattern for output verification

[mohansesetti29]

Problem

LLM agents may generate hallucinated or incorrect outputs, and CrewAI currently does not
document a standard verification pattern.

Solution

This PR introduces a VerifierAgent pattern under docs/examples/verification, demonstrating
how to validate agent outputs using a secondary verification agent.

What’s Included

• Documentation describing the VerifierAgent pattern
• A runnable example using the public CrewAI API

Scope

Docs-first contribution. No core framework changes.

---

Note

Introduces a docs-first example of separating generation from verification using a dedicated VerifierAgent.

• Adds docs/examples/verification/verifier_agent_crew.md outlining the pattern, architecture, sample JSON verdict, usage, and limitations
• Adds docs/examples/verification/verifier_agent_crew.py defining a generator and verifier Agent, sequential Tasks, and producing a JSON verification report
• No core/framework code changes

^{Written by Cursor Bugbot for commit d6ed1e6. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Removed .env from .gitignore exposing API keys

The .gitignore file has been completely replaced with a minimal template that removes the .env entry. The project documentation explicitly states that .env files store sensitive API keys like OPENAI_API_KEY and should "never commit API keys to version control." Removing this protection means .env files containing secrets could accidentally be committed to the repository. Additionally, many other important entries like .pytest_cache, .mypy_cache, .ruff_cache, .idea, .vscode, *.pkl, database files, and chromadb-*.lock were also removed. This change appears unintentional for a "docs-first" PR.

 

[mohansesetti29]

Thanks for the review!
Restored the original .gitignore to avoid any unintended changes outside the docs scope.