Add structured GitHub issue forms

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,104 @@
+name: Bug report
+description: Report a reproducible defect in Needle's current public source.
+title: "[Bug]: "
+labels:
+  - bug
+assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a problem. Needle is a pre-alpha project, so first
+        check the current limitations in `PROJECT_STATUS.md`.
+
+        Do not include credentials, private repository content, provider tokens,
+        sealed benchmark material, or vulnerability details. Follow `SECURITY.md`
+        for security reports.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: Describe the defect and its user-visible impact.
+      placeholder: A concise description of what is broken and why it matters.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction
+      description: Provide the smallest deterministic sequence that reproduces the problem.
+      placeholder: |
+        1. Start from...
+        2. Run...
+        3. Observe...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+      description: Explain what should have happened instead.
+    validations:
+      required: true
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: Include only relevant, non-sensitive version and platform information.
+      placeholder: |
+        Needle commit or version:
+        Operating system and architecture:
+        Rust version:
+        Codex version, if relevant:
+        Node.js version, if relevant:
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Affected area
+      description: Select every area that appears relevant.
+      multiple: true
+      options:
+        - Routing, proof, or semantic reuse
+        - Runtime, persistence, or lifecycle
+        - Codex adapter or worker execution
+        - Verified changes, patching, or verification
+        - Web control plane
+        - Benchmarks or evidence
+        - Packaging, compatibility, or CI
+        - Documentation
+        - Unknown
+    validations:
+      required: true
+
+  - type: textarea
+    id: diagnostics
+    attributes:
+      label: Diagnostics
+      description: Add bounded logs, error messages, or failing test names after removing sensitive data.
+      placeholder: Paste only the smallest relevant excerpt. Do not attach complete private logs.
+
+  - type: textarea
+    id: additional_context
+    attributes:
+      label: Additional context
+      description: Add links to related issues, regressions, or other useful evidence.
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Submission checks
+      options:
+        - label: I checked `PROJECT_STATUS.md` and this is not a documented unsupported behavior.
+          required: true
+        - label: I searched existing issues for the same problem.
+          required: true
+        - label: This report contains no credentials, private source, sealed benchmark data, or vulnerability details.
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,9 @@
+blank_issues_enabled: true
+
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/IASolutionOrg/Needle/security/policy
+    about: Do not disclose vulnerability details publicly. Follow the private-reporting instructions in the security policy.
+  - name: Project status and roadmap
+    url: https://github.com/IASolutionOrg/Needle/blob/main/PROJECT_STATUS.md
+    about: Check current capabilities, evidence levels, limitations, and release-readiness gates before opening an issue.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,103 @@
+name: Feature request
+description: Propose a focused capability or improvement for Needle.
+title: "[Feature]: "
+labels:
+  - enhancement
+assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Before proposing a substantial change, review `PROJECT_STATUS.md`,
+        `docs/ROADMAP.md`, and `CONTRIBUTING.md`. Configuration support for an
+        agent host does not imply execution or orchestration support.
+
+        Describe the problem and observable outcome. A complete implementation
+        design is welcome but not required.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What concrete limitation or user need should Needle address?
+      placeholder: Explain the current limitation without assuming a specific implementation.
+    validations:
+      required: true
+
+  - type: textarea
+    id: outcome
+    attributes:
+      label: Expected outcome
+      description: Describe the observable behavior that would make this request complete.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Product area
+      multiple: true
+      options:
+        - Role profiles or agents
+        - Runtime or lifecycle orchestration
+        - Routing, proof, or semantic reuse
+        - Codex adapter or worker execution
+        - Other-host configuration
+        - Verified changes
+        - Web control plane
+        - Benchmarks or evidence
+        - Packaging or compatibility
+        - Security
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed_scope
+    attributes:
+      label: Proposed scope
+      description: If you have an approach in mind, describe the smallest complete slice and its boundaries.
+      placeholder: Include important constraints, invariants, or non-goals when known.
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Describe existing workflows or simpler alternatives you considered.
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: Compatibility, safety, and performance impact
+      description: Note any expected effect on schemas, storage, cache identity, execution authority, security boundaries, latency, memory, or packaging.
+      placeholder: Write "No known impact" when none is currently known.
+    validations:
+      required: true
+
+  - type: textarea
+    id: validation
+    attributes:
+      label: Acceptance evidence
+      description: What tests, fixtures, benchmarks, or live evidence would demonstrate completion?
+
+  - type: textarea
+    id: additional_context
+    attributes:
+      label: Additional context
+      description: Link related issues, documentation, examples, or prior art.
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Submission checks
+      options:
+        - label: I checked `PROJECT_STATUS.md` and `docs/ROADMAP.md` for the current boundary.
+          required: true
+        - label: I searched existing issues for the same request.
+          required: true
+        - label: I understand that an accepted request is not a release, support, performance, or provider-backed evidence claim.
+          required: true
+        - label: This request contains no credentials, private source, sealed benchmark material, or vulnerability details.
+          required: true