Build research panel POC fixture endpoint

[yonadavGit]

Description

A brief description of the PR

Code Changes

The following changes were made to the files below

Notes

Any additional notes go here

[gitvelocity-reviewer]

📊 Code Quality Score: 14/100

14 (base) × 1.0 (ESF, Extra Large lines tier) = 14

Category	Score	Factors
🔭 Scope	4/20	One new file added under data/research_panel_poc/. No subsystems, APIs, or application code touched. The diff was truncated so up to 11 additional files may exist but are not visible.
🏗️ Architecture	1/20	No module boundary changed. The file lands in an existing research POC directory with no wiring into application code.
⚙️ Implementation	3/20	The JSON schema encodes a multi-field tagging structure: purposeTags, primaryPurpose, questionsAnswered, normalizedQuestion, topicTags, quality, needsHumanReview, rationale, clusterId, and clusterLabel per item, plus deterministicSnippetEvidence arrays with charRange offsets. The pipeline logic that produced this output is not present in the diff.
⚠️ Risk	3/20	No production code paths are affected. The file permanently adds ~several MB to repository history. Fetched webpage snippets stored in the file raise potential copyright questions, though webpagesWithBodyCount is 0 per the enrichment summary.
✅ Quality	2/15	No tests accompany the file. No generation script is included. No README exists in data/research_panel_poc/. The data itself carries internal quality metadata (needsHumanReview flags, quality ratings of weak/okay/strong) but no external validation tooling.
🔒 Perf / Security	1/5	Webpage body text was intentionally excluded from the fixture per webpagesWithBodyCount: 0. No other performance or security work is present.

Was this score accurate? 👍 Yes · 👎 No

How this was scored →

_{Scored by GitVelocity · How are scores calculated?}