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

@@ -22,11 +22,11 @@ Downstream documentation slices should compare their proposed edits against the
| Legacy or ambiguous source term | Preferred documentation term | Apply in docs when | Notes and examples |
| --- | --- | --- | --- |
| `SaasRock`, `SaasRock Boilerplate`, `saasrock` | Current boilerplate wording | Product, project, setup, architecture, and roadmap prose that describes the current repository. | Keep historical references only when naming an archived upstream source or old decision context. |
| `saasrock.com`, `www.saasrock.com`, SaasRock marketing domains | Neutral local/example domain wording | Domain examples, mail examples, deployment examples, and screenshots that should represent the current project. | Prefer `app.localhost:3000` and `admin.localhost:3000` for the default web dev loop; use `api.localhost:3001` only when the standalone API runtime is started separately. Use `example.com` / `app.example.com` for tenant-safe examples unless a deployment-specific domain is explicitly documented. |
| `SaasRock LLC`, old SaasRock legal branding, old trademark/legal wording | Current project/legal owner wording or neutral placeholder | Legal, privacy, imprint, footer, and branding documentation. | Do not invent legal claims. If ownership is unknown, use a placeholder and mark the document as needing legal review outside the code task summary, not with inline TODO markers. |
| `LegacySourceProduct`, `Legacy Source Product`, `legacy-source-product` | Current boilerplate wording | Product, project, setup, architecture, and roadmap prose that describes the current repository. | Keep historical references only when naming an archived upstream source or old decision context. |
| `legacy-source.example`, `www.legacy-source.example`, LegacySourceProduct marketing domains | Neutral local/example domain wording | Domain examples, mail examples, deployment examples, and screenshots that should represent the current project. | Prefer `app.localhost:3000` and `admin.localhost:3000` for the default web dev loop; use `api.localhost:3001` only when the standalone API runtime is started separately. Use `example.com` / `app.example.com` for tenant-safe examples unless a deployment-specific domain is explicitly documented. |
| `Legacy Source Product LLC`, old LegacySourceProduct legal branding, old trademark/legal wording | Current project/legal owner wording or neutral placeholder | Legal, privacy, imprint, footer, and branding documentation. | Do not invent legal claims. If ownership is unknown, use a placeholder and mark the document as needing legal review outside the code task summary, not with inline TODO markers. |
| Product-brand variants in prose | Generic boilerplate wording | Human-readable product or brand references. | Keep actual package names, queue names, runner labels, and other runtime identifiers unchanged. |
| Root package display names inherited from old boilerplate | `toolctrl-boilerplate` | Documentation that names the root `package.json` project. | Confirm against root `package.json` before changing package-manager or script examples. |
| Root package display names inherited from old boilerplate | `hivegrid-cloud` | Documentation that names the root `package.json` project. | Confirm against root `package.json` before changing package-manager or script examples. |
| Generic `SaaS boilerplate` where it means this repository | Current boilerplate | Repository-specific docs, quick-start text, architecture handoffs, and migration plans. | Keep generic `SaaS` only when the sentence describes the product category rather than the repository name. |
| Old monolith wording that implies all runtime code is root-only | `apps/web` web source plus workspace boundaries | Architecture docs and migration status docs. | State that `apps/web/app` owns web source while root scripts keep top-level command compatibility and `apps/api`, `apps/worker`, and selected `packages/*` provide target or runtime-wired boundaries. |
| `Remix` runtime wording where it describes current root app execution | `React Router` runtime | Current runtime commands, build, route, and app-shell descriptions. | Preserve `remix-i18next` and dependency names when referring to actual package names. |
@@ -53,11 +53,11 @@ Downstream documentation slices should compare their proposed edits against the
Do not blindly rename the following public, runtime, package, or historical identifiers while porting documentation:
- `@toolctrl/*` workspace imports and package names, including `@toolctrl/config`, `@toolctrl/db`, `@toolctrl/mail`, `@toolctrl/queue`, and `@toolctrl/ui`.
- Root package and workspace package names that are confirmed by `package.json` files, including `toolctrl-boilerplate`.
- Queue names and runtime strings such as `toolctrl.email` when they represent actual queue identifiers or integration contracts.
- `@hivegrid/*` workspace imports and package names, including `@hivegrid/config`, `@hivegrid/db`, `@hivegrid/mail`, `@hivegrid/queue`, and `@hivegrid/ui`.
- Root package and workspace package names that are confirmed by `package.json` files, including `hivegrid-cloud`.
- Queue names and runtime strings such as `hivegrid.email` when they represent actual queue identifiers or integration contracts.
- Environment variable names such as `APP_NAME`, `SESSION_SECRET`, `CRYPTO_SECRET`, `DATABASE_URL`, `DIRECT_URL`, `WORKER_ENABLED`, `BULLMQ_REDIS_URL`, and `REDIS_URL`.
- Database, Prisma, migration, and generated-client paths such as `prisma/`, `prisma/schema/schema.prisma`, `packages/db/generated/prisma/client`, and `@toolctrl/db/client.server`.
- Database, Prisma, migration, and generated-client paths such as `prisma/`, `prisma/schema/schema.prisma`, `packages/db/generated/prisma/client`, and `@hivegrid/db/client.server`.
- Current local examples that are still accurate, especially `app.localhost:3000` and `admin.localhost:3000` for the default web loop, `api.localhost:3001` only for the standalone API runtime, `127.0.0.1`, seeded users such as `admin@email.com`, and sample passwords used only in local seed documentation.
- Third-party product names that describe actual dependencies or providers, including Prisma, PostgreSQL, Supabase-style PostgreSQL URLs, Redis, BullMQ, Mailjet, Hono, React Router, Gitea, Docker, Fly.io, Vercel, AWS Lightsail, and Coolify.
- Historical decision/report references, milestone IDs, slice IDs, decision IDs, and files under `.tc/` or `docs/feature-decisions/` unless a task explicitly updates those records.
@@ -99,7 +99,7 @@ Do not blindly rename the following public, runtime, package, or historical iden
- Use `PostgreSQL` and `Prisma` for the active database stack.
- Use `Mailjet` for transactional mail provider wording.
- Use `BullMQ` and Redis only where worker/queue behavior is being described.
- Use `React Router` for the current `@toolctrl/web` runtime under `apps/web/app`.
- Use `React Router` for the current `@hivegrid/web` runtime under `apps/web/app`.
- Use `Hono` for the `apps/api` runtime-wired API app.
## Verification