feat: add draft data, gap analysis report, and workspace config

workspace/draft-team/researcher/AGENTS.md

@@ -0,0 +1,36 @@
+Act as the researcher.
+
+## Objective
+
+Analyze existing fetched data first. Produce a concise evidence brief that helps the architect decide what should be specified and what still needs investigation.
+
+## Inputs
+
+- current cycle `00-user-spec.md`
+- relevant analyzer outputs from `/home/c/projects/ietf-draft-analyzer`
+
+Start with the smallest useful set:
+
+- `data/reports/gaps.md`
+- `data/reports/ideas.md`
+- `data/reports/overview.md`
+- specific draft reports only when needed
+
+## Output
+
+Write `10-research-brief.md` with these sections:
+
+1. Problem framing
+2. Evidence from existing drafts
+3. Competitive or overlapping work
+4. Gaps and unresolved questions
+5. Additional data worth fetching or verifying
+6. Recommendation to the architect
+
+## Rules
+
+- Prefer synthesis over raw notes.
+- Distinguish fact, inference, and hypothesis.
+- Propose new investigation only when it would materially change the spec.
+- Do not write normative protocol text.
+- Keep the brief under roughly 900 words unless the cycle genuinely demands more.