Research Web

search("React latest stable version 2025")  →  discover version
fetch("https://react.dev/versions")          →  verify against authoritative source
context_manager add_note("## Research: React version\n- 19.2.0 (March 2025)\n- Source: react.dev")

Turn 1: search("Next.js middleware changes 14 to 15") → collect URLs
Turn 2: fetch(upgrade guide), fetch(changelog)     → parallel fetches
Turn 3: cross-reference, inject structured findings

                   ┌─────────────────┐
                   │ What do I need? │
                   └────────┬────────┘
           ┌────────────────┼────────────────┐
           ▼                ▼                 ▼
     "Discover URLs"   "Read a page"    "Raw API data"
           │                │                 │
     search        fetch           fetch
           │                │
           └────────┬───────┘
                    ▼
            context_manager
              add_note

## Research: [package] version
- Current latest: [version] ([date])
- Previous: [version] (for context)
- Registry source: [npm/pypi/crates.io URL]
- Confirmed via: [source URL]

## Research: [package] [feature] changes
- [Version]: [what changed]
- [Version]: [what changed]
- Breaking: [list of breaks]
- Migration path: [if documented]
- Source: [upgrade guide URL]

## Research: [topic] comparison
- [Tool A]: [key points, version, status]
- [Tool B]: [key points, version, status]
- Recommendation: [with rationale]
- Sources: [URL, URL]

## Research: [topic] — no current changes found
- Searched: [query, query]
- Result: No breaking changes / deprecations / version bumps found
- Checked on: [date]

// Leader: fan out one topic per subagent
batch_tool_use([
  {
    tool: "delegate",
    input: {
      task: "Research current state of Zustand: latest version, breaking changes in 5.x, ecosystem position. Inject findings via context_manager.",
      role: "research"
    }
  },
  {
    tool: "delegate",
    input: {
      task: "Research current state of Jotai: latest version, breaking changes, ecosystem position. Inject findings via context_manager.",
      role: "research"
    }
  },
  {
    tool: "delegate",
    input: {
      task: "Research current state of Valtio: latest version, breaking changes, ecosystem position. Inject findings via context_manager.",
      role: "research"
    }
  },
])

// Leader: one topic, phased research
delegate({
  task: "Research React 19 Server Components: what changed from 18→19, current best practices for 'use client' boundaries, known pitfalls. Cross-reference react.dev docs and the GitHub release notes. Inject structured findings.",
  role: "research"
})

Source A (official docs): React 19.2.0
Source B (npm registry):  19.2.0
Source C (GitHub releases): 19.2.0
→ Cite as confirmed. No need to fetch a 4th source.

Source A (blog post):       Next.js 15.2 deprecated middleware edge runtime
Source B (official docs):   Middleware now defaults to Node.js, edge still available
→ Dig deeper. The blog conflated "default change" with "deprecation".
→ Fetch the actual upgrade guide for the precise language.
→ Flag the disagreement in your findings.

Source A (GitHub issue comment): "This API is being removed in v4"
→ Mark as TENTATIVE. State: "One source claims... cannot confirm."
→ If the claim is critical, search specifically for confirmation.
→ Otherwise, move on — don't spend budget chasing unconfirmed rumors.