feat(console-kit): align blocks around feature packs

.github/workflows/ci.yml

@@ -5,6 +5,8 @@ on:
     branches: [main]
     tags:
       - '@constructive-io/ui@*'
+      - '@constructive-io/data@*'
+      - '@constructive-io/sheets@*'
       - '@constructive-io/schema-builder@*'
   pull_request:
     branches: [main]
@@ -42,7 +44,32 @@ jobs:
       - name: Build shadcn registry
         run: pnpm build:registry
 
+  packages:
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v6
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v7
+        with:
+          node-version: '24'
+          cache: pnpm
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Verify packed packages in clean consumers
+        run: pnpm pack:check
+
   pages:
+    needs: packages
     runs-on: ubuntu-latest
     timeout-minutes: 20
     steps:

.gitignore

@@ -143,3 +143,6 @@ dist
 vite.config.js.timestamp-*
 vite.config.ts.timestamp-*
 .vite/
+
+# Local proof and visual QA artifacts
+.local/

AGENTS.md

@@ -1,17 +1,20 @@
 # Constructive Blocks Repository Guide
 
 This public monorepo owns the Constructive Blocks documentation, the
-`@constructive` shadcn registry, and the `@constructive-io/ui` and
-`@constructive-io/schema-builder` packages.
+`@constructive` shadcn registry, and the `@constructive-io/ui`,
+`@constructive-io/data`, and `@constructive-io/sheets` packages. The local
+schema-builder package remains in the workspace but is not part of the public
+registry.
 
 ## Invariants
 
-- Canonical source lives in `apps/blocks`, `packages/ui`, and
-  `packages/schema-builder`; do not edit generated registry output.
+- Canonical public source lives in `apps/blocks`, `packages/ui`,
+  `packages/data`, and `packages/sheets`; do not edit generated registry output.
 - Keep the registry collision-free and `@constructive`-namespaced.
-- Preserve registry requirements sidecars.
+- Preserve the seven feature-pack manifests and four experimental preset
+  profiles installed under `.constructive/feature-packs`.
 - Never auto-discover or mutate sibling repositories from flow tooling.
-- Keep generated SDK fixtures pruned and normal CI independent of live endpoints.
+- Keep normal CI independent of generated SDKs and live endpoints.
 - Never add automated npm publishing; publish verified tarballs manually.
 
 ## Verification

CLAUDE.md

@@ -1,20 +1,23 @@
 # Constructive Blocks Repository Guide
 
 This public monorepo owns the Constructive Blocks documentation, the
-`@constructive` shadcn registry, and the `@constructive-io/ui` and
-`@constructive-io/schema-builder` packages.
+`@constructive` shadcn registry, and the `@constructive-io/ui`,
+`@constructive-io/data`, and `@constructive-io/sheets` packages. The local
+schema-builder package remains available for development but is delisted from
+the public registry.
 
 ## Invariants
 
-- `apps/blocks`, `packages/ui`, and `packages/schema-builder` are canonical
-  source trees; generated registry output is never edited.
+- `apps/blocks`, `packages/ui`, `packages/data`, and `packages/sheets` are
+  canonical public source trees; generated registry output is never edited.
 - The combined registry must remain collision-free and every install command
   must use the `@constructive` namespace.
-- Registry requirements sidecars are part of the public contract.
+- Feature-pack and preset manifests installed under
+  `.constructive/feature-packs` are part of the public contract.
 - Flow outputs outside this repository are generated only when explicit output
   environment variables are supplied.
-- Generated SDK fixtures are intentionally pruned. Refresh them explicitly;
-  do not add complete SDK trees or make normal CI depend on live endpoints.
+- Blocks use injected endpoints, sessions, and adapters. Do not add generated
+  SDK trees or make normal CI depend on live endpoints.
 - npm packages are versioned with Lerna and published manually from locally
   verified tarballs. Do not add automated npm publishing.
 

README.md

@@ -8,7 +8,9 @@ component documentation, and published React packages.
 - `apps/blocks` — primitive documentation and canonical block source.
 - `apps/registry` — private builder for the `@constructive` shadcn registry.
 - `packages/ui` — the `@constructive-io/ui` npm package and UI registry source.
-- `packages/schema-builder` — the shared schema-builder npm package and registry source.
+- `packages/data` — runtime GraphQL generation and the strict July 2026 `_meta` contract.
+- `packages/sheets` — the metadata-driven application CRUD grid.
+- `packages/schema-builder` — retained platform/operator tooling that is delisted from the public registry.
 
 The documentation site is published at
 <https://constructive-io.github.io/blocks/>. Registry JSON is served from
@@ -21,9 +23,10 @@ its own:
 ```bash
 pnpm add @constructive-io/ui
 pnpm dlx shadcn@4.13.1 add @constructive/button
+pnpm dlx shadcn@4.13.1 add @constructive/console-kit-nextjs
 ```
 
-The package exposes its Tailwind foundation at
+The UI package exposes its Tailwind foundation at
 `@constructive-io/ui/globals.css`. Registry installs copy the required UI
 source and Constructive theme into the consumer and do not install the npm
 package. Registry consumers require shadcn CLI 4.13.1 or newer.
@@ -42,6 +45,13 @@ first-party executable tooling is TypeScript and runs through `tsx`.
 Use `pnpm check:full` when validating Storybook, registry installation, and
 publishable package artifacts together.
 
+Console Kit and the feature packs are source-installed blocks. They accept
+database-scoped endpoints, a host-owned session, and provider-neutral adapters;
+they do not require generated SDKs or environment-specific global clients. A
+Console Kit instance owns one Zustand store composed from separate navigation,
+runtime, and adapter slices, which keeps state isolated across mounts and
+server requests.
+
 `pnpm pack:local` builds the public packages and writes publishable tarballs to
 the ignored `.artifacts/npm` directory. Consume those tarballs from downstream
 projects before publishing so validation exercises the real package contents.

apps/blocks/README.md

@@ -1,8 +1,8 @@
 # Blocks docs
 
-This Next.js app is the clean documentation surface for the Constructive UI foundation. It intentionally exposes only
-the landing page, setup guidance, and the 29 base primitive pages while the complete block catalog remains available
-through the public registry.
+This Next.js app documents the Constructive Blocks registry: the UI foundation,
+29 base primitives, customer billing blocks, seven capability-aligned feature
+packs, and Console Kit.
 
 The same primitive implementation is shown through two distribution modes:
 
@@ -18,9 +18,10 @@ pnpm --filter blocks test
 pnpm --filter blocks build:pages
 ```
 
-`src/lib/base-primitives.ts` is the single docs catalog. `pnpm gen:check` validates that every entry has an npm export,
-a registry item, and a preview that imports the npm subpath. The SDK fixture and mutation-selection checks remain in
-place for the canonical block source under `src/blocks`.
+`src/lib/base-primitives.ts`, `src/lib/billing-blocks.ts`, and
+`src/lib/feature-packs.ts` are the documentation catalogs. `pnpm gen:check`
+validates primitive distribution and keeps the feature-pack docs aligned with
+their manifests, registry roots, and live previews.
 
 The static Pages build uses `/blocks` as its deployment base path. Publishing npm packages remains a separate manual
 release step.