feat(tooling): pre-ship approved library traces in optional core generator templates

Each of the five optional core package generators (events, realtime, audit,
trpc, ui) now copies pre-written decision: approved trace files into
docs/library-decisions/ at scaffold time, covering every direct runtime
dependency of that core package.

This prevents a pre-commit gate failure the first time a developer runs
pnpm turbo gen core-package <name> — the generator is the policy-compliant
path, so the traces land by construction.

- Added docs/library-decisions/*.md.hbs trace files under each of the five
  core-package template directories (15 files total)
- Updated generator config to emit traces into workspace docs/library-decisions/
  via a second emitTemplateTree call per core package
- Updated all five __snapshots__/core-package/*.snapshot.json to include the
  new trace file entries
- Added verify-doc-shas.test.ts to pin SHA256 hashes of all 15 trace templates
  so snapshot and file content cannot drift independently

ADR refs: events→ADR-015, realtime→ADR-016, audit→ADR-018;
trpc and ui cite closest ADR or null where no specific ADR exists.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-05-14 09:34:17 +00:00
parent 090410e9c3
commit b1e2e8a788
23 changed files with 1248 additions and 10 deletions

View File

@@ -0,0 +1,68 @@
---
package: "@tanstack/react-query"
version: "^5.66.0"
tier: core
decision: approved
date: 2026-05-14
deciders: [scaffolded]
adr: null
filter-results:
license: MIT
types: native
maintenance: active
boundary-fit: pass
shadow-check: pass
eu-residency: n/a
cve-scan: clean
named-consumer: pass
verification-commands:
- pnpm audit --audit-level=moderate
- npm view @tanstack/react-query license
accepted-cves: []
---
## Filter: license
MIT — on the workspace allowlist.
## Filter: types
Ships first-party TypeScript types in its distribution.
## Filter: maintenance
Active. Maintained by the TanStack team; v5 is the current stable major.
## Filter: boundary-fit
Core package (client-side). Used exclusively in `core-trpc` to power the React Query integration layer. No boundary rule violation.
## Filter: shadow-check
No other server-state library in the workspace. No shadow.
## Filter: eu-residency
Client-side state management; no network calls to vendor endpoints. n/a.
## Filter: cve-scan
No advisories at adoption time.
## Filter: named-consumer
`core-trpc` exposes the `QueryClient` and React Query hooks via `@trpc/react-query`.
## Prompt: replaces
Nothing — this is the initial tRPC scaffold.
## Prompt: migration-cost-out
Hard: query keys, cache invalidation patterns, and mutation hooks are all shaped around React Query's API.
## Prompt: alternatives-considered
1. **SWR** — narrower feature set; less aligned with tRPC's first-class React Query adapter.
2. **RTK Query** — Redux-bound; heavier than needed for this use case.
React Query is tRPC's canonical client-side data-fetching companion.

View File

@@ -0,0 +1,68 @@
---
package: "@trpc/client"
version: "^11.0.0"
tier: core
decision: approved
date: 2026-05-14
deciders: [scaffolded]
adr: null
filter-results:
license: MIT
types: native
maintenance: active
boundary-fit: pass
shadow-check: pass
eu-residency: n/a
cve-scan: clean
named-consumer: pass
verification-commands:
- pnpm audit --audit-level=moderate
- npm view @trpc/client license
accepted-cves: []
---
## Filter: license
MIT — on the workspace allowlist.
## Filter: types
Ships first-party TypeScript types; end-to-end type safety is the library's primary value.
## Filter: maintenance
Active. Maintained by the tRPC team; v11 is the current stable line.
## Filter: boundary-fit
Core package. `@trpc/client` is the companion to `@trpc/server` (present in `core-api`). No boundary rule violation.
## Filter: shadow-check
No competing RPC client in the workspace. No shadow.
## Filter: eu-residency
Client-side HTTP transport; calls the workspace's own tRPC server, no third-party vendor. n/a.
## Filter: cve-scan
No advisories at adoption time.
## Filter: named-consumer
`core-trpc` uses `@trpc/client` to build the typed HTTP client exposed to feature packages.
## Prompt: replaces
Nothing — this is the initial tRPC scaffold.
## Prompt: migration-cost-out
Hard: the typed client is tightly coupled to the server router type; replacing requires re-implementing the client abstraction.
## Prompt: alternatives-considered
1. **Plain fetch** — loses end-to-end type safety.
2. **GraphQL client** — significantly heavier; not aligned with the workspace API shape.
`@trpc/client` is the only viable companion to `@trpc/server`.

View File

@@ -0,0 +1,66 @@
---
package: "@trpc/react-query"
version: "^11.0.0"
tier: core
decision: approved
date: 2026-05-14
deciders: [scaffolded]
adr: null
filter-results:
license: MIT
types: native
maintenance: active
boundary-fit: pass
shadow-check: pass
eu-residency: n/a
cve-scan: clean
named-consumer: pass
verification-commands:
- pnpm audit --audit-level=moderate
- npm view @trpc/react-query license
accepted-cves: []
---
## Filter: license
MIT — on the workspace allowlist.
## Filter: types
Ships first-party TypeScript types; deeply integrated with tRPC's type inference.
## Filter: maintenance
Active. Maintained by the tRPC team alongside `@trpc/server` and `@trpc/client`.
## Filter: boundary-fit
Core package. The React Query integration bridge belongs in `core-trpc` alongside its sibling tRPC packages. No boundary rule violation.
## Filter: shadow-check
No other tRPCReact Query bridge in the workspace. No shadow.
## Filter: eu-residency
Client-side integration adapter; no vendor data transmission. n/a.
## Filter: cve-scan
No advisories at adoption time.
## Filter: named-consumer
`core-trpc` re-exports `@trpc/react-query` hooks for use in Next.js feature pages.
## Prompt: replaces
Nothing — this is the initial tRPC scaffold.
## Prompt: migration-cost-out
Hard: hooks are tRPC-procedure-typed; migrating away requires replacing all call sites.
## Prompt: alternatives-considered
This package is the canonical integration point between `@trpc/client` and `@tanstack/react-query`. No viable alternative exists.

View File

@@ -0,0 +1,68 @@
---
package: "@trpc/server"
version: "^11.0.0"
tier: core
decision: approved
date: 2026-05-14
deciders: [scaffolded]
adr: null
filter-results:
license: MIT
types: native
maintenance: active
boundary-fit: pass
shadow-check: pass
eu-residency: n/a
cve-scan: clean
named-consumer: pass
verification-commands:
- pnpm audit --audit-level=moderate
- npm view @trpc/server license
accepted-cves: []
---
## Filter: license
MIT — on the workspace allowlist.
## Filter: types
Ships first-party TypeScript types; type-safe by design.
## Filter: maintenance
Active. Maintained by the tRPC team; v11 is the current stable line.
## Filter: boundary-fit
Core package. `@trpc/server` is also present in `core-api`; using the same version in `core-trpc` for router type inference is the intended usage pattern.
## Filter: shadow-check
`@trpc/server` is workspace-present via `core-api`. Same major version; no shadow.
## Filter: eu-residency
Server-side RPC framework; no vendor data transmission. n/a.
## Filter: cve-scan
No advisories at adoption time.
## Filter: named-consumer
`core-trpc` re-exports tRPC router types and the `t` initializer used by feature routers.
## Prompt: replaces
Nothing — tRPC is already the workspace API layer via `core-api`.
## Prompt: migration-cost-out
Hard: router types, procedure definitions, and middleware are tRPC-shaped across the entire workspace.
## Prompt: alternatives-considered
1. **REST + OpenAPI** — loses end-to-end type safety; see ADR-022 context for why this was rejected.
2. **GraphQL** — significantly heavier; not aligned with the workspace API shape.
tRPC is the locked workspace API library.

View File

@@ -0,0 +1,66 @@
---
package: "@trpc/tanstack-react-query"
version: "^11.1.0"
tier: core
decision: approved
date: 2026-05-14
deciders: [scaffolded]
adr: null
filter-results:
license: MIT
types: native
maintenance: active
boundary-fit: pass
shadow-check: pass
eu-residency: n/a
cve-scan: clean
named-consumer: pass
verification-commands:
- pnpm audit --audit-level=moderate
- npm view @trpc/tanstack-react-query license
accepted-cves: []
---
## Filter: license
MIT — on the workspace allowlist.
## Filter: types
Ships first-party TypeScript types; part of the tRPC v11 adapter suite.
## Filter: maintenance
Active. Maintained by the tRPC team as part of the v11 TanStack Start integration.
## Filter: boundary-fit
Core package. Required for the TanStack Start provider (`core-trpc/tanstack`). No boundary rule violation.
## Filter: shadow-check
No duplicate TanStack adapter in the workspace. No shadow.
## Filter: eu-residency
Client-side integration adapter; no vendor data transmission. n/a.
## Filter: cve-scan
No advisories at adoption time.
## Filter: named-consumer
`core-trpc` exposes a TanStack Start provider via `@trpc/tanstack-react-query` for `apps/web-tanstack`.
## Prompt: replaces
Nothing — this is the initial tRPC scaffold.
## Prompt: migration-cost-out
Hard: the TanStack provider is shaped around this adapter's API; replacing requires re-implementing the provider.
## Prompt: alternatives-considered
This is the official tRPC adapter for TanStack Start. No viable alternative exists.

View File

@@ -0,0 +1,66 @@
---
package: react
version: "^19.0.0"
tier: core
decision: approved
date: 2026-05-14
deciders: [scaffolded]
adr: null
filter-results:
license: MIT
types: "@types/react"
maintenance: active
boundary-fit: pass
shadow-check: pass
eu-residency: n/a
cve-scan: clean
named-consumer: pass
verification-commands:
- pnpm audit --audit-level=moderate
- npm view react license
accepted-cves: []
---
## Filter: license
MIT — on the workspace allowlist.
## Filter: types
TypeScript types via `@types/react` (community-maintained but canonical; ships in sync with each React major).
## Filter: maintenance
Active. Maintained by Meta; v19 is the current stable major.
## Filter: boundary-fit
Core package (client-side). React is already present in app packages; exposing it from `core-trpc` for provider components is standard practice.
## Filter: shadow-check
React is already workspace-present in app packages. Same major version; no shadow.
## Filter: eu-residency
Client-side rendering library; no vendor data transmission. n/a.
## Filter: cve-scan
No advisories at adoption time.
## Filter: named-consumer
`core-trpc` uses React to implement the `TRPCProvider` and `QueryClientProvider` wrapper components.
## Prompt: replaces
Nothing — React is already the UI framework in the workspace.
## Prompt: migration-cost-out
Impossible: React is the foundational UI library for this workspace.
## Prompt: alternatives-considered
React is workspace-locked as the UI framework. No alternative evaluated.

View File

@@ -0,0 +1,68 @@
---
package: superjson
version: "^2.2.1"
tier: core
decision: approved
date: 2026-05-14
deciders: [scaffolded]
adr: null
filter-results:
license: MIT
types: native
maintenance: active
boundary-fit: pass
shadow-check: pass
eu-residency: n/a
cve-scan: clean
named-consumer: pass
verification-commands:
- pnpm audit --audit-level=moderate
- npm view superjson license
accepted-cves: []
---
## Filter: license
MIT — on the workspace allowlist.
## Filter: types
Ships first-party TypeScript types in its distribution.
## Filter: maintenance
Active. Currently maintained by the tRPC team after the original author transferred stewardship.
## Filter: boundary-fit
Core package. superjson is used exclusively in `core-trpc` as the tRPC transformer; no feature package imports it directly.
## Filter: shadow-check
No competing JSON-extended serializer in the workspace. No shadow.
## Filter: eu-residency
Pure serialization library; no network calls or vendor data transmission. n/a.
## Filter: cve-scan
No advisories at adoption time.
## Filter: named-consumer
`core-trpc` uses superjson as the tRPC transformer to support `Date`, `Map`, `Set`, and other non-JSON-native types over the wire.
## Prompt: replaces
Nothing — this is the initial tRPC scaffold.
## Prompt: migration-cost-out
Mechanical: swap transformer in the tRPC init; update client config. No data-storage coupling.
## Prompt: alternatives-considered
1. **devalue** — no stable npm release at adoption time.
2. **Plain JSON** — loses Date/Map/Set round-trip support required by the workspace's domain models.
superjson is the tRPC-canonical transformer for extended types.