feat: foundation (milestone 1) and DTCG token core #1
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/foundation-and-token-core"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Milestone 1 (foundation) complete, plus the core of milestone 2 (DTCG token engine, drafts, versions).
Request path and access check:
Token resolution order (ADR 0006): primitive -> semantic -> component -> project override -> mode -> project override for that mode, then alias resolution on the merged tree.
Evidence
README.mdonly).After:
pnpm lintclean,pnpm typecheck5/5 packages@designbase/core41 tests (access rules, alias chains, cycles reported per member, modes + overrides, diff -> operations round trip, CSS output, WCAG contrast, starter palette passes AA in light and dark)@designbase/api37 tests throughapp.inject()against real Postgres 18 (auth rejection, org/member/invitation rules, last-owner protection, sharing, cross-org isolation, draft revision conflicts, publish blocked on invalid tokens, semver bump suggestion)@designbase/web16 tests (Testing Library + MSW)docker compose up(built images, migrations, seed), walked through sign-up, invitations, editor and viewer views, light and dark themes.Merge Danger
Door: two-way
First code on
main; nothing deployed depends on it. The two migrations become the baseline once anyone runs them, so later schema changes must be new migrations.Blast Radius: none
Notes for review:
trail checkreports 20 conflicts. All are keyword matches on this branch's own learnings ("drizzle-orm must come from @designbase/db/orm" and "token documents are json, not jsonb"); the flagged lines follow both rules..forgejo/workflows/ci.yml) expecting a runner labelleddocker; it has not run yet.🤖 Generated with Claude Code