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
2.0 KiB
2.0 KiB
AGENTS.md — core-cms
Tag: core-composition
Composition-only package that aggregates feature Payload collections and globals into a single Payload config. It does not define its own collections; instead, it imports them from feature packages.
Responsibilities
- Compose Payload config —
buildConfig()with all collections and globals from features - Type generation — Output
generated-types.tsfrom Payload's TypeScript generator - No collection definitions — all collections owned by their respective features (
@repo/auth,@repo/blog, etc.) - No business logic — purely structural assembly
Allowed imports
@repo/<feature>/cmssubpath exports only (to get collections/globals)- e.g.,
import { articles } from "@repo/blog/cms" - e.g.,
import { users } from "@repo/auth/cms"
- e.g.,
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-shared,@repo/core-api,@repo/core-trpc,@repo/core-ui
Note:
@repo/core-trpcand@repo/core-uiare optional packages scaffolded viapnpm turbo gen core-package trpc/ui. If not present, these constraints still apply to any future installation.
Public exports
From package.json:
.— the Payload config (default export) + buildConfig re-export./generated-types— Payload-generated TypeScript types
Example usage:
import { buildConfig } from "@repo/core-cms";
// or
import type { Config, User, Article } from "@repo/core-cms/generated-types";
Test conventions
- No unit tests (composition layer)
- Verify at app boot:
pnpm dev --filter @repo/cmssucceeds and admin UI loads - Type generation:
pnpm generate:typesinapps/cms
Structure
src/
payload.config.ts # imports feature /cms exports, calls buildConfig()
generated-types.ts # auto-generated by Payload
index.ts # re-exports config