Update hivegrid-cloud reference to latest main

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
davidandClaude Fable 5 committed 2026-07-08 16:15:37 +02:00
1 parent e98d38e716
commit 7b21524c86
3781 files changed
+373484 -225607

No files matched your search

@@ -5,15 +5,15 @@ Use this when moving feature logic into the reusable boilerplate layer or when t
## Ownership Rules
- Runtime apps may orchestrate requests, headers, sessions, and responses.
- Shared business rules belong in `packages/*`, preferably `@toolctrl/foundation` for pure policy and `@toolctrl/db` for schema-backed server boundaries.
- Shared business rules belong in `packages/*`, preferably `@hivegrid/foundation` for pure policy and `@hivegrid/db` for schema-backed server boundaries.
- UI and route modules must not reach around package boundaries for tenant-scoped persistence.
- Foundation exports must stay generic. Do not add product-specific roles, flags, templates, adapters, or catalog entries.
## Required Checks
- Audit writes use `@toolctrl/db/audit-events.server`.
- Idempotency keys use `@toolctrl/db/idempotency-keys.server` or the API idempotency store bridge.
- API usage limits use `@toolctrl/db/usage.server`; API routes should not recompute subscription feature math locally.
- Audit writes use `@hivegrid/db/audit-events.server`.
- Idempotency keys use `@hivegrid/db/idempotency-keys.server` or the API idempotency store bridge.
- API usage limits use `@hivegrid/db/usage.server`; API routes should not recompute subscription feature math locally.
- Notification deliveries use `sourceKey` whenever a producer can derive a stable event key, so DB upsert prevents duplicate delivery records.
- Feature flags resolve in this order: explicit override, user scope, tenant scope, global scope, default.
@@ -4,7 +4,7 @@ Use this when moving UI primitives toward `packages/ui` hotswap-ready adapters.
## Goal
App code should eventually depend on stable adapter contracts such as `@toolctrl/ui/buttons`, not directly on a specific library implementation. Migration happens category by category.
App code should eventually depend on stable adapter contracts such as `@hivegrid/ui/buttons`, not directly on a specific library implementation. Migration happens category by category.
## Migration Order
@@ -53,7 +53,7 @@ For each category migration:
Current button adapter contract:
- `@toolctrl/ui/buttons`
- `@hivegrid/ui/buttons`
- `buttonAdapterNames`
- `buttonAdapters`
- source: `apps/web/app/components/ui/button.tsx`
@@ -64,10 +64,10 @@ This records stable intent without moving the current shadcn implementation yet.
Current shell/navigation adapter contracts:
- `@toolctrl/ui/layout`
- `@hivegrid/ui/layout`
- `layoutAdapterNames`
- `layoutAdapters`
- `@toolctrl/ui/navigation`
- `@hivegrid/ui/navigation`
- `navigationAdapterNames`
- `navigationAdapters`
@@ -31,7 +31,7 @@ The feature manifest must declare:
- Jobs should be idempotent or have explicit duplicate protection.
- Browser jobs must enforce admin-owned navigation policy.
- Failures should be visible to the initiating user or admin.
- AI/browser-backed features use `toolctrl.ai-chatbot` and `toolctrl.browser-automation` unless a manifest explicitly justifies a new queue.
- AI/browser-backed features use `hivegrid.ai-chatbot` and `hivegrid.browser-automation` unless a manifest explicitly justifies a new queue.
## Browser-Backed Work