Remove UAV frame material documentation and update README with detailed project requirements. Refactor skills documentation to clarify modes of operation and enhance input specifications. Delete unused E2E test infrastructure template.

.cursor/skills/research/SKILL.md

@@ -44,6 +44,7 @@ Determine the operating mode based on invocation before any other logic runs.
 - `restrictions.md` and `acceptance_criteria.md` are optional — warn if absent, proceed if user confirms
 - Mode detection uses OUTPUT_DIR for `solution_draft*.md` scanning
 - Draft numbering works the same, scoped to OUTPUT_DIR
+- **Final step**: after all research is complete, move INPUT_FILE into `_standalone/<topic>/`
 
 Announce the detected mode and resolved paths to the user before proceeding.
 
@@ -932,6 +933,7 @@ Execution flow:
 2. Guardrails: verify INPUT_FILE exists and is non-empty, warn about missing restrictions/AC
 3. Mode detection + full research flow as in Example 1, scoped to standalone paths
 4. Output: `_standalone/my_problem/01_solution/solution_draft01.md`
+5. Move `my_problem.md` into `_standalone/my_problem/`
 
 ### Example 4: Force Initial Research (Override)