docs: rebuild the public repository front door

[AetherAI3]

Why

A first-time visitor currently reaches release/version administration before the
install-and-try path, the hero has generic alt text and renders small, and the
package description presents catalogued-but-unavailable Kimi/Gemma entries as
usable. This makes a capable CLI harder to understand and trust than it should be.

What changed

• Reordered the README around one product sentence, a large accessible repo-owned
  hero, minimal badges, the exact three-command quickstart, hosted/Ollama routes,
  differentiators, model truth, core commands, security/local authority, and docs.
• Moved release/source caveats and contributor setup below the first-use path while
  preserving generated catalogue markers and release evidence links.
• Changed only package.json description and keywords; version, scripts,
  dependencies, entrypoints, and runtime fields are untouched.
• Added lightweight bug, feature, security-routing, and pull-request templates.

Repository metadata (applied directly)

Field	Before	After
Description	A coding agent for your terminal that runs fully offline on your own machine via Ollama — or on hosted frontier models when you want them. Open-source, one account with Aether AI.	Open-source terminal coding agent for hosted models or local Ollama, with repository-aware tools, operator-controlled execution, MCP, and verification loops.
Homepage	https://app.aethersystems.net/	https://aethersystems.net/
Topics	autonomous-agent, claude, cli, coding-agent, llm, ollama, terminal, typescript, developer-tools, mcp, ai-agents, ai-coding-assistant, local-agent, local-first, local-llm, offline-ai, offline-first, ollama-cli, terminal-agent, tui	coding-agent, ollama, typescript, developer-tools, mcp, ai-coding-assistant, local-first, local-llm, terminal-agent, code-review, open-source, software-engineering

Social preview recommendation

No preview upload is claimed. GitHub is currently serving its default 1200×600
repository card, including the owner avatar, while the repo-owned hero is 847×418
and is not a native 1280×640 upload.

Operator instruction: from the original brand design, export a 1280×640 PNG that
matches assets/aether-agent-hero.png, keeps the AETHER wordmark inside a centered
1024×512 safe area, contains no personal avatar, then open Settings → General →
Social preview → Edit → Upload image, save it, and read back the rendered preview
dimensions before reporting completion.

Verification

• CLI help from the built 0.3.0 source confirms auth, agent, models, local,
  and mcp; the command manifest and public-doc tests confirm --test-cmd and
  --local.
• npm run docs:check — pass; 6 generated outputs checked.
• Public-doc, release-truth, and release-coherence tests — 40/40 pass.
• npm run verify:production — pass; 673 packed files, 4 workflows.
• npm run release:truth — pass; 12/12, 0 unavailable.
• npm pack --dry-run — pass; version 0.3.0, 673 files.
• README local links/assets — pass; external endpoints respond except npmjs.com
  returns its expected automated-client 403 while the npm registry independently
  confirms latest 0.3.0.
• GitHub render reviewed at 1440×1000 and 390×844: the hero scales correctly, the
  three-command quickstart is exact, and there is no page-level horizontal overflow.
• Issue Publish precondition: README hard-codes pre-publish registry state and will red main after 0.3.0 goes live #112 closed only after current main passed release truth 12/12 and the
  published tarball SHA-1 66021f08d961ddd7b9236ce56afc356a48a45997
  proved the stale 0.1.0/“still resolves” claims are absent.

Scope

No runtime source, installers, generated command docs, CONTRIBUTING.md, versions,
tags, releases, npm publication, Cloud/APR/Supercluster/ATS Web state, or Agent
main changes are included.

[AetherAI3]

Merge Masters handoff: exact head 5ea931b is green against required base e9cbe44. Hosted build, Ubuntu, Windows, supply-chain, CodeQL workflow, and CodeQL analysis all passed; GitHub reports the PR CLEAN. Scope is limited to README.md, package description/keywords, and GitHub issue/PR templates. Repository description/homepage/topics are recorded before/after in the PR body. The only operator-only follow-up is the exact 1280×640 social-preview upload instruction in the PR body. Ready for rollout integration; not merged.