@fui-org/fui-cli 2.1.4 → 2.2.1

package/skills/{fui-skill → fui}/references/project-config.md

@@ -1,303 +1,303 @@
-# Project Config — project.json & module set
-
-> Owns: **`project.json`: menu, menuLeft, navigation, domainSetting, `right`, relation to module `set`**.
-
-> Platform merge mechanism: [platform-architecture.md](platform-architecture.md) §2.1. This file is the **full property catalog** for project.json and `set`.
-
-> **Edit and push:** `project.json` is **file-driven** like `module.json`: `fui project sync` (pull latest) → edit `{projectId}/project.json` → `fui project publish-config [-p project]`. It takes no config arguments, so local never drifts from server. (`fui project update` edits project **metadata**, not runtime config.)
-
-## project.json ↔ module.json `set`
-
-At render `fastproject.js` merges **3 layers** (later overrides earlier), then the domain override:
-
-```
-$projectGroupSetting        (cấu hình nhóm project — thấp nhất)
-  ⤵ override bởi
-project.json (khối "data")
-  ⤵ override bởi
-module.json "set"           ← ưu tiên cao nhất
-  ⤵ cuối cùng override bởi
-domainSetting[domain hiện tại]   (nếu đang chạy trên domain đó)
-```
-
-Result: `vueData.v_Set` (read via `vueData.v_Set.*`). Module inherits all project config and may override any field. Normal pages **need no `set`**.
-
-### `v_Set` properties (project.json.data or module.set; used by `fastproject.js`)
-
-| Field             | Type             | Effect                                                                          |
-| ----------------- | ---------------- | ------------------------------------------------------------------------------- |
-| `title`           | string           | Page title (header bar)                                                         |
-| `apiDomain`       | string           | tAPI base URL — prepended to API paths without `http`                           |
-| `login`           | string           | Login page URL; runtime opens it on missing token / 401                         |
-| `userInfo`        | string           | User info endpoint → `vueData.user`; empty = no fetch                           |
-| `menu`            | `false` \| array | Horizontal header menu; `false` = hidden (48px tall when shown)                 |
-| `menuLeft`        | array            | Left sidebar menu                                                               |
-| `menuComponent`   | array            | Custom components in the menu area                                              |
-| `menuStyle`       | object           | Top/left menu colors                                                            |
-| `logo`            | string           | Header logo URL                                                                 |
-| `userProfile`     | object/string    | Header user profile block                                                       |
-| `themeStyle`      | object           | Passed to `new Vuetify(...)` — page Vuetify theme                               |
-| `disableValidate` | boolean          | `true` = skip form validation on submit                                         |
-| `authDomain`      | string           | Domain whose cookies `logout()` clears                                          |
-| `fileDomain`      | string           | File server base URL                                                            |
-| `domainSetting`   | object           | Per-domain config override (multi-domain)                                       |
-| `webSocket`       | object           | SignalR real-time group config ([websocket-realtime.md](websocket-realtime.md)) |
-
-Example — only this landing page hides the header menu:
-
-```json
-// module.json — set của trang đó
-"set": {
-  "menu": false
-}
-```
-
-## project.json structure
-
-`project.json` holds a single `data` object (not an array like module.json):
-
-```json
-{
-  "data": {
-    "ProjectName": "...",
-    "title":       "...",
-    "apiDomain":   "...",
-    "login":       "...",
-    "userInfo":    "...",
-    "apiFile":     "...",
-    "menuStyle":   { ... },
-    "menu":        false | [ ... ],
-    "menuLeft":    [ ... ],
-    "menuComponent": [ ... ],
-    "domainSetting": { ... }
-  }
-}
-```
-
-### `data` fields
-
-Same meaning as the `v_Set` table above, plus:
-
-| Field         | Type   | Description                                                                                    |
-| ------------- | ------ | ---------------------------------------------------------------------------------------------- |
-| `ProjectName` | string | Display name                                                                                   |
-| `title`       | string | Default page title                                                                             |
-| `logo`        | string | Menu bar logo URL, e.g. `"/images/fastUI_White.png"`                                           |
-| `apiDomain`   | string | tAPI base URL with apiName, e.g. `https://tapi.example2.vn/` or `https://tapi.example.vn/acc/` |
-| `userInfo`    | string | Public FUI: `"https://api.fui.vn/fp/userinfo"`                                                 |
-| `apiFile`     | string | File upload endpoint (optional)                                                                |
-| `fileDomain`  | string | File server base URL (optional)                                                                |
-
-## menuStyle
-
-Top and left menu colors:
-
-```json
-"menuStyle": {
-  "topmenu": {
-    "bgcolor":   "#217D46",
-    "textcolor": "white"
-  },
-  "leftmenu": {
-    "bgcolor":   "#217D46",
-    "textcolor": "white"
-  }
-}
-```
-
-## menu (top header)
-
-- `false` → header bar with menu fully hidden
-- Array → top bar menu items
-
-**Fixed height: 48px** when shown. Every "full screen" content height calc (`calc(100vh - Npx)`, `$(window).height() - N`, CSS `height: 100vh` on a container...) must also subtract 48px, or it overflows/scrolls:
-
-```css
-/* Có menu hiển thị */
-height: calc(100vh - 48px);
-
-/* menu: false → không trừ phần này */
-height: 100vh;
-```
-
-Applies to `module.json` (`:height` of `f-table`, `f-echart`...) and to CSS in `header.html`/components for `HTMLOnly=true` pages.
-
-## menuLeft (sidebar)
-
-Array of sidebar items. One item:
-
-```json
-{
-  "name": "Tên mục",
-  "icon": "mdi-folder-multiple",
-  "url":  "/duong-dan-module",
-  "submenu": [ ... ],
-  "right": {
-    "SystemRight":   [1, 2, 3, 5, 9],
-    "FunctionRight": ["10", "20"]
-  }
-}
-```
-
-### Menu item fields
-
-| Field     | Required | Description                                      |
-| --------- | -------- | ------------------------------------------------ |
-| `name`    | ✅       | Display name                                     |
-| `url`     | ❌       | Module path (omit for a group with submenu only) |
-| `icon`    | ❌       | Material Design icon (`mdi-*`)                   |
-| `submenu` | ❌       | Child items (same structure)                     |
-| `right`   | ❌       | Visibility by right — missing = visible to all   |
-
-### Menu visibility (`right`)
-
-> `SystemRight` (rank) vs `FunctionRight` (per-function) and managing right definitions: [permission-system.md](permission-system.md).
-
-```json
-"right": {
-  "SystemRight":   [1, 2, 5, 9],
-  "FunctionRight": ["10", "20"]
-}
-```
-
-- **`SystemRight`**: `user.SystemRight` (number) must be in the array
-- **`FunctionRight`**: `user.FunctionRight` (string array) must intersect the array (at least one code)
-- **`UserID`**: only listed `UserID`s see it — for internal/DEV menus
-- Multiple keys: user must satisfy **all** (`rightTest` checks each key's intersection with `vueData.user[key]`)
-- No `right` → visible to every logged-in user
-
-**Real example — DEV menu for a few UserIDs:**
-
-```json
-{
-  "name": "DEV",
-  "right": { "UserID": ["NV0000177", "NV0001078", "NV0000605"] },
-  "submenu": [{ "name": "Tra cứu lịch sử OTP", "url": "/hoso-sms-history" }]
-}
-```
-
-> Top menu parents usually have only `name` + `right` + `submenu` (no `url`); `url` sits on each `submenu` item.
-
-**Real example — menu for level-1 Team lead/BGH only:**
-
-```json
-{
-  "name": "Cấp 1 - Tổ trưởng",
-  "icon": "mdi-account-tie",
-  "right": {
-    "FunctionRight": ["10"],
-    "SystemRight":   [5, 9]
-  },
-  "submenu": [ ... ]
-}
-```
-
-→ Visible only if `FunctionRight` contains `"10"` AND `SystemRight` is 5 or 9.
-
-## menuComponent
-
-Custom Vue components embedded in the menu area (e.g. school-year or role dropdown):
-
-```json
-"menuComponent": [
-  { "el": "uc-nien-khoa" },
-  { "el": "uc-vaitro" }
-]
-```
-
-Components must be registered in the project's `components/_components.json`.
-
-## userProfile (header account block)
-
-Header-right avatar/account block:
-
-```json
-"userProfile": {
-  "color": "white",
-  "url-signout":          "https://app.example.vn/Signout",
-  "url-change-password":  "https://app.example.vn/ChangePassword",
-  "url-account":          "https://app.example.vn",
-  "url-avatar":           "https://file.example.vn/me/avatarOrigin/",
-  "url-app-list":         "https://tapi.example.vn/me/auth/ApplicationList"
-}
-```
-
-| Field                 | Meaning                             |
-| --------------------- | ----------------------------------- |
-| `color`               | Text/icon color                     |
-| `url-signout`         | Sign-out URL                        |
-| `url-change-password` | Change-password URL                 |
-| `url-account`         | Account page URL                    |
-| `url-avatar`          | Avatar base URL (`UserID` appended) |
-| `url-app-list`        | App list endpoint (app switcher)    |
-
-> `menuLeft: false` = no left sidebar (top menu only). `menuLeft: [ ... ]` = sidebar on.
-
-## domainSetting (multi-domain)
-
-Project on several domains (each with its own tAPI server and DB):
-
-```json
-"domainSetting": {
-  "sec.example.vn": {
-    "apiDomain":  "https://tapi.example.vn/acc/",
-    "fileDomain": "https://file.example.vn/acc/",
-    "login":      "https://app.example.vn",
-    "userInfo":   "https://tapi.example.vn/acc/UserInfo/acc"
-  },
-  "sec.example3.vn": {
-    "apiDomain":  "https://api.example3.vn/acc/",
-    "fileDomain": "https://file.example3.vn/acc/",
-    "login":      "https://login.example3.vn",
-    "userInfo":   "https://api.example3.vn/acc/UserInfo/acc"
-  }
-}
-```
-
-Key = hostname; runtime applies the current domain's override.
-
-## module.json `set` — per-page override
-
-`set` can override any project.json field. Common:
-
-```json
-"set": {
-  "title":    "Trang quản lý sinh viên",
-  "menu":     false,
-  "menuLeft": [ ... ]
-}
-```
-
-| Use `set` when                 | Example                                   |
-| ------------------------------ | ----------------------------------------- |
-| Page has its own title         | `"title": "Nhập điểm Tiểu học"`           |
-| Page hides header menu         | `"menu": false`                           |
-| Page needs a different sidebar | Override `"menuLeft"` with a shorter list |
-| Landing / public page          | `"menu": false, "menuLeft": []`           |
-
-**Do not repeat unchanged fields** — declare only what differs from the project default.
-
-## File relation summary
-
-```
-project.json.data          ← config mặc định cho toàn project
-    ↓ bị override bởi
-module.json.set             ← config riêng cho từng trang
-
-Effective config = merge(project.json.data, module.json.set)
-                   (module.set được ưu tiên)
-```
-
-## openWindow — URL parameter rule
-
-Pass in the `openWindow` URL **only the parent record ID** the child queries the DB with. Never pass names, labels or any field the child can look up.
-
-```json
-// ✅ Đúng — chỉ truyền ID cần thiết
-"url": "`/ContestDetail?ContestID={{sContestID}}"
-
-// ❌ Sai — truyền thừa field có thể tra từ DB
-"url": "`/ContestDetail?ContestID={{sContestID}}&ContestName={{sContestName}}"
-```
-
-Why: the child loads everything by ID; extra fields lengthen the URL, go stale, and couple the modules.
+# Project Config — project.json & module set
+
+> Owns: **`project.json`: menu, menuLeft, navigation, domainSetting, `right`, relation to module `set`**.
+
+> Platform merge mechanism: [platform-architecture.md](platform-architecture.md) §2.1. This file is the **full property catalog** for project.json and `set`.
+
+> **Edit and push:** `project.json` is **file-driven** like `module.json`: `fui project sync` (pull latest) → edit `{projectId}/project.json` → `fui project publish-config [-p project]`. It takes no config arguments, so local never drifts from server. (`fui project update` edits project **metadata**, not runtime config.)
+
+## project.json ↔ module.json `set`
+
+At render `fastproject.js` merges **3 layers** (later overrides earlier), then the domain override:
+
+```
+$projectGroupSetting        (cấu hình nhóm project — thấp nhất)
+  ⤵ override bởi
+project.json (khối "data")
+  ⤵ override bởi
+module.json "set"           ← ưu tiên cao nhất
+  ⤵ cuối cùng override bởi
+domainSetting[domain hiện tại]   (nếu đang chạy trên domain đó)
+```
+
+Result: `vueData.v_Set` (read via `vueData.v_Set.*`). Module inherits all project config and may override any field. Normal pages **need no `set`**.
+
+### `v_Set` properties (project.json.data or module.set; used by `fastproject.js`)
+
+| Field             | Type             | Effect                                                                          |
+| ----------------- | ---------------- | ------------------------------------------------------------------------------- |
+| `title`           | string           | Page title (header bar)                                                         |
+| `apiDomain`       | string           | tAPI base URL — prepended to API paths without `http`                           |
+| `login`           | string           | Login page URL; runtime opens it on missing token / 401                         |
+| `userInfo`        | string           | User info endpoint → `vueData.user`; empty = no fetch                           |
+| `menu`            | `false` \| array | Horizontal header menu; `false` = hidden (48px tall when shown)                 |
+| `menuLeft`        | array            | Left sidebar menu                                                               |
+| `menuComponent`   | array            | Custom components in the menu area                                              |
+| `menuStyle`       | object           | Top/left menu colors                                                            |
+| `logo`            | string           | Header logo URL                                                                 |
+| `userProfile`     | object/string    | Header user profile block                                                       |
+| `themeStyle`      | object           | Passed to `new Vuetify(...)` — page Vuetify theme                               |
+| `disableValidate` | boolean          | `true` = skip form validation on submit                                         |
+| `authDomain`      | string           | Domain whose cookies `logout()` clears                                          |
+| `fileDomain`      | string           | File server base URL                                                            |
+| `domainSetting`   | object           | Per-domain config override (multi-domain)                                       |
+| `webSocket`       | object           | SignalR real-time group config ([websocket-realtime.md](websocket-realtime.md)) |
+
+Example — only this landing page hides the header menu:
+
+```json
+// module.json — set của trang đó
+"set": {
+  "menu": false
+}
+```
+
+## project.json structure
+
+`project.json` holds a single `data` object (not an array like module.json):
+
+```json
+{
+  "data": {
+    "ProjectName": "...",
+    "title":       "...",
+    "apiDomain":   "...",
+    "login":       "...",
+    "userInfo":    "...",
+    "apiFile":     "...",
+    "menuStyle":   { ... },
+    "menu":        false | [ ... ],
+    "menuLeft":    [ ... ],
+    "menuComponent": [ ... ],
+    "domainSetting": { ... }
+  }
+}
+```
+
+### `data` fields
+
+Same meaning as the `v_Set` table above, plus:
+
+| Field         | Type   | Description                                                                                    |
+| ------------- | ------ | ---------------------------------------------------------------------------------------------- |
+| `ProjectName` | string | Display name                                                                                   |
+| `title`       | string | Default page title                                                                             |
+| `logo`        | string | Menu bar logo URL, e.g. `"/images/fastUI_White.png"`                                           |
+| `apiDomain`   | string | tAPI base URL with apiName, e.g. `https://tapi.example2.vn/` or `https://tapi.example.vn/acc/` |
+| `userInfo`    | string | Public FUI: `"https://api.fui.vn/fp/userinfo"`                                                 |
+| `apiFile`     | string | File upload endpoint (optional)                                                                |
+| `fileDomain`  | string | File server base URL (optional)                                                                |
+
+## menuStyle
+
+Top and left menu colors:
+
+```json
+"menuStyle": {
+  "topmenu": {
+    "bgcolor":   "#217D46",
+    "textcolor": "white"
+  },
+  "leftmenu": {
+    "bgcolor":   "#217D46",
+    "textcolor": "white"
+  }
+}
+```
+
+## menu (top header)
+
+- `false` → header bar with menu fully hidden
+- Array → top bar menu items
+
+**Fixed height: 48px** when shown. Every "full screen" content height calc (`calc(100vh - Npx)`, `$(window).height() - N`, CSS `height: 100vh` on a container...) must also subtract 48px, or it overflows/scrolls:
+
+```css
+/* Có menu hiển thị */
+height: calc(100vh - 48px);
+
+/* menu: false → không trừ phần này */
+height: 100vh;
+```
+
+Applies to `module.json` (`:height` of `f-table`, `f-echart`...) and to CSS in `header.html`/components for `HTMLOnly=true` pages.
+
+## menuLeft (sidebar)
+
+Array of sidebar items. One item:
+
+```json
+{
+  "name": "Tên mục",
+  "icon": "mdi-folder-multiple",
+  "url":  "/duong-dan-module",
+  "submenu": [ ... ],
+  "right": {
+    "SystemRight":   [1, 2, 3, 5, 9],
+    "FunctionRight": ["10", "20"]
+  }
+}
+```
+
+### Menu item fields
+
+| Field     | Required | Description                                      |
+| --------- | -------- | ------------------------------------------------ |
+| `name`    | ✅       | Display name                                     |
+| `url`     | ❌       | Module path (omit for a group with submenu only) |
+| `icon`    | ❌       | Material Design icon (`mdi-*`)                   |
+| `submenu` | ❌       | Child items (same structure)                     |
+| `right`   | ❌       | Visibility by right — missing = visible to all   |
+
+### Menu visibility (`right`)
+
+> `SystemRight` (rank) vs `FunctionRight` (per-function) and managing right definitions: [permission-system.md](permission-system.md).
+
+```json
+"right": {
+  "SystemRight":   [1, 2, 5, 9],
+  "FunctionRight": ["10", "20"]
+}
+```
+
+- **`SystemRight`**: `user.SystemRight` (number) must be in the array
+- **`FunctionRight`**: `user.FunctionRight` (string array) must intersect the array (at least one code)
+- **`UserID`**: only listed `UserID`s see it — for internal/DEV menus
+- Multiple keys: user must satisfy **all** (`rightTest` checks each key's intersection with `vueData.user[key]`)
+- No `right` → visible to every logged-in user
+
+**Real example — DEV menu for a few UserIDs:**
+
+```json
+{
+  "name": "DEV",
+  "right": { "UserID": ["NV0000177", "NV0001078", "NV0000605"] },
+  "submenu": [{ "name": "Tra cứu lịch sử OTP", "url": "/hoso-sms-history" }]
+}
+```
+
+> Top menu parents usually have only `name` + `right` + `submenu` (no `url`); `url` sits on each `submenu` item.
+
+**Real example — menu for level-1 Team lead/BGH only:**
+
+```json
+{
+  "name": "Cấp 1 - Tổ trưởng",
+  "icon": "mdi-account-tie",
+  "right": {
+    "FunctionRight": ["10"],
+    "SystemRight":   [5, 9]
+  },
+  "submenu": [ ... ]
+}
+```
+
+→ Visible only if `FunctionRight` contains `"10"` AND `SystemRight` is 5 or 9.
+
+## menuComponent
+
+Custom Vue components embedded in the menu area (e.g. school-year or role dropdown):
+
+```json
+"menuComponent": [
+  { "el": "uc-nien-khoa" },
+  { "el": "uc-vaitro" }
+]
+```
+
+Components must be registered in the project's `components/_components.json`.
+
+## userProfile (header account block)
+
+Header-right avatar/account block:
+
+```json
+"userProfile": {
+  "color": "white",
+  "url-signout":          "https://app.example.vn/Signout",
+  "url-change-password":  "https://app.example.vn/ChangePassword",
+  "url-account":          "https://app.example.vn",
+  "url-avatar":           "https://file.example.vn/me/avatarOrigin/",
+  "url-app-list":         "https://tapi.example.vn/me/auth/ApplicationList"
+}
+```
+
+| Field                 | Meaning                             |
+| --------------------- | ----------------------------------- |
+| `color`               | Text/icon color                     |
+| `url-signout`         | Sign-out URL                        |
+| `url-change-password` | Change-password URL                 |
+| `url-account`         | Account page URL                    |
+| `url-avatar`          | Avatar base URL (`UserID` appended) |
+| `url-app-list`        | App list endpoint (app switcher)    |
+
+> `menuLeft: false` = no left sidebar (top menu only). `menuLeft: [ ... ]` = sidebar on.
+
+## domainSetting (multi-domain)
+
+Project on several domains (each with its own tAPI server and DB):
+
+```json
+"domainSetting": {
+  "sec.example.vn": {
+    "apiDomain":  "https://tapi.example.vn/acc/",
+    "fileDomain": "https://file.example.vn/acc/",
+    "login":      "https://app.example.vn",
+    "userInfo":   "https://tapi.example.vn/acc/UserInfo/acc"
+  },
+  "sec.example3.vn": {
+    "apiDomain":  "https://api.example3.vn/acc/",
+    "fileDomain": "https://file.example3.vn/acc/",
+    "login":      "https://login.example3.vn",
+    "userInfo":   "https://api.example3.vn/acc/UserInfo/acc"
+  }
+}
+```
+
+Key = hostname; runtime applies the current domain's override.
+
+## module.json `set` — per-page override
+
+`set` can override any project.json field. Common:
+
+```json
+"set": {
+  "title":    "Trang quản lý sinh viên",
+  "menu":     false,
+  "menuLeft": [ ... ]
+}
+```
+
+| Use `set` when                 | Example                                   |
+| ------------------------------ | ----------------------------------------- |
+| Page has its own title         | `"title": "Nhập điểm Tiểu học"`           |
+| Page hides header menu         | `"menu": false`                           |
+| Page needs a different sidebar | Override `"menuLeft"` with a shorter list |
+| Landing / public page          | `"menu": false, "menuLeft": []`           |
+
+**Do not repeat unchanged fields** — declare only what differs from the project default.
+
+## File relation summary
+
+```
+project.json.data          ← config mặc định cho toàn project
+    ↓ bị override bởi
+module.json.set             ← config riêng cho từng trang
+
+Effective config = merge(project.json.data, module.json.set)
+                   (module.set được ưu tiên)
+```
+
+## openWindow — URL parameter rule
+
+Pass in the `openWindow` URL **only the parent record ID** the child queries the DB with. Never pass names, labels or any field the child can look up.
+
+```json
+// ✅ Đúng — chỉ truyền ID cần thiết
+"url": "`/ContestDetail?ContestID={{sContestID}}"
+
+// ❌ Sai — truyền thừa field có thể tra từ DB
+"url": "`/ContestDetail?ContestID={{sContestID}}&ContestName={{sContestName}}"
+```
+
+Why: the child loads everything by ID; extra fields lengthen the URL, go stale, and couple the modules.

package/skills/{fui-skill → fui}/references/project-provisioning.md

@@ -51,7 +51,7 @@ Begin
         RAISERROR(N'Bạn không có quyền tạo dự án', 16, 1)
 ```
 
-**No right ⇒ STOP, report, do nothing else.** Project goes before the DB because `INSERT INTO tblA_Project` needs only `ProjectID`/`ProjectName`/`GroupName`/`Framework`/`pDomain`/`Router` — no database. DB-first then rejection leaves a real DB, two SQL logins and an orphan `acc` record; fui hard-blocks `DROP DATABASE`, so cleanup is manual. `fui project new` _is_ the gate A check (no extra call); rejected ⇒ nothing created (if B was checked first).
+**No right ⇒ STOP, report, do nothing else.** Project goes before the DB because `INSERT INTO tblA_Project` needs only `ProjectID`/`ProjectName`/`GroupName`/`Framework`/`pDomain`/`Router` — no database. DB-first then rejection leaves a real DB, two SQL logins and an orphan `acc` record; never run `DROP DATABASE` (fui has no guard for it), so cleanup is the user's manual job. `fui project new` _is_ the gate A check (no extra call); rejected ⇒ nothing created (if B was checked first).
 
 | Operation                                             | SP                                                        | Condition                                  |
 | ----------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------ |
@@ -207,7 +207,7 @@ fui calls `SM_Modules_Update` **twice**: `UpdateConnection=0` creates the record
 
 - 🔴 **Credentials = Step 3 APP account, NEVER the dev account.** Dev account ⇒ every app API call runs as `db_owner`, with no visible error.
 - New `ModuleID` = `MAX(ModuleID)+1` over **all** `acc.tblModules` ⇒ needs an `acc` connection (`fui db add-by-name acc`). Can't use `fui db alias list`: it lists only modules **you** manage; MAX over a subset may collide.
-- Existing alias ⇒ hard error, no overwrite.
+- Existing alias ⇒ hard error, no overwrite. An explicit `--module-id` that is already in `acc.tblModules` (or used by an alias you manage) ⇒ hard error too; without an `acc` connection it can only be checked against the aliases you manage, and fui says so.
 
 Then `fui db add-by-name tenalias` works — [db-workflow.md](db-workflow.md) §2b.
 
@@ -223,7 +223,7 @@ Order is **mandatory**:
 3. fui user add DEV001 --right 3
 ```
 
-**`fui user add`/`set`/`remove` take only the exact `UserID`** — a structural identity gate: you must run `fui user search` and see `UserID | Username | Họ tên`. **Show that table and let the user pick before granting** — duplicate names are common; a wrong Admin grant can't be undone in one call.
+**`fui user add`/`set`/`remove` take only the exact `UserID`** — a structural identity gate: you must run `fui user search` and see its `userId`, `username`, `fullName` columns. **Show that table and let the user pick before granting** — duplicate names are common; a wrong Admin grant can't be undone in one call.
 
 | Level | Meaning                                                                                |
 | ----- | -------------------------------------------------------------------------------------- |
@@ -243,7 +243,7 @@ Order is **mandatory**:
 
 Step 6 ends **phase 1 only**: the project is empty, runtime config still SP-seeded empty strings, no tables/modules/right codes. Don't report "done"; don't jump into module.json.
 
-1. `fui project sync` + `fui use <projectId>` — pull into workspace, set as target.
+1. `fui project sync -p <projectId>`, then work from `{workspace}/<projectId>` (or pass `-p <projectId>`) — pulls the project into the workspace; `fui use` needs a module.
 2. **Runtime config (mandatory)**: edit `{projectId}/project.json` (`apiDomain` → new alias, `title`, `login`, `menu`), then `fui project publish-config` — [project-config.md](project-config.md). Skipped ⇒ the project can't call any API.
 3. `fui db add-by-name <apiName>` ([db-workflow.md](db-workflow.md) §2c) — also **proves** Steps 3 and 5 (app account + `acc` record OK).
 4. Resume [system-design.md](system-design.md) at **Step 1**, following the index.