Update hivegrid-cloud reference to latest main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
e98d38e716
commit
7b21524c86
3781 files changed
+373484
-225607
No files matched your search
+13
-13
@@ -4,7 +4,7 @@
|
||||
|
||||
Decision: `extract-plugin`
|
||||
|
||||
Portals/Sites are classified by D007 as an optional plugin candidate, not as Boilerplate Core and not as an immediate removal target. This report is the canonical Portals/Sites lifecycle source for Feature Decision/S03 and carries forward the D006 deferral that kept Portals/Sites persistence in module-owned DB files until the Feature Decision feature decision was made. The current code surfaces are retained as plugin-candidate inventory, while default core route registration disables the portal/site route trees. Later implementation work must preserve or explicitly remove the retained schema, Stripe billing, analytics, domains, sidebar, docs, environment, and verification boundaries atomically.
|
||||
Portals/Sites are classified by D007 as an optional plugin candidate, not as Boilerplate Core and not as an immediate removal target. This report is the canonical Portals/Sites lifecycle source for Feature Decision/S03 and carries forward the D006 deferral that kept Portals/Sites persistence in module-owned DB files until the Feature Decision feature decision was made. The current code surfaces are retained as plugin-candidate inventory, while default core route registration disables the portal/site route trees. Later implementation work must preserve or explicitly remove the retained schema, billing provider, analytics, domains, sidebar, docs, environment, and verification boundaries atomically.
|
||||
|
||||
No runtime code is changed in this slice. This slice only records the decision report and prepares the later static verifier/execution plan so downstream agents do not blindly alter retained Portals/Sites surfaces or mistake disabled plugin routes for active core routes.
|
||||
|
||||
@@ -19,30 +19,30 @@ The canonical inventory and manifest references are `docs/feature-inventory.md`
|
||||
Concrete Portals/Sites surfaces that later work must audit before any runtime change. Route paths listed here are retained plugin-candidate code surfaces, not active default core route registrations:
|
||||
|
||||
- Modules: `apps/web/app/modules/portals` and `apps/web/app/modules/sites`.
|
||||
- Admin route: `apps/web/app/routes/admin/portals.tsx`.
|
||||
- Admin route: removed from the default HiveGrid admin surface; tenant portal routes remain inventoried as plugin-candidate code.
|
||||
- Tenant portal routes: `apps/web/app/routes/app.$tenant/__portals/*`.
|
||||
- Tenant site routes: `apps/web/app/routes/app.$tenant/sites/*`.
|
||||
- Portal Stripe services: `apps/web/app/modules/portals/services/PortalStripe.server.ts` and `apps/web/app/modules/portals/services/StripeConnect.server.ts`.
|
||||
- Portal billing provider services: `apps/web/app/modules/portals/services/PortalPayment provider.server.ts` and `apps/web/app/modules/portals/services/Payment providerConnect.server.ts`.
|
||||
- Module-owned persistence: `apps/web/app/modules/portals/db/portals.db.server.ts` and `apps/web/app/modules/sites/db/sites.db.server.ts`.
|
||||
- Site configuration types: `apps/web/app/modules/sites/site-types.ts`.
|
||||
- Analytics coupling: `apps/web/app/routes/admin/analytics/page-views.tsx` and `prisma/schema/analytics.prisma`.
|
||||
- Analytics coupling: `prisma/schema/analytics.prisma` powers portal analytics; the old admin analytics route was removed from the core admin surface.
|
||||
- Domains coupling: `apps/web/app/modules/domains/services/Domains.server.ts`.
|
||||
- Sidebar coverage: `apps/web/app/application/sidebar/AppSidebar.test.tsx`.
|
||||
- Prisma schema surfaces: `prisma/schema/portals.prisma` and `prisma/schema/sites.prisma`.
|
||||
- Environment documentation: `.env.example`, `.env.production.example`, and `.env.fly.example`.
|
||||
- Environment documentation: `.env.example` and `.env.production.example`.
|
||||
- Documentation and manifest contracts: `docs/feature-inventory.md` and `docs/feature-manifests/plugin-candidates.json`.
|
||||
|
||||
## Couplings
|
||||
|
||||
Portals/Sites are coupled to tenant navigation, admin management, analytics reporting, domain resolution, Stripe billing flows, Prisma schema, and environment configuration. The retained route code spans both hidden portal paths under `apps/web/app/routes/app.$tenant/__portals/*` and visible site-builder paths under `apps/web/app/routes/app.$tenant/sites/*`, while default core route discovery excludes those plugin trees. Extraction must preserve route ownership and user-visible navigation behavior if the plugin is enabled, or remove the retained surfaces atomically.
|
||||
Portals/Sites are coupled to tenant navigation, admin management, analytics reporting, domain resolution, billing provider flows, Prisma schema, and environment configuration. The retained route code spans both hidden portal paths under `apps/web/app/routes/app.$tenant/__portals/*` and visible site-builder paths under `apps/web/app/routes/app.$tenant/sites/*`, while default core route discovery excludes those plugin trees. Extraction must preserve route ownership and user-visible navigation behavior if the plugin is enabled, or remove the retained surfaces atomically.
|
||||
|
||||
Analytics portal filters and site page-view behavior must be explicitly preserved, redesigned, or removed during later implementation. Domains behavior in `apps/web/app/modules/domains/services/Domains.server.ts` must also be treated as part of the feature boundary because public site routing and domain lookup can become broken if the module is moved without corresponding domain configuration.
|
||||
|
||||
## Stripe Billing and Provider Boundary
|
||||
## Billing Provider Boundary
|
||||
|
||||
Portals/Sites include Stripe-specific behavior through `apps/web/app/modules/portals/services/PortalStripe.server.ts` and `apps/web/app/modules/portals/services/StripeConnect.server.ts`. Later implementation must preserve or explicitly decide Stripe Connect behavior, customer billing portal behavior, provider initialization, webhook expectations, environment variables, and failure handling before moving or removing any portal billing route.
|
||||
Portals/Sites include billing-provider behavior through the portal pricing and subscription persistence boundary. Later implementation must preserve or explicitly decide provider checkout behavior, customer billing portal behavior, provider initialization, webhook expectations, environment variables, and failure handling before moving or removing any portal billing route.
|
||||
|
||||
This report keeps Billing/Subscriptions Core separate from the Portals/Sites plugin candidate. Core Stripe subscription flows may remain in the boilerplate, while portal-specific Stripe Connect and customer portal behavior must be isolated behind a plugin/provider boundary if Portals/Sites are extracted.
|
||||
This report keeps Billing/Subscriptions Core separate from the Portals/Sites plugin candidate. Core subscription flows remain in HiveGrid, while portal-specific payment-connect and customer portal behavior must be isolated behind a plugin/provider boundary if Portals/Sites are extracted.
|
||||
|
||||
## Schema and Data Impact
|
||||
|
||||
@@ -59,10 +59,10 @@ Docs and command/playbook surfaces must point executors to this report before ru
|
||||
## Execution Plan
|
||||
|
||||
1. Land this report and a static verifier for required sections, exact decision token, D007 reference, D006 deferral, path references, manifest alignment, unresolved placeholders, and no runtime-change instructions in this slice.
|
||||
2. Audit dependencies across routes, modules, Stripe services, analytics, domains, environment examples, sidebar tests, Prisma schema, and docs/manifests.
|
||||
3. Implement route/module extraction or removal only after the dependency audit proves a safe order for `apps/web/app/modules/portals`, `apps/web/app/modules/sites`, `apps/web/app/routes/admin/portals.tsx`, `apps/web/app/routes/app.$tenant/__portals/*`, and `apps/web/app/routes/app.$tenant/sites/*`.
|
||||
2. Audit dependencies across routes, modules, billing provider services, analytics, domains, environment examples, sidebar tests, Prisma schema, and docs/manifests.
|
||||
3. Implement route/module extraction or removal only after the dependency audit proves a safe order for `apps/web/app/modules/portals`, `apps/web/app/modules/sites`, `apps/web/app/routes/app.$tenant/__portals/*`, and `apps/web/app/routes/app.$tenant/sites/*`.
|
||||
4. Create the schema/data migration plan for `prisma/schema/portals.prisma`, `prisma/schema/sites.prisma`, `prisma/schema/analytics.prisma`, and the module-owned DB files before moving persistence or deleting data models.
|
||||
5. Define the Stripe/env boundary for portal-specific Stripe Connect, customer billing portal behavior, dynamic site API keys, and `.env.example`, `.env.production.example`, `.env.fly.example` updates.
|
||||
5. Define the billing/env boundary for portal-specific Payment provider Connect, customer billing portal behavior, dynamic site API keys, and `.env.example`, `.env.production.example` updates.
|
||||
6. Align analytics, domains, sidebar, docs, inventory, and plugin manifest references so retained Core behavior remains coherent after extraction.
|
||||
7. Add or update focused tests and static scans that protect route coverage, manifest classification, schema/data expectations, provider boundaries, and placeholder-free documentation without browser or E2E execution in this documentation slice.
|
||||
|
||||
@@ -76,4 +76,4 @@ Task-level verification for this report is static: the file must be non-empty an
|
||||
|
||||
Missing any route, schema, provider, analytics, domains, environment, sidebar, inventory, or manifest surface would let a later implementation handle Portals/Sites incompletely. Reclassifying Portals/Sites as Core would conflict with D007, while immediate removal would conflict with the `extract-plugin` action and the D006 ownership deferral.
|
||||
|
||||
The highest implementation risk is partial extraction: moving routes without Stripe/customer portal decisions, deleting schema without data migration, or changing analytics/domains behavior without preserving public site expectations. Downstream work must therefore treat this report as the decision boundary and use static verification before runtime code changes.
|
||||
The highest implementation risk is partial extraction: moving routes without billing provider/customer portal decisions, deleting schema without data migration, or changing analytics/domains behavior without preserving public site expectations. Downstream work must therefore treat this report as the decision boundary and use static verification before runtime code changes.
|
||||
Reference in new issue
Block a user