refactor(navigation)!: delete navigation demo feature

Veect retrofit (ADR-027): fifth and final slice of the demo-content
removal. Deletes packages/navigation whole and prunes every composition
edge in one commit: core-api router mount + dep + router test, core-cms
header-global composition + dep + regenerated Payload types (globals
now empty), web-next bindAll (prod + dev-seed) + tests + Tailwind
source + transpilePackages + dep, cms/core-cms payload config test
assertions, home e2e nav assertion, tsconfig paths, fallow
ignoreDependencies entry, anchor-guard FEATURES list, generator e2e
strip lists + reference-feature comments (navigation -> auth, incl.
feature templates + scaffolding guide), lockfile prune, and
feature-list doc trims (CLAUDE.md, AGENTS.md, glossary, app/feature
AGENTS.md). Compliance YAML regeneration produced no churn (navigation
declared no PII).

Cycle break: navigation's UI hooks were the last edge closing the
committed core-trpc -> core-api -> navigation -> core-trpc package
cycle. With it gone, the lint turbo task graph builds for the first
time and every package's ESLint executes; the epic's lint waiver
expires here. Latent findings: 3 errors, all mechanical, fixed
in-slice - require() import in turbo/generators/config.ts
(no-require-imports), literal type assertion in auth's
authentication.service.ts (prefer-as-const), and next-env.d.ts
triple-slash in apps/cms (rule scoped off for that generated file,
mirroring web-next's existing override). 99 warn-severity findings
remain across 5 packages (pii-declaration-must-be-complete on test
fixtures, turbo/no-undeclared-env-vars on test env keys) - all
warn-by-design, non-gating.

core-trpc keeps a consumer (apps/web-next providers) and stays per
ADR-027. Its unused @trpc/react-query dependency, surfaced by the
post-deletion fallow audit, is removed rather than ignore-listed -
core-trpc's hooks use @trpc/tanstack-react-query. Remaining fallow
warn (auth validateSession "unused member") is a false positive: the
method implements IAuthenticationService and is exercised in
container.test.ts; auth stays untouched as the regression canary.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK

docs/glossary.md

@@ -22,7 +22,7 @@ _Avoid:_ module, library, app (unless specifically `apps/`).
 The boundary classification on a package (`app`, `core`, `core-composition`, `feature`, `tooling`). Enforced by ESLint (`eslint-plugin-boundaries`) and Turborepo `boundaries`. See `AGENTS.md` → Boundary Rules.
 
 **Feature** (a.k.a. **feature package**):
-A vertical slice owning its Clean Architecture layers + integrations under `packages/<name>/`. Currently: `auth`, `navigation`. **In architecture-refactor conversations (the `improve-codebase-architecture` skill), "module" defaults to "feature" — they're the same unit at the highest level of granularity.**
+A vertical slice owning its Clean Architecture layers + integrations under `packages/<name>/`. Currently: `auth`. **In architecture-refactor conversations (the `improve-codebase-architecture` skill), "module" defaults to "feature" — they're the same unit at the highest level of granularity.**
 _Avoid:_ domain, vertical (use "feature" or "vertical feature"). "Module" is acceptable inside the refactor skill specifically, where it abstractly covers "anything with interface + implementation" at any scale (use case, controller, repository port, or full feature).
 
 **Must-have core**:
@@ -190,7 +190,7 @@ The commit-message spec mandated by this template — `<type>(<scope>): <imperat
 The Google-maintained automation that reads Conventional Commits, derives semver bumps, and opens a rolling release PR with version bumps + per-package CHANGELOG entries on every push to main. Configured in `release-please-config.json` + `.release-please-manifest.json`. ADR-021.
 
 **Hybrid versioning**:
-The template's versioning strategy (ADR-021) — root template (`template-vertical`) + 2 feature packages (`@repo/{auth,navigation}`) version independently from `0.1.0`. Core packages, tooling, and apps are NOT versioned (cascade-effect would invalidate the signal).
+The template's versioning strategy (ADR-021) — root template (`template-vertical`) + 1 feature package (`@repo/auth`) version independently from `0.1.0`. Core packages, tooling, and apps are NOT versioned (cascade-effect would invalidate the signal).
 
 **Tag prefix**:
 The per-package prefix release-please uses to avoid tag collisions in a monorepo — `template-v0.1.0` for the root, `auth-v0.1.0` / etc. for features.

docs/guides/scaffolding-a-feature.md

@@ -1,7 +1,7 @@
 # Scaffolding a feature
 
 `turbo gen feature` produces a feature package under
-`packages/<name>/` matching the shape of the reference `navigation` feature.
+`packages/<name>/` matching the shape of the reference `auth` feature.
 
 ## Invoking the generator
 
@@ -122,7 +122,7 @@ The realtime generators insert at three additional fixed `// <gen:realtime-*>` a
 
 - `CLAUDE.md` — Key Conventions (factory-style use cases, `.toDynamicValue()`,
   schemas-in-use-case, three binding modes per feature, span + capture sandwich)
-- `packages/navigation/AGENTS.md` — canonical reference shape the templates mirror
+- `packages/auth/AGENTS.md` — canonical reference shape the templates mirror
 - `docs/architecture/vertical-feature-spec.md` — design rationale for the layout
 - `docs/decisions/adr-012-feature-conventions.md` — file naming + factory pattern
 - `docs/decisions/adr-013-input-output-unification.md` — schemas-in-use-case + presenter