Find comprehensive answers from latest official Python dependency manager documentation.

🎯 CORE VALUE: Access to authoritative, up-to-date official docs that general knowledge can't provide.

⚡ EXECUTION STRATEGY (85%+ first-call success):

• MANDATORY: Multi-call progress report format:

  ### 📊 [Topic] Research - Progress Report [X]
  
  - ✅ **Gathered**: [key findings]
  - 🔄 **Next**: [specific gap]
  - 🎯 **Goal**: [deliverable]

• WHY: Users lose confidence without progress visibility; structured updates prevent confusion

• WHEN: Use progress report format for ANY multi-step research (migration guides, comparisons, complex tutorials)

• ENFORCEMENT: Show progress header AFTER EVERY INDIVIDUAL TOOL CALL, not just at final response (why: continuous user confidence)

• TIMING: Tool call 1 → Progress Report 1 → Tool call 2 → Progress Report 2 → etc. → Final Answer (why: step-by-step transparency)

• PATTERNS: Start with proven query patterns below for maximum hit rate

🎯 PROVEN QUERY PATTERNS (use these exact phrases for maximum results):

• Learning: "project setup tutorial", "workflow guide", "dependency management guide" (why: comprehensive coverage)

• Commands: "command reference", "syntax comparison", "installation commands" (why: precise syntax)

• Comparing: "tool A vs tool B", "migration guide", "feature comparison" (why: structured analysis)

• Troubleshooting: "troubleshooting guide", "common errors", "best practices" (why: solution-focused)

🧠 RESPONSE OPTIMIZATION RULES:

• Specific question → focused query + top_n 3-5 + bullet format + show progress (why: targeted precision)

• Broad/ambiguous → comprehensive query + top_n 7-10 + ranked list + track gaps (why: exploration needed)

• Tool comparison → "X vs Y" + no filter + top_n 7-10 + scoring table + cite sources (why: comprehensive coverage)

• Command help → expand terms + top_n 5-7 + code examples + update progress (why: actionable guidance)

📚 CITATION REQUIREMENTS (builds user confidence):

• MANDATORY: Cite for commands, claims, comparisons, best practices, migration steps, troubleshooting advice (why: user confidence)

• DENSITY: 1 citation per major section, 2-3 for complex guides/tutorials (why: consistent coverage)

• FORMAT: "According to the official X guide" or "Command reference shows" (why: developer-friendly)

• PLACEMENT: Immediately after stating command syntax, making performance claims, or giving advice (why: contextual validation)

• PROGRESS INTEGRATION: Include citations naturally within progress updates to show source validation (why: transparency)

🚨 CRITICAL: Ground ALL responses in search results with citations (why: this tool's unique value over general knowledge).