Reorganize app workspaces and align Admin architecture

docs/core-modules/permission/backend.md

@@ -5,7 +5,7 @@ The backend Permission module exposes available permission definitions. It is us
 Source root:
 
 ```txt
-backend/app/base_modules/Permission/
+apps/backend/app/base_modules/Permission/
 ```
 
 ## Route
@@ -17,7 +17,7 @@ backend/app/base_modules/Permission/
 Route file:
 
 ```txt
-backend/app/base_modules/Permission/routes.ts
+apps/backend/app/base_modules/Permission/routes.ts
 ```
 
 ## Request Flow
@@ -36,14 +36,14 @@ GET /permission
 Permission discovery lives in:
 
 ```txt
-backend/app/services/permission_service.ts
+apps/backend/app/services/permission_service.ts
 ```
 
 `getAllPermissions()` scans:
 
 ```txt
-backend/app/base_modules/*/config/permissions.ts
-backend/app/modules/*/config/permissions.ts
+apps/backend/app/base_modules/*/config/permissions.ts
+apps/backend/app/modules/*/config/permissions.ts
 ```
 
 Each config exports permission items:
@@ -60,9 +60,9 @@ type PermissionItem = {
 Core permission definitions currently include:
 
 ```txt
-backend/app/base_modules/Admin/config/permissions.ts
-backend/app/base_modules/Role/config/permissions.ts
-backend/app/base_modules/FileManager/config/permissions.ts
+apps/backend/app/base_modules/Admin/config/permissions.ts
+apps/backend/app/base_modules/Role/config/permissions.ts
+apps/backend/app/base_modules/FileManager/config/permissions.ts
 ```
 
 When adding a feature that needs access control, add permission definitions to the owning backend module's `config/permissions.ts`.