Template

Files

Danijel Martinek 48bf4da4cd 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

2026-07-12 19:34:54 +02:00

1.6 KiB

Raw Blame History

AGENTS.md — core-api

Tag: core-composition

Composition-only package that aggregates feature tRPC routers into a single root appRouter. It does not define procedures; instead, it imports them from feature packages.

Responsibilities

Compose tRPC appRouter — merges feature routers into t.router({ ... })
Type export — exports AppRouter type for frontend type safety
No procedure definitions — all routers owned by their respective features (@repo/auth, @repo/blog, etc.)
No business logic — purely structural assembly

Allowed imports

@repo/<feature>/api subpath exports only (to get tRPC routers)
- e.g., import { authRouter } from "@repo/auth/api"
- e.g., import { blogRouter } from "@repo/blog/api"
@repo/core-shared/trpc/init — for t.router() builder

Must NOT import

Any feature's root package or other subpaths (e.g., NOT @repo/blog/di, NOT @repo/blog/entities)
Any app package
@repo/core-cms, @repo/core-trpc, @repo/core-ui

Public exports

From package.json:

. — appRouter and AppRouter type

Example usage:

import { appRouter, type AppRouter } from "@repo/core-api";

Test conventions

No unit tests (composition layer)
Verify at app boot: pnpm dev --filter @repo/web-next succeeds and tRPC client fetches data
Run router health check: pnpm typecheck confirms AppRouter type is valid

Structure

src/
  root.ts                    # t.router({ ... }) aggregating all feature routers
  index.ts                   # re-exports appRouter + type

1.6 KiB Raw Blame History