@beignet/core 0.0.25 → 0.0.26

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @beignet/core
 
+## 0.0.26
+
+### Patch Changes
+
+- 104302c: Refresh package-shipped TanStack Intent skills and add package skills for Drizzle database providers, Better Auth, React Hook Form, and React uploads.
+
 ## 0.0.25
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beignet/core",
-  "version": "0.0.25",
+  "version": "0.0.26",
   "type": "module",
   "description": "Core framework primitives for Beignet",
   "exports": {

package/skills/app-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: app-architecture
-description: "Build Beignet app feature slices with @beignet/core primitives: schemas, contracts, use cases, app errors, ports, policies, context, providers, domain events, listeners, jobs, schedules, tasks, notifications, outbox, mail, uploads, seeds, tests, and explicit core subpath imports. Use when adding or fixing Beignet application behavior, dependency boundaries, app-facing ports, authorization, workflow primitives, or app-bound lib builders."
+description: "Build Beignet app feature slices with @beignet/core primitives: schemas, contracts, use cases, app errors, ports, policies, context, providers, domain events, listeners, jobs, schedules, tasks, notifications, outbox, mail, uploads, seeds, tests, auth helpers, audit, idempotency, storage, cache, rate limits, flags, entitlements, payments, search, webhooks, and explicit core subpath imports. Use when adding or fixing Beignet application behavior, dependency boundaries, app-facing ports, authorization, workflow primitives, or app-bound lib builders."
 ---
 
 # Beignet App Architecture
@@ -56,6 +56,9 @@ generator or deliberate feature change introduces that concern.
   clients.
 - UI and feature client modules call server behavior through contracts and a
   typed client, not by importing use cases.
+- Server, provider, and infra code may import `@beignet/core/server-only`;
+  browser-reachable client helpers may import `@beignet/core/client-only` as
+  lint markers when the app uses them.
 
 ## Contracts And Schemas
 
@@ -129,7 +132,8 @@ or outbox records must commit together.
 - `bound` ports are app-owned at boot, such as gates, config, clocks, IDs, or
   no-op reporters.
 - `deferred` ports are supplied by providers at startup, such as auth,
-  database, mail, logger, jobs, repositories, idempotency, and rate limits.
+  database, mail, logger, jobs, repositories, idempotency, rate limits,
+  storage, search, payments, flags, locks, and error reporting.
 
 Do not import provider packages from contracts, use cases, routes, UI, or
 feature client modules.
@@ -167,6 +171,12 @@ Register workflow artifacts explicitly:
 - outbox events and jobs in `server/outbox.ts`
 - seeds through the app's seed entrypoint, usually `infra/db/seed.ts`
 
+Uploads are feature-owned definitions under `features/<feature>/uploads/`,
+then exposed through an app route with `createUploadRouter(...)` and the
+platform adapter. Webhooks and payment webhooks are inbound transport concerns:
+define reusable verification or fulfillment in feature/application modules and
+keep provider-specific route glue in focused route files.
+
 Providers should not start unbounded background loops on server boot. Expose
 cron routes, worker entrypoints, task runners, schedule runners, or outbox
 drains instead.