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

apps/cms/AGENTS.md

@@ -49,14 +49,10 @@ When Payload imports `@payload-config`, it resolves to the composed config from
 ## Composition flow
 
 ```
-Feature 1 (@repo/auth)
+Feature (@repo/auth)
   └─ src/integrations/cms/collections/users.ts
       └─ exported as ./cms
 
-Feature 2 (@repo/navigation)
-  └─ src/integrations/cms/globals/header.ts
-      └─ exported as ./cms
-
 Core CMS (@repo/core-cms)
   └─ src/payload.config.ts
       imports all feature /cms exports

apps/cms/eslint.config.js

@@ -1,3 +1,11 @@
 import baseConfig from "@repo/core-eslint/base";
 
-export default baseConfig;
+export default [
+  ...baseConfig,
+  {
+    files: ["next-env.d.ts"],
+    rules: {
+      "@typescript-eslint/triple-slash-reference": "off",
+    },
+  },
+];

apps/cms/src/payload.config.test.ts

@@ -8,9 +8,9 @@ describe("CMS app payload.config", () => {
     expect(slugs).toEqual(expect.arrayContaining(["users"]));
   });
 
-  it("registers all feature globals", async () => {
+  it("registers no feature globals (none remain)", async () => {
     const resolved = await config;
     const slugs = resolved.globals?.map((g) => g.slug) ?? [];
-    expect(slugs).toEqual(expect.arrayContaining(["header"]));
+    expect(slugs).toEqual([]);
   });
 });