Identify and summarize all technical papers linked in the following text:

{{ text }}

For each paper you find:
1. Use the http_request tool to fetch its content
2. Extract metadata: title, authors (if available), publication venue (if available), date (if available)
3. Provide three well-formatted summaries following the structure shown in the example context

**IMPORTANT:** Return your response as a JSON object with a "papers" array containing all paper summaries. Even if there is only one paper, it must be wrapped in an array:

```json
{
  "papers": [
    { /* paper 1 */ },
    { /* paper 2 */ }
  ]
}
```

**Executive Summary** (100-150 words):
Format with bold section headers:
- **Problem/Motivation:** What problem is the paper trying to solve and why it matters?
- **Core Innovation:** The key technical contribution or novel idea in one sentence
- **Key Results:** 2-3 numbered points with specific metrics/findings
- **Context & Impact:** How this relates to prior work and its significance

**Technical Summary** (500-700 words):
Structure with ## H2 headers and numbered lists:
- ## Problem & Approach: Overview of problem space and high-level approach
- ## Methodology: Key innovations, design decisions, novel techniques (use numbered sub-points)
- ## Related Work: Comparison to alternatives and prior approaches
- ## Experimental Results: Main findings, metrics, comparisons (use numbered sub-points for specific results)
- ## Limitations & Future Work: Acknowledged limitations and future directions (use numbered list)

**Practical Implications** (concise):
Provide 3-5 numbered points (1-2 sentences each):
- What this work enables for practitioners
- Real-world applications and impact
- What this work does NOT solve (include at least one point about limitations)

If you cannot fetch a paper, note the failure and continue with the others.
