lsm / neokai / 28591939071

82%

Build Type

push

github

Committed by web-flow

Commit Message

docs: rebrand user-facing strings and docs to HyperNeo (#2220)

* docs: rebrand user-facing strings and docs from NeoKai to HyperNeo

Third PR of the NeoKai -> HyperNeo rebrand. Replaces the standalone
product name NeoKai with HyperNeo across user-facing surfaces only:

- CLI banner, --help text, and startup messages
- Web UI labels (About section, page title, modals) and HTML title
- HTTP User-Agent strings and ACP client name
- All markdown docs (README, CONTRIBUTING, CHANGELOG, CLAUDE.md, QA.md,
  docs/**) including design docs, reports, plans, and architecture docs
- Source comments describing the product and prompt/seed-data strings
- Test fixtures and assertions referencing the product name

Deliberately unchanged (handled by other PRs in the series):
- Code identifiers, e.g. shouldUseNeoKaiCompactFallback, NeokaiActionMessage
- Package scopes (@neokai/*) and the npm package/binary name
- Env vars (NEOKAI_*) and file paths (~/.neokai, /tmp/neokai-)
- GitHub repo URLs (github.com/lsm/neokai)
- Dotted identifier keys (neokai.provider.github, neokai.output-mode.compressed)

Also fixes one markdown anchor link that pointed at a rebranded heading.

* fix(rebrand): correct derived values, data-matching lookups, and benchmark data

Addresses review feedback on the NeoKai -> HyperNeo rebrand where the
PascalCase-only swap left lowercase derived/matching values stale:

- slug assertions (slug.test, space-slug.test): expected slug must follow
  the rebranded input, so neokai-dev -> hyperneo-dev.
- topic-trie case-insensitive test: the pattern segment must stay NeoKai,
  the mixed-case counterpart of the lowercase repo name 'neokai' in the
  lookup topic (the test verifies case-insensitivity, not the product name).
- migration 142 Forge evidence lookup: keep 'Build and harden NeoKai Forge'
  unchanged — this matches scope rows that already exist in user databases,
  so rebranding it would silently skip the evidence backfill on upgrade.
- benchmark results ... (continued)

Coverage Stats

11522 of 16599 branches covered (69.41%)

Branch coverage included in aggregate %.

14 of 19 new or added lines in 14 files covered. (73.68%)

15 existing lines in 2 files now uncovered.

98002 of 116290 relevant lines covered (84.27%)

301.35 hits per line