@atlashub/smartstack-cli 4.81.0 → 5.0.0

package/templates/skills/application/references/backend-table-prefix-mapping.md

@@ -1,80 +0,0 @@
-# Backend: Table Prefix & Controller Folder Mapping
-
-> Referenced from `steps/step-04-backend.md` — Deriving table prefixes and controller organization.
-
----
-
-## Table Prefix Priority
-
-1. **If a `feature.json` exists** with `metadata.tablePrefix` → use that prefix (e.g., `rh_`, `fi_`)
-2. **Otherwise**, derive from navigation context using the fallback table below
-
----
-
-## Fallback Table (when no feature.json tablePrefix)
-
-| Application | Table Prefix | Controller Folder | Example |
-|---------|--------|-------------------|---------|
-| `administration.*` | `auth_` or `cfg_` | `Administration` | Table: `auth_Tenants`, Controller: `Controllers/Administration/TenantsController.cs` |
-| `support.*` | `support_` | `Support` | Table: `support_Tickets`, Controller: `Controllers/Support/TicketsController.cs` |
-| `*` (business apps) | `ref_` or domain-specific | `{ApplicationPascal}` | Table: `ref_Products`, Controller: `Controllers/Sales/ProductsController.cs` |
-| `myspace.*` | `usr_` | `MySpace` | Table: `usr_Preferences`, Controller: `Controllers/MySpace/PreferencesController.cs` |
-| `api.*` | `auth_` or `ext_` | `Api` | Table: `auth_ExternalApplications`, Controller: `Controllers/Platform/Api/ExternalApplications/` |
-
----
-
-## Feature.json Table Prefix Detection
-
-```
-Search for feature.json in:
-  - docs/business/{application}/business-analyse/*/feature.json
-  - Read metadata.tablePrefix if exists
-```
-
-**Example from feature.json:**
-
-```json
-{
-  "metadata": {
-    "tablePrefix": "rh_",
-    "schema": "core"
-  },
-  "analysis": { ... }
-}
-```
-
----
-
-## Implementation
-
-```csharp
-// Check for feature.json tablePrefix
-Search for feature.json in:
-  - docs/business/{application}/business-analyse/*/feature.json
-  - Read metadata.tablePrefix if exists
-
-IF metadata.tablePrefix exists:
-  {prefix} = metadata.tablePrefix   # e.g., "rh_"
-ELSE:
-  {prefix} = derived from context table above
-```
-
-Store: `{controller_folder}` = the Controller Folder from the table above.
-
----
-
-## Usage in MCP Call
-
-When calling `mcp__smartstack__scaffold_extension`:
-
-```
-Tool: mcp__smartstack__scaffold_extension
-Args:
-  type: "feature"
-  name: "{entityName}"
-  options:
-    navRoute: "{full_path}"
-    tablePrefix: "{prefix}"        ← Derived prefix
-    schema: "core"
-    ...
-```

package/templates/skills/application/references/backend-verification.md

@@ -1,88 +0,0 @@
-# Backend Post-Generation Verification
-
-**Run ALL checks before proceeding to next step.**
-
-## Check 1: Backend Build (BLOCKING)
-
-```bash
-dotnet build {SolutionName}.sln --no-restore
-```
-
-IF build fails: Read errors, fix compilation issues, re-run until success.
-
-## Check 2: DbSet Registration (BLOCKING)
-
-Search for `DbSet<{EntityName}>` in `I{DbContextName}.cs` or `{DbContextName}.cs`.
-
-IF NOT found, add:
-```csharp
-public DbSet<{EntityName}> {EntityName}s => Set<{EntityName}>();
-```
-
-## Check 3: DI Registration (BLOCKING)
-
-Search for `I{EntityName}Service` in `DependencyInjection.cs`.
-
-IF NOT found, add:
-```csharp
-services.AddScoped<I{EntityName}Service, {EntityName}Service>();
-```
-
-## Check 4: RequirePermission Attributes (BLOCKING)
-
-Each HTTP action MUST have `[RequirePermission(Permissions.{Application}.{Module}.{Action})]`.
-
-## Check 5: Entity Configuration (BLOCKING)
-
-Verify:
-- `builder.ToTable("{table_prefix}{EntityName}s")` uses correct prefix
-- `builder.HasKey(e => e.Id)` present
-- `builder.HasIndex` for unique fields
-
-## Check 5b: Seeding Infrastructure (first entity only)
-
-**If this is the FIRST entity (no existing DevDataSeeder):**
-
-1. **`Infrastructure/Persistence/Seeding/Data/SeedConstants.cs`**
-```csharp
-namespace {BaseNamespace}.Infrastructure.Persistence.Seeding.Data;
-public static class SeedConstants
-{
-    public static readonly DateTime SeedDate = new(2024, 1, 1, 0, 0, 0, DateTimeKind.Utc);
-}
-```
-
-2. **`Infrastructure/Persistence/Seeding/DevDataSeeder.cs`**
-```csharp
-public class DevDataSeeder : IDevDataSeeder
-{
-    private readonly ExtensionsDbContext _context;
-    private readonly ILogger<DevDataSeeder> _logger;
-    public DevDataSeeder(ExtensionsDbContext context, ILogger<DevDataSeeder> logger) { _context = context; _logger = logger; }
-    public async Task SeedAsync(CancellationToken cancellationToken = default)
-    {
-        _logger.LogInformation("Starting development data seeding...");
-        // Add Seed{Entity}sAsync calls here
-        _logger.LogInformation("Development data seeding complete.");
-    }
-}
-```
-
-3. Register: `services.AddScoped<IDevDataSeeder, DevDataSeeder>();`
-
-## Check 5c: SqlObjects Directory (first entity only)
-
-**If no existing SqlObjectHelper:**
-
-1. **`Infrastructure/Persistence/SqlObjects/SqlObjectHelper.cs`** - Helper for embedded SQL resources
-2. Create `Infrastructure/Persistence/SqlObjects/Functions/` directory
-3. Ensure `.csproj` has: `<EmbeddedResource Include="Persistence\SqlObjects\**\*.sql" />`
-
-## Check 6: Convention Validation (RECOMMENDED)
-
-```
-Tool: mcp__smartstack__validate_conventions
-Args: target: "backend", scope: "{entity_name}"
-```
-
-Verifies naming conventions, architecture layers, required attributes, DTO patterns.

package/templates/skills/application/references/contexts-cheatsheet.md

@@ -1,86 +0,0 @@
-# SmartStack Contexts — Cheatsheet
-
-> **Reference for `application` skill** — quick lookup of the 10 system contexts exposed by `<SmartStackProvider>`.
-
-## When This Reference Applies
-
-- You generate a component that needs to read auth/tenant/theme state
-- You audit a page that re-implements existing context state
-- The user asks "how do I read the current tenant", "how do I check a permission", "where is the SignalR connection"
-
----
-
-## The 10 contexts (state map)
-
-| # | Context | Hook | State exposed | Example use case |
-|---|---|---|---|---|
-| 1 | AuthContext | `useAuth()` | `user`, `roles`, `permissions`, `isAuthenticated`, `login()`, `logout()`, `refresh()`, `hasPermission(path)` | Read current user, check permission gate |
-| 2 | TenantContext | `useTenant()` | `currentTenant`, `userTenants`, `isGlobalView`, `switchTenant(id)` | Display tenant switcher, scope a query |
-| 3 | NavigationContext | `useNavigation()` | `menu` (MenuDto), `reload()`, `currentApp`, `currentModule`, `currentSection`, `isLoading`, `getApplicationsByZone()` (back-compat alias) | Render sidebar, breadcrumb, route resolution |
-| 4 | ThemeContext | `useTheme()` | `mode`, `selectedTheme`, `selectedPreset`, `setMode()`, `setTheme(id)`, `setPreset(id)` | Toggle dark mode, switch theme |
-| 5 | LicenseContext | `useLicense()` | `license`, `isFeatureEnabled(code)`, `hasModule(code)` | Gate a feature behind license |
-| 6 | SignalRContext | `useSignalR()` | `isConnected`, `on(event, handler)`, `off(event, handler)`, `emit(event, payload)` | Real-time notifications |
-| 7 | FavoritesContext | `useFavorites()` | `favorites`, `toggleFavorite(item)`, `isFavorite(id)` | Bookmark a page/entity |
-| 8 | SidebarContext | `useSidebar()` | `isCollapsed`, `toggle()`, `setCollapsed(value)` | Sidebar collapse button |
-| 9 | FeatureConfigContext | `useFeatureConfig()` | `features` (record from `/api/config/public`) | Feature flag, A/B test |
-| 10 | DocPanelContext | `useDocPanel()` | `isOpen`, `toggle()`, `openDoc(slug)` | Contextual help panel |
-
----
-
-## Common patterns
-
-### Permission check — render guard
-
-```tsx
-const { hasPermission } = useAuth();
-if (!hasPermission('administration.users.create')) return <Forbidden />;
-```
-
-### Tenant-scoped query
-
-```tsx
-const { currentTenant } = useTenant();
-const { data } = useQuery(
-  ['orders', currentTenant?.id],
-  () => orderApi.list({ tenantId: currentTenant?.id })
-);
-```
-
-### Real-time updates
-
-```tsx
-const { on, off } = useSignalR();
-useEffect(() => {
-  const handler = (notif) => toast(notif.message);
-  on('NotificationReceived', handler);
-  return () => off('NotificationReceived', handler);
-}, []);
-```
-
-### Feature flag
-
-```tsx
-const { isFeatureEnabled } = useLicense();
-if (isFeatureEnabled('ai-assistant')) return <AiAssistant />;
-```
-
----
-
-## DO / DON'T
-
-| ✅ DO | ❌ DON'T |
-|---|---|
-| Consume contexts via the provided hooks | `useContext(SmartStackContext)` directly |
-| Memoize derived values from context | Re-compute on every render |
-| Subscribe/unsubscribe SignalR handlers in `useEffect` cleanup | Forget to `off()` (memory leak) |
-| Treat `permissions` as opaque strings | Parse permissions client-side |
-| Read tenant from `currentTenant`, not URL | Trust the URL slug as a source of truth |
-
----
-
-## Reference source files (read-only)
-
-- `D:\01 - projets\SmartStack.app\features\IA-Workflow\web\smartstack-web\src\contexts\` (all 10 files)
-- `D:\01 - projets\SmartStack.app\features\IA-Workflow\web\smartstack-web\src\provider\SmartStackProvider.tsx` (wrapping order)
-
-See [smartstack-provider.md](smartstack-provider.md) for the wrapping order.

package/templates/skills/application/references/extensions-system.md

@@ -1,158 +0,0 @@
-# Extension System — Slot/Fill, Page Overrides, Hooks
-
-> **Reference for `application` skill** — how a client project enriches a SmartStack page without forking the SDK.
-
-## When This Reference Applies
-
-- Client wants to inject content into an existing SmartStack page (header action, table column, side panel)
-- Client wants to fully replace a built-in page with a custom one
-- Client needs to react to navigation/auth/tenant lifecycle events
-- The user asks "how do I add a column to UsersList", "how do I override the AdministrationDashboard page", "how do I customize a SmartStack form"
-
----
-
-## Three extension mechanisms
-
-### 1. Page overrides — `componentRegistry` + `PageRegistry`
-
-Override a built-in page by registering your component under the same key :
-
-```tsx
-// In your client componentRegistry.generated.ts (or a custom registry.ts)
-import { PageRegistry } from '@atlashub/smartstack';
-import { lazy } from 'react';
-
-PageRegistry.register(
-  'administration.users',                       // built-in key — replaces SmartStack page
-  lazy(() => import('@/pages/MyCustomUsers')),  // your component
-);
-
-// Or via SmartStackConfig.extensions.pages (declarative)
-const config: SmartStackConfig = {
-  apiUrl: '...',
-  extensions: {
-    pages: {
-      'administration.users': () => import('@/pages/MyCustomUsers'),
-    },
-  },
-};
-```
-
-The `DynamicRouter` calls `PageRegistry.resolve(componentKey)` and your override wins.
-
-> **Tip** — for net-new pages on client-defined routes, prefer the MCP tool `mcp__smartstack__scaffold_routes` to keep `componentRegistry.generated.ts` consistent.
-
-### 2. Slot / Fill — render-prop injection
-
-Inject content into a named slot exposed by a SmartStack page :
-
-```tsx
-import { Fill } from '@atlashub/smartstack';
-
-// Inject into the slot 'users.header.actions'
-<Fill slot="users.header.actions">
-  <button onClick={...}>My custom action</button>
-</Fill>
-```
-
-Available slot names follow the convention `{section}.{location}.{purpose}` (see `extensions/types.ts` SlotName union for the full list — examples : `users.header.actions`, `users.table.columns.before`, `users.table.row.actions`, `users.form.fields.after`, `users.detail.tabs.after`).
-
-You can declare slots once via `SmartStackConfig.extensions.slots` :
-
-```ts
-extensions: {
-  slots: {
-    'users.header.actions': MyHeaderWidget,
-    'dashboard.kpi.before': MyKpi,
-  }
-}
-```
-
-### 3. Lifecycle hooks
-
-Subscribe to platform events from anywhere :
-
-```ts
-extensions: {
-  hooks: {
-    onAuthSuccess: (user) => analytics.identify(user.id),
-    onTenantSwitch: (tenant) => router.navigate('/dashboard'),
-    onNavigationChanged: (menu) => console.log('menu refreshed'),
-  }
-}
-```
-
----
-
-## Table columns & form fields extensions
-
-Extend the standard `DataTable` or `EntityForm` of any built-in section :
-
-```ts
-extensions: {
-  tableColumns: {
-    'administration.users.list': [
-      {
-        key: 'department',
-        label: 'Department',
-        render: (row) => row.department?.name,
-        align: 'left',
-        sortable: true,
-      },
-    ],
-  },
-  formFields: {
-    'administration.users.create': [
-      {
-        name: 'department',
-        type: 'select',
-        label: 'Department',
-        options: () => departmentApi.list(),
-        validation: { required: true },
-      },
-    ],
-  },
-}
-```
-
-These extensions are consumed by the corresponding hooks in the SmartStack page :
-
-```tsx
-const extraColumns = useTableColumnExtensions('administration.users.list');
-const extraFields = useFormFieldExtensions('administration.users.create');
-```
-
----
-
-## DO / DON'T
-
-| ✅ DO | ❌ DON'T |
-|---|---|
-| Use `PageRegistry.register()` once at startup | Register the same key twice (last wins, but ambiguous) |
-| Use lazy imports for page overrides | Import override pages eagerly (kills code splitting) |
-| Match exact componentKey from the navigation menu | Guess the key — read it from `/api/navigation/menu` response |
-| Use slots for additive content | Use slots to remove content (use page override instead) |
-| Type custom column data via `row` typing | Cast `row as any` |
-
----
-
-## MCP delegation
-
-For complex extension scaffolds (page override + slots + tests), prefer the MCP tool over hand-written code :
-
-| Goal | MCP tool |
-|---|---|
-| Generate a page override + register it | `mcp__smartstack__scaffold_frontend_extension` (type: `page-override`) |
-| Generate a custom Slot component | `mcp__smartstack__scaffold_frontend_extension` (type: `slot`) |
-| Generate a custom column extension | `mcp__smartstack__scaffold_frontend_extension` (type: `table-column`) |
-
----
-
-## Reference source files (read-only)
-
-- `D:\01 - projets\SmartStack.app\features\IA-Workflow\web\smartstack-web\src\extensions\PageRegistry.tsx`
-- `D:\01 - projets\SmartStack.app\features\IA-Workflow\web\smartstack-web\src\extensions\types.ts` (SlotName, ColumnExtension, FormFieldExtension)
-- `D:\01 - projets\SmartStack.app\features\IA-Workflow\web\smartstack-web\src\extensions\ExtensionContext.tsx` (useExtensions, useTableColumnExtensions, useFormFieldExtensions)
-- `D:\01 - projets\SmartStack.app\features\IA-Workflow\web\smartstack-web\src\extensions\SlotFill.tsx` (Slot, Fill, SlotFillProvider)
-
-See also [smartstack-provider.md](smartstack-provider.md) for the SmartStackConfig shape that hosts `extensions`.

package/templates/skills/application/references/frontend-i18n-and-output.md

@@ -1,67 +0,0 @@
-# Frontend: i18n Structure & Output Formatting
-
-> Referenced from `steps/step-05-frontend.md` — i18n files and output presentation.
-
----
-
-## i18n Structure
-
-All i18n files must follow this structure:
-
-```
-locales/
-├── fr/
-│   └── {entityCode}.json
-├── en/
-│   └── {entityCode}.json
-├── it/
-│   └── {entityCode}.json
-└── de/
-    └── {entityCode}.json
-```
-
-**Note:** i18n files are auto-generated by `type: "page"` scaffold. Verify the 4 language files were created and customize the `title`/`subtitle` with proper labels.
-
-If customization needed:
-- `i18n/locales/fr/{entityCode}.json` → set `"title": "{labels.fr}"`
-- `i18n/locales/en/{entityCode}.json` → set `"title": "{labels.en}"`
-- `i18n/locales/it/{entityCode}.json` → set `"title": "{labels.it}"`
-- `i18n/locales/de/{entityCode}.json` → set `"title": "{labels.de}"`
-
----
-
-## Presenting Output to User
-
-Display generated frontend code organized by category:
-
-### Pages
-- `pages/{application}/{module}/{EntityName}Page.tsx`
-- `pages/{application}/{module}/{EntityName}ListView.tsx`
-
-### Components
-- `components/{application}/{module}/{EntityName}.tsx`
-- `hooks/use{EntityName}.ts`
-
-### API Client
-- `services/api/{entityCode}Api.ts`
-- `types/{entityName}.types.ts`
-
-### Routes
-- Updated `navRoutes.generated.ts`
-- Generated `componentRegistry.generated.ts` (PageRegistry registrations)
-- Navigation seed data has matching componentKeys
-
-### i18n
-- `locales/fr/{entityCode}.json`
-- `locales/en/{entityCode}.json`
-- `locales/it/{entityCode}.json`
-- `locales/de/{entityCode}.json`
-
-### Route Configuration Example
-```tsx
-// In routes.tsx - NESTED routes (not flat!)
-<Route path="{application_kebab}">
-  <Route index element={<Navigate to="{module_kebab}" replace />} />
-  <Route path="{module_kebab}" element={<{EntityName}Page />} />
-</Route>
-```

package/templates/skills/application/references/frontend-route-naming.md

@@ -1,123 +0,0 @@
-# Frontend: Route Naming & Kebab-Case Requirements
-
-> Referenced from `steps/step-05-frontend.md` — Route path conventions and naming rules.
-
----
-
-## Route Naming Rule (BLOCKING)
-
-All route paths MUST use **kebab-case** to match navigation seed data exactly.
-
-**Transformation:** `PascalCase` → `kebab-case`
-
-Examples:
-- `HumanResources` → `human-resources`
-- `Employees` → `employees`
-- `TimeManagement` → `time-management`
-- `OrderItems` → `order-items`
-
----
-
-## Forbidden Patterns
-
-| Pattern | Issue |
-|---------|-------|
-| `humanresources` | Concatenated words without hyphens |
-| `timemanagement` | Missing hyphens in multi-word names |
-| `mymodule` | Ambiguous (is this "my-module" or literal "mymodule"?) |
-
----
-
-## Required Patterns
-
-| Pattern | Correct Usage |
-|---------|---------------|
-| `human-resources` | Multi-word segment with proper hyphens |
-| `time-management` | Proper kebab-case |
-| `employees` | Single-word segments stay lowercase |
-| `products` | Single-word segments stay lowercase |
-
----
-
-## Verification
-
-Route paths MUST match the navigation seed data routes (which use `ToKebabCase()`).
-
-**Example verification:**
-
-Navigation seed data:
-```csharp
-Route = "/human-resources/time-management"  // From ToKebabCase()
-```
-
-PageRegistry keys and seed data ComponentKeys must use kebab-case:
-```tsx
-// v3.7+ (DynamicRouter): componentKey uses dot-separated kebab-case
-PageRegistry.register('human-resources.time-management', lazy(() => ...));
-
-// Legacy (applicationRoutes): paths use kebab-case
-const applicationRoutes: ApplicationRouteExtensions = {
-  'human-resources': [  // ← kebab-case
-    { path: 'time-management', element: <TimeManagementPage /> },  // ← kebab-case
-  ],
-};
-```
-
----
-
-## Kebab-Case Conversion Rules
-
-| Input | Output | Rule |
-|-------|--------|------|
-| `ProductCode` | `product-code` | Insert `-` before uppercase letters |
-| `Product` | `product` | Lowercase single words |
-| `IDs` | `ids` | Lowercase acronyms |
-| `HTTPSConnection` | `https-connection` | Insert `-` before each uppercase cluster transition |
-| `CamelCaseExample` | `camel-case-example` | Insert `-` at each camelCase boundary |
-
----
-
-## Implementation Pattern
-
-> **v3.46+ note** — The domain-specific layouts `AdminLayout`, `BusinessLayout`, `UserLayout`, `HRLayout`, `SalesLayout` are REMOVED. `AppLayout` is now the SOLE shell for authenticated application routes. Routes are resolved dynamically by `DynamicRouter` via `componentRegistry.generated.ts` — the JSX `<Route>` blocks below are illustrative for naming convention only, not for manual declaration. See `references/smartstack-provider.md` for the full provider/router setup.
-
-When generating routes, apply kebab-case to all multi-word segments:
-
-```tsx
-// CORRECT — kebab-case convention (illustrative — actual routes flow through DynamicRouter)
-<Route path="/human-resources" element={<AppLayout />}>
-  <Route path="employees" element={<EmployeesPage />} />
-  <Route path="time-management" element={<TimeManagementPage />} />
-</Route>
-
-// FORBIDDEN
-<Route path="/humanresources" element={<AppLayout />} />
-<Route path="/HR" element={<AppLayout />} />
-<Route path="/human_resources" element={<AppLayout />} />
-```
-
----
-
-## Cross-Reference with Navigation Seeds
-
-Before finalizing route paths, verify they match navigation seeds:
-
-**Step 1:** Extract application code from `{full_path}` (e.g., `human-resources.time-management` → app: `human-resources`)
-
-**Step 2:** Check existing navigation seeds:
-```bash
-Glob: **/Seeding/Data/Navigation/NavigationApplicationSeedData.cs
-Search for: Route = "/{application_kebab}"
-```
-
-**Step 3:** Ensure App.tsx routes use the exact same kebab-case format.
-
----
-
-## Validation Checklist
-
-- [ ] All multi-word segments use hyphens (kebab-case)
-- [ ] Single-word segments are lowercase
-- [ ] Route paths match navigation seed data routes
-- [ ] No uppercase letters in route paths
-- [ ] No underscores (`_`) or camelCase in paths

package/templates/skills/application/references/frontend-route-wiring-app-tsx.md

@@ -1,91 +0,0 @@
-# Frontend: Route Registration with PageRegistry + DynamicRouter
-
-> **v3.7+** — Replaces the legacy Pattern A (mergeRoutes) and Pattern B (JSX routes) patterns.
-
----
-
-## How It Works
-
-1. **Backend seed data** defines navigation entries with `ComponentKey` values
-   (e.g., `administration.users`, `support.tickets.list`)
-2. **`componentRegistry.generated.ts`** registers all page components into `PageRegistry`
-   via `PageRegistry.register('key', lazy(() => import(...)))`
-3. **DynamicRouter** fetches the menu API, matches each entry's `componentKey` to a
-   `PageRegistry` entry, and generates `<Route>` elements at runtime
-4. **Implicit routes** (detail, create, edit) are resolved by convention:
-   - `*.detail` → `.../:id`
-   - `*.create` → `.../create`
-   - `*.edit` → `.../:id/edit`
-
-No manual App.tsx wiring is needed.
-
----
-
-## For SmartStack Core Pages
-
-`componentRegistry.generated.ts` is auto-generated by MCP `scaffold_routes`:
-
-```tsx
-// Auto-generated — DO NOT EDIT
-import { lazy } from 'react';
-import { PageRegistry } from '@/extensions/PageRegistry';
-
-PageRegistry.register('administration.users', lazy(() =>
-  import('@/pages/platform/administration/users/UsersPage').then(m => ({ default: m.UsersPage }))
-));
-PageRegistry.register('administration.users.detail', lazy(() =>
-  import('@/pages/platform/administration/users/UserDetailPage').then(m => ({ default: m.UserDetailPage }))
-));
-// ... ~100 registrations
-```
-
-Imported once in `main.tsx`:
-```tsx
-import './extensions/componentRegistry.generated';
-```
-
----
-
-## For Client SDK Pages
-
-> **CRITICAL:** Keys use DOT notation (`rh.employes.list`), NEVER hyphens (`rh-employes-list`).
-> Dots are hierarchy separators matching `NavigationService.ComponentKey` computation at runtime.
-
-Clients register their own pages directly:
-
-```tsx
-import { PageRegistry } from '@atlashub/smartstack';
-import { lazy } from 'react';
-
-PageRegistry.register('rh.time.dashboard', lazy(() => import('./pages/TimeDashboard')));
-PageRegistry.register('rh.time.list', lazy(() => import('./pages/TimeList')));
-PageRegistry.register('rh.time.detail', lazy(() => import('./pages/TimeDetail')));
-```
-
-Navigation entries are created in DB (via admin UI or seed data).
-DynamicRouter does the junction automatically.
-
----
-
-## Verification
-
-```
-Tool: mcp__smartstack__validate_frontend_routes
-Args:
-  scope: "routes"
-```
-
-Checks:
-- `componentRegistry.generated.ts` exists
-- Each backend NavRoute has a `PageRegistry.register()` call
-- `main.tsx` imports the generated file
-- Implicit route keys (*.detail, *.create, *.edit) exist for CRUD pages
-
----
-
-## Legacy Patterns (DEPRECATED)
-
-> The Pattern A (`mergeRoutes(clientRoutes, applicationRoutes)`) and Pattern B
-> (JSX `<Route>` in App.tsx) patterns are deprecated since v3.7.
-> They still work but are not recommended for new development.
-> See git history for the legacy documentation.