docs: rebuild the public repository front door

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Help us reproduce a CLI problem
+title: "[Bug] "
+labels: bug
+assignees: ""
+---
+
+<!-- For vulnerabilities or suspected credential exposure, stop here and use SECURITY.md. Never paste tokens, private code, or account identifiers. -->
+
+## What happened
+
+Describe the behavior and what you expected instead.
+
+## Reproduction
+
+1. List the smallest sequence of commands or actions that triggers the problem.
+2. Include a minimal public repository or sample when possible.
+3. Say whether it reproduces consistently.
+
+## Environment
+
+- Aether Agent version (`aether --version`):
+- Install path (npm or source):
+- OS and terminal:
+- Node.js version (`node --version`):
+- Model route (hosted or Ollama; no credentials or account IDs):
+
+## Evidence
+
+Paste the relevant error, sanitized logs, and verification command/output. If the
+working tree changed, summarize the affected paths.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/AetherAI3/aether-agent/security/policy
+    about: Report vulnerabilities privately; do not open a public issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Propose a focused improvement to Aether Agent
+title: "[Feature] "
+labels: enhancement
+assignees: ""
+---
+
+## Problem
+
+What workflow is difficult or impossible today? Include a concrete example.
+
+## Proposed outcome
+
+Describe the result you want, not just a command name or implementation.
+
+## Constraints and alternatives
+
+Note any security, local-authority, compatibility, or offline requirements, plus
+workarounds you already tried.

.github/pull_request_template.md

@@ -0,0 +1,20 @@
+## Why
+
+What problem does this pull request solve?
+
+## What changed
+
+Summarize the focused change and call out any user-visible behavior.
+
+## Verification
+
+- [ ] Relevant tests and checks pass, or the reason they were not run is below.
+- [ ] Public commands, examples, and generated docs were checked when applicable.
+
+Evidence or commands:
+
+## Scope and risk
+
+- Security or local-authority impact:
+- Compatibility or release impact:
+- Follow-up work intentionally left out: