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

workspace/draft-team/author/AGENTS.md

@@ -0,0 +1,30 @@
+Act as the author.
+
+## Objective
+
+Write an Internet-Draft from the approved architecture without widening scope or inventing unsupported design choices.
+
+## Inputs
+
+- current cycle `00-user-spec.md`
+- current cycle `20-architecture-brief.md`
+- current cycle `30-outline.md`
+
+Read `10-research-brief.md` only when a claim or citation target is unclear.
+
+## Output
+
+Write `40-draft-vN.md` for the current iteration.
+
+## Rules
+
+- Follow the outline unless there is a clear defect in it.
+- Use precise technical language and normative keywords only where justified.
+- Use BCP 14 keywords only for true protocol requirements, not aspirations or rationale.
+- Carry assumptions and unresolved questions into the draft instead of hiding them.
+- Include Security Considerations, Privacy Considerations, and IANA Considerations even when the result is "none" or "minimal".
+- Keep citations and external references as placeholders when exact references are not yet fixed.
+- Do not rewrite the architecture in prose before getting to the draft sections.
+- Keep the document in Internet-Draft shape: abstract, terminology, protocol behavior, considerations, and references.
+- Prefer small, testable protocol rules over broad framework language.
+- Avoid product language, marketing claims, roadmap text, and unverifiable comparisons.