docs: clarify HVE Core Extension vs Installer messaging across documentation #964
Description
Issue Description
Documentation conflates the HVE Core Extension (flagship) with the HVE Core Installer (guided setup companion) and makes inaccurate claims about Installer capabilities. Users cannot reliably understand which product to install, what each provides, or when clone-based methods are needed.
Originated from PR #846 review feedback requesting clearer distinction between the Extension and Installer.
Problem
Three products exist with overlapping names and no consistent documentation:
| Product | Purpose | Key capability |
|---|---|---|
| HVE Core Extension | Flagship AI artifact library | All stable agents, prompts, instructions, skills. Zero config. |
| HVE Core Installer | Guided setup companion | Setup method selection, MCP auto-config, agent bundle copying |
| Clone-based methods | Full artifact customization | Direct file access for modifying any artifact |
The docs currently claim the Installer can "select specific collections" and let users "install" collections independently. Neither is true. The Installer copies agents by bundle and auto-configures MCP servers. That distinction is buried or missing across 18 files.
There is also a broken extension ID in docs/hve-guide/lifecycle/setup.md (hve-hve-core-installer instead of hve-installer).
Acceptance criteria
- Every user-facing page uses consistent three-tier messaging: Extension (recommended) → Installer (guided setup + MCP) → Clone (full customization)
- No page claims the Installer can select or install collections (it filters agents only)
- No page claims the Installer can customize prompts, instructions, or skills (agents only)
- MCP auto-configuration is surfaced as the Installer's unique capability where relevant
- Broken extension ID in
setup.mdis fixed - Extension method page (
extension.md) includes the Installer as an intermediate customization step before clone migration - Customization section (
customization/README.md) links customization levels to required installation methods - Method page Quick Start blocks reference both Extension and Installer
- Docusaurus config includes Customization in navbar Topics dropdown and footer
Scope
18 files across 4 priority tiers:
| Priority | Files | Change type |
|---|---|---|
| P0 | docs/hve-guide/lifecycle/setup.md |
Bug fix (broken extension ID) |
| P1 | docs/getting-started/install.md, methods/extension.md, docs/customization/README.md |
Major content corrections |
| P2 | mcp-configuration.md, team-adoption.md, new-contributor.md, 7 method pages, cli-plugins.md |
Cross-reference additions |
| P3 | README.md, docs/README.md, docs/getting-started/README.md, docs/docusaurus/docusaurus.config.js |
Minor additions and nav updates |
Additional Context
No response