docs: define research hardening roadmap

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -17,6 +17,20 @@ body:
       description: What concrete limitation or workflow gap should be addressed?
     validations:
       required: true
+  - type: dropdown
+    attributes:
+      label: Research area
+      options:
+        - Frida visibility reduction
+        - /proc and process-map consistency
+        - Virtual-environment fidelity
+        - Android or vendor compatibility
+        - Import, integrity, or ABI handling
+        - Controller and developer tooling
+        - Product UI and accessibility
+        - Documentation or validation
+    validations:
+      required: true
   - type: textarea
     attributes:
       label: Proposed boundary

.github/PULL_REQUEST_TEMPLATE.md

@@ -20,11 +20,18 @@ Describe the problem and the narrow change that solves it.
 - [ ] Device validation attached when runtime behavior changed
 - [ ] Original guest APK remains unmodified
 - [ ] No credentials, private agents, proprietary APKs, or sensitive logs included
+- [ ] I understand and can explain every submitted change, including AI-assisted code
 
 ## Evidence
 
 List exact commands, Android/device details, and sanitized output.
 
+## Research assistance
+
+If Codex, Claude, or another assistant materially contributed, identify the
+tool, the scoped task it helped with, and the manual review/device validation
+you performed. Never include prompts or transcripts containing sensitive data.
+
 ## Risks and limitations
 
 Describe compatibility impact, process-lifecycle assumptions, and remaining gaps.