@fui-org/fui-cli 1.3.1 → 2.0.0

package/skills/fui-skill-cli/references/controls-styling-vocabulary.md

@@ -1,137 +0,0 @@
-# Controls Styling — Approved Layout Vocabulary (use only this)
-
-> Owns: **approved class/prop/style set for `controls` and `.vue`, and presentation priority order**. Aesthetic mode + `border-radius` limits: [design-modes.md](design-modes.md).
-
-**Rule #1: do NOT add `style` or `class` to "beautify" UI.** Use only the vocabulary below (extracted from 78 real `module.json` files across 5 projects: contest-score, security-manager, fp, lhu-test, lhu-lib). If the user didn't ask for a specific effect/spacing/color → **add nothing**. FUI layout (grid + Vuetify + project theme) is already consistent.
-
-> Stats: of 1,284 control objects only ~12% use `attr.style` (almost only for `width`), and **zero custom classes** — 100% standard Vuetify utilities. Common AI mistake: adding `style="padding/margin/border/box-shadow/border-radius/background"` and invented classes → **don't.**
-
----
-
-## Principles
-
-1. **Default: no style, no class.** Set only `el`, `attr` (v-model/label/:items/:action…), `w`, and `col` when splitting columns.
-2. Spacing/alignment → **Vuetify utility classes** from the tables below, NOT `style`.
-3. `style` only for **fixed `width`** of a filter field (`style: "width:200px"`) — never padding/margin/border/color/background.
-4. Color: component prop (`color="primary"`) or class `primary--text`/`error--text` — no `style="color:#..."`.
-5. **Never** add `border`, `border-radius`, `box-shadow`, `background`, `padding`, custom classes unless the user explicitly asks.
-6. **Compact padding — default `pa-2`** (or `pa-1`/`pa-0`). **NO large padding** (`pa-4`, `pa-6`, `pa-8`...) — wastes screen space. Margin likewise: prefer `-1`/`-2`, avoid `-6`/`-8`.
-7. **When the user _does_ ask for specific presentation — follow this priority**, moving down only when the previous level can't do it:
-   `component prop` (`color`, `outlined`, `dense`, `elevation`) → `Vuetify utility class` (`pa-*`, `ma-*`, `d-flex`, `text-*`, `primary--text`) → `mw-*` for width → custom class → inline `style` (**last**).
-
----
-
-## 1. Container / row `prop` (grid wrapper)
-
-Outer container and each row use only these tokens (by real frequency):
-
-| Token                                            | Purpose                                                               | Frequency |
-| ------------------------------------------------ | --------------------------------------------------------------------- | --------- |
-| `grid-list-md`                                   | Standard column gap (container)                                       | very high |
-| `fluid`                                          | Full-width container                                                  | high      |
-| `row`                                            | Marks a row                                                           | very high |
-| `align-center`                                   | **Vertically center** controls in a row, esp. different types/heights | high      |
-| `justify-center`                                 | Horizontal centering                                                  | very high |
-| `justify-left` / `justify-end` / `justify-start` | Left / right align                                                    | medium    |
-| `text-center` / `text-left`                      | Text align                                                            | medium    |
-| `mw-800` `mw-1000` `mw-1200` `mw-1400`           | **Limit content width** (FUI class) — centered form/data-entry pages  | medium    |
-| `hidden-container`                               | Wraps dialogs (v-dialog/f-dialog) — takes no layout space             | dialogs   |
-| `grid-list-lg`                                   | Wider gap than grid-list-md                                           | low       |
-| `pa-0` / `py-0`                                  | Remove container padding to touch edges                               | low       |
-| `page-container` / `page-navigation`             | Sticky filter-bar layout (see ui-layout-patterns.md)                  | rare      |
-
-> **Default formula**: container `"fluid grid-list-md"`, each row `"row"`. Rows mixing control types/heights: `"row wrap align-center"` for a shared vertical axis; `justify-center` is horizontal only. Form pages: add `mw-1000`/`mw-1200`.
-
-## 2. `col` (grid column wrapping a control)
-
-`col` only for width splitting or aligning/shrinking the column:
-
-| Token                                     | Purpose                                                                                                                                                   |
-| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `shrink`                                  | **Fixed-width filter field** (doesn't grow) — most common. **Required whenever `w` is px**; write `"class": "shrink"`, NOT `"shrink": true` (inert on V3) |
-| `text-end` / `text-start` / `text-center` | Align content in column                                                                                                                                   |
-| `pa-0`                                    | Remove column padding                                                                                                                                     |
-| `align-self-center`                       | Vertical centering                                                                                                                                        |
-
-Short string `"text-end"` or object `{ "class": "shrink" }`. Add `"v-if": "..."` to `col` to show/hide the whole column by right/condition.
-
-> Prefer `align-center` on the row to align the whole row. Use `align-self-center` on `col` only when a single control needs fixing. Never compensate vertical offset with margin or inline style.
-
-## 3. `attr.class` (on the control itself)
-
-Vuetify utility classes only:
-
-| Group                 | Tokens                                                                                                                                                                        |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Margin                | `mt-1 mt-2 mt-3` · `mb-1 mb-2 mb-4` · `my-2` · `ml-1 ml-2` · `mr-1 mr-2`                                                                                                      |
-| Padding               | `pa-0 pa-2` · `pt-3` · `py-1` — **avoid `pa-4/6/8`**                                                                                                                          |
-| Flex                  | `d-flex` · `flex-column` · `align-center` · `justify-center` · `justify-end` · `flex-grow-0` · `flex-wrap` · `flex-md-grow-0`                                                 |
-| Text                  | `text-center` · `text-left` · `text-right`                                                                                                                                    |
-| Size / weight         | `text-h6` · `subtitle-1` · `body-2` · `caption` · `font-weight-bold` · `font-weight-medium`                                                                                   |
-| Text color (V2)       | `primary--text` · `error--text` · `grey--text` · `white--text` — **FUI V2 (Vuetify 1.5) only** (`--text` suffix)                                                              |
-| Text color (V3)       | `text-primary` · `text-error` · `text-grey` · `text-white` — **Vuetify 3** `text-{color}`. Wrong version = no effect, no error                                                |
-| Background            | prop `color="primary"`, or Vuetify bg classes `primary` · `grey lighten-4`                                                                                                    |
-| Rounding              | `rounded` · `rounded-lg` · `rounded-0`                                                                                                                                        |
-| Shadow / flat         | prop `elevation="0"` / `flat` / `outlined` on `v-card`/`v-btn`                                                                                                                |
-| Breakpoint visibility | `d-none d-md-flex`...                                                                                                                                                         |
-| Size                  | component props (`max-width`, `width`, `dense`, `small`, `x-large`) — no `style="width:..."` unless fixed px needed. Icons: keep default size, **don't add `small`/`:small`** |
-
-### Icon size
-
-- Icons use the component/theme default size.
-- **Don't set `small` or `:small`** on `v-icon`, icon buttons, or buttons with icons just to look "compact".
-- Shrink only when the user explicitly asks or a specialised component/pattern prescribes it; then set the prop on exactly that component — don't shrink the whole button unintentionally.
-
-**Before adding a class → check the table above.** Define a custom class only for what Vuetify lacks: complex grid-template, animation, pseudo-element (`::before`), specific child selectors. Put it in `header.html`, clearly prefixed, **minimal count** — don't recreate card/badge/spacing Vuetify already has.
-
-> `flex-md-grow-0` + `col: { class: "shrink" }` + `style: "width:200px"` = **fixed-width filter field** — standard toolbar pattern ([ui-patterns.md](ui-patterns.md) §4). The only valid place for `style` (width only).
-
----
-
-## 4. Width: `w` (NOT style/class)
-
-| `w`                  | Meaning                                                                                |
-| -------------------- | -------------------------------------------------------------------------------------- |
-| `1`–`12`             | Grid columns (12 = full row)                                                           |
-| `>= 25` (e.g. `250`) | Fixed px width — **requires `col: { "class": "shrink" }`**, otherwise px has no effect |
-| `13`–`24`            | **Don't use** — dead zone: V2 yields px, V3 yields a non-existent class                |
-| `""` (empty)         | Size to content                                                                        |
-
-Always split columns with `w` — no `style="width:..%"`, no invented `col-6`.
-
-Measurements and reasons: [controls-patterns.md](controls-patterns.md) §Pixel `w`.
-
----
-
-## 5. RIGHT / WRONG
-
-```json
-// ✅ ĐÚNG — gọn, dùng w + prop chuẩn, không style thừa
-{ "el": "v-text-field", "w": 6, "attr": { "v-model": "hoTen", "label": "Họ tên" } }
-
-// ❌ SAI — style/class tự chế không cần thiết
-{ "el": "v-text-field", "w": 6, "attr": {
-    "v-model": "hoTen", "label": "Họ tên",
-    "style": "padding:8px; border:1px solid #ddd; border-radius:8px; margin-bottom:12px",
-    "class": "my-custom-input rounded-lg shadow" } }
-```
-
-```json
-// ✅ ĐÚNG — card mặc định của Vuetify, không tự style
-{ "el": "v-card", "attr": { "class": "pa-2" }, "innerHTML": [ ... ] }
-
-// ❌ SAI — tự vẽ lại card
-{ "el": "v-card", "attr": { "style": "background:#fff; box-shadow:0 4px 12px rgba(0,0,0,.1); border-radius:16px; padding:24px" } }
-```
-
----
-
-## 6. When style/class IS allowed
-
-Only when the user **explicitly requests** specific presentation (e.g. "grey background for this block", "limit width to 800px", "this text red"). Even then:
-
-- Prop → Vuetify utility class → `mw-*` for width → `style` last.
-- `border-radius` on request: obey limits in [design-modes.md](design-modes.md) (large frame ≤12px, medium ≤8px, small ≤6px).
-- No `<style>` in `.vue`; CSS goes in `header.html`.
-
-> **About to type `style` or name a new class → stop and ask "did the user request this?". If not → drop it.**

package/skills/fui-skill-cli/references/db-table-design.md

@@ -1,73 +0,0 @@
-# Table Design Conventions
-
-> Owns: **table design rules: naming, PK/FK, audit columns, data types**. Connection/SP workflow: [db-workflow.md](db-workflow.md). Load when designing a new schema.
-
-> **DDL — structure changes OK, data loss not:** `ALTER TABLE ... ADD` (column/constraint) and `DROP CONSTRAINT` run directly via fui. `ALTER COLUMN` (type change) runs but **needs `--confirm-write`** — narrowing numeric/time precision silently loses data. `CREATE TABLE`, `DROP COLUMN`, `DROP TABLE` are **hard-blocked**; the developer runs them. Conventions below are documentation — present DDL to the user for approval before running.
->
-> DB connection, dbToken, schema, SP workflow: [db-workflow.md](db-workflow.md). Multi-table/multi-module app design: [system-design.md](system-design.md).
-
----
-
-## Table names
-
-| Group                            | Rule                      | Example                                    |
-| -------------------------------- | ------------------------- | ------------------------------------------ |
-| System / auxiliary lookup tables | Lowercase, no prefix      | `syslog`, `syslogtype`, `syspermission`    |
-| Business / main entity tables    | `tbl` prefix + PascalCase | `tblUsers`, `tblDepartments`, `tblSession` |
-
-**Primary key:** `[EntityName]ID`
-
-| Table            | PK             |
-| ---------------- | -------------- |
-| `tblUsers`       | `UserID`       |
-| `tblDepartments` | `DepartmentID` |
-| `tblSession`     | `SessionID`    |
-
-> FK in a child table uses the same name as the parent PK — `UserID`, never `CreatorID` or `OwnerID`.
-
----
-
-## Timestamp columns
-
-Every table should have at least one timestamp:
-
-```sql
-[CreateTime]  [datetime]  DEFAULT (getdate())
-[UpdateTime]  [datetime]  DEFAULT (getdate())
-```
-
-- Type `datetime`; `DEFAULT (getdate())` — SQL Server **fills it** on INSERT, no need to pass from code.
-- `CreateTime` for write-once tables; `UpdateTime` for frequently updated ones; both when created vs last-modified must differ.
-
----
-
-## User tracking columns
-
-```sql
-[CreateUser]  [char](9)  NULL
-[UpdateUser]  [char](9)  NULL
-```
-
-- Type `char(9)` or `varchar(20)` — **match the type of `UserID` in `tblUsers`**.
-- **No DEFAULT** — the app must pass the logged-in `UserID`. SQL Server can't know the FUI/tAPI user; code is responsible.
-- In SPs: receive via `@sys_UserID` (tAPI auto-injects), store into `[CreateUser]` / `[UpdateUser]`.
-
-```sql
-CREATE PROCEDURE spAPI_EntityInsert
-    @Name        nvarchar(100),
-    @sys_UserID  int              -- tAPI auto-inject UserID
-AS
-    INSERT INTO tblEntity (Name, CreateUser, CreateTime)
-    VALUES (@Name, @sys_UserID, DEFAULT)
-```
-
----
-
-## Audit column template — paste into new tables
-
-```sql
-[CreateUser]  [char](9)   NULL,
-[CreateTime]  [datetime]  DEFAULT (getdate()),
-[UpdateUser]  [char](9)   NULL,
-[UpdateTime]  [datetime]  DEFAULT (getdate()),
-```

package/skills/fui-skill-cli/references/db-workflow.md

@@ -1,288 +0,0 @@
-# DB Connection Workflow
-
-> Owns: DB connections, dbToken, schema cache, SP workflow, rollback. Per-command risk/guards: [tools-registry.md](tools-registry.md); SP checklist: [verification.md](verification.md). Flags: `fui <command> --help`.
-
-## 1. Storage layout
-
-One `_db/` subfolder PER connection; a project may call several DBs, each via its alias (`apiName`):
-
-```
-{FUI_MCP_WORKDIR}/{projectId}/
-└── _db/
-    ├── _connections.json      ← all connections + default
-    ├── rights.json            ← rights cache from "acc", keyed by alias
-    ├── {alias}/               ← alias = apiName = first segment of "API": "/{alias}/Ten"
-    │   ├── schema.json        ← schema cache
-    │   └── {name}.sql         ← SPs (NO "sp/" level)
-    └── {other-alias}/…
-```
-
-- Alias links everything: `"API": "/fee/HocPhi_Select"` → apiName `fee` → `_db/fee/`.
-- Every DB command takes `--db <alias>` or `--db <project>/<alias>`. Omitted → inferred from the object; if not inferable, fui returns a MENU of aliases — pick one, re-run. Never guess.
-- Overwritten/deleted files go to `{FUI_MCP_WORKDIR}/_history/`, same path shape; all versions of a file sit together. Never auto-cleaned (user deletes manually):
-
-```
-{FUI_MCP_WORKDIR}/_history/{projectId}/_db/{alias}/{name}_{timestamp}.sql
-{FUI_MCP_WORKDIR}/_history/{projectId}/_db/{alias}/{name}_{timestamp}_deleted.sql   ← DROPped SP
-```
-
-`_db/_connections.json`:
-
-```json
-{
-  "default": "acc",
-  "connections": {
-    "acc": {
-      "apiDomain": "api.example3.vn",
-      "sqlServer": "192.0.2.101",
-      "database": "AccountUser",
-      "dbToken": "<base64-encoded connection string>",
-      "userToken": "<bearer token — optional>"
-    },
-    "Dashboard": { "apiDomain": "api.example3.vn", "…": "…" }
-  }
-}
-```
-
-`default` applies only to reads without `--db`. Writes (`fui query` with a write, `fui exec`, `fui db token-rebuild`) never use it — `--db` required.
-
-| Field       | Req | Meaning                                                  |
-| ----------- | --- | -------------------------------------------------------- |
-| key         | ✅  | alias/apiName = `_db/{alias}/` = `"/{alias}/Ten"`        |
-| `apiDomain` | ✅  | Host only, NO alias, NO trailing `/` (`api.example3.vn`) |
-| `sqlServer` | ❌* | Needed for `fui db token-rebuild`                        |
-| `database`  | ❌* | Needed for `fui db token-rebuild`                        |
-| `dbToken`   | ✅  | Base64 SQL Server connection string                      |
-| `userToken` | ❌  | Bearer to test `spAPI_*` after deploy                    |
-
-*Pass on `fui db add` so rebuild needs no re-asking.
-
-> **CRITICAL — `apiDomain` has two meanings:** `_connections.json` → bare host (`api.example3.vn`); `project.json` `data.apiDomain` → full base URL with apiName + trailing `/` (`https://tapi.example.vn/acc/`). Top bug: bare host + apiName without `/` → `tapi.lhu.edu.vnts` instead of `tapi.lhu.edu.vn/ts`. See [tapi-reference.md](tapi-reference.md) §3. Don't build URLs; copy the `Wiring URL` line from `fui sp verify`/`fui sp help`.
-
-## 2. Finding connection info
-
-### 2a. From project.json
-
-```json
-"data": {
-  "apiDomain": "https://tapi.example.vn/acc/",
-  ...
-}
-```
-
-→ `apiDomain` = `tapi.example.vn`, `apiName` = `acc` (first path segment). Multi-domain projects:
-
-```json
-"domainSetting": {
-  "sec.example.vn": {
-    "apiDomain": "https://tapi.example.vn/acc/"
-  },
-  "sec.example3.vn": {
-    "apiDomain": "https://api.example3.vn/acc/"
-  }
-}
-```
-
-→ Ask the user which domain to use.
-
-### 2b. Alias known, no dbToken → `fui db alias list` + `fui db add-by-name`
-
-Never extract UID/PWD by hand (PowerShell etc.) — exposes credentials.
-
-1. `fui db alias list` — no args: tAPI injects `@sys_UserID` from the Bearer token, so `SM_Modules_ManagerSelect` returns only DBs you're granted. Columns `APIName | SQLServer | DatabaseName | ModuleName | Enable`; `--search` filters client-side (APIName/DatabaseName/ModuleName, case-insensitive).
-2. `fui db add-by-name <apiName>` — looks up SQLServer/DatabaseName on acc → borrows the UID/PWD pair of an existing connection → builds dbToken → tests `SELECT 1` before saving anything → saves + fetches schema to `_db/{alias}/`. Never prints dbToken/UID/PWD.
-
-- Several different logins in workspace → menu; pass `--borrow-from <projectId>/<alias>`. Same login across one group's connections is not ambiguous.
-- "apiName not found" = alias doesn't exist OR you're not granted it. Don't assume a typo; run `fui db alias list`.
-- Project with no connections works: apiDomain from local `project.json`, userToken borrowed from another project on the same domain (auto only if exactly one candidate, else menu). Else pass `--api-domain` + `--user-token-env VAR`.
-
-> ⚠️ `Password` in `SM_Modules_ManagerSelect` is a tAPI internal hash, not the SQL password — unusable for dbToken. fui never prints it.
-
-### 2c. First connection for a new project
-
-> Requires the DB to exist and be registered as an alias in `acc`. Otherwise do [project-provisioning.md](project-provisioning.md) first (DB, two SQL accounts, `fui db alias new`).
-
-```
-1. fui project sync -p <projectId>   → local project.json (apiDomain source)
-2. fui use -p <projectId>            → project implied afterwards
-3. fui db alias list                 → aliases you may manage
-4. fui db add-by-name <apiName>      → lookup + token + test + save + schema (do NOT run fui schema pull after)
-5. Module uses other aliases? Repeat 4 per alias. Added connections do NOT become default (use --default).
-```
-
-Already have a dbToken → skip 3–4, use `fui db add`.
-
-## 3. Building a dbToken
-
-Only if you hold UID/PWD and want `fui db add`; to borrow credentials use `fui db add-by-name` (no plain text). dbToken = base64 of:
-
-```
-Server={sqlServer};Database={database};UID={uid};PWD={pwd};Encrypt=True;TrustServerCertificate=True;
-```
-
-```js
-Buffer.from(
-  "Server=192.0.2.101;Database=AccountUser;UID=sa;PWD=MyPass;Encrypt=True;TrustServerCertificate=True;",
-).toString("base64");
-```
-
-```powershell
-[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("Server=192.0.2.101;Database=AccountUser;UID=sa;PWD=MyPass;Encrypt=True;TrustServerCertificate=True;"))
-```
-
-Pass secrets only via stdin (`-`) or `--*-env VAR`.
-
-## 4. `fui db add`
-
-- Saved to `{FUI_MCP_WORKDIR}/{projectId}/_db/_connections.json` under `apiName`. projectId ≠ apiName; a project can have many apiNames — never derive one from the other.
-- **Mandatory:** projectId not stated, or alias's project unclear → ask _"Which project should this DB connection be saved to? (projectId)"_ before `fui db add`. Wrong project misplaces schema/SPs.
-
-```
-fui db add <alias> -p <project> --token - --api-domain host --sql-server host --database name [--user-token-env VAR] [--default]
-  → schema auto-fetched to _db/{alias}/schema.json; do NOT run fui schema pull after
-```
-
-- Always pass `--sql-server` + `--database` (enables `fui db token-rebuild`).
-- Multi-DB: each distinct `"/{alias}/…"` in `module.json` needs its own `fui db add`; later adds don't touch existing ones. A missing alias gets no checks: `fui module validate` can't match SP names, `fui sp verify`/`fui sp get` can't find SPs, `fui sp deploy` can't reach the DB.
-- First connection stays `default`; change with `--default`.
-
-## 5. Password change — `fui db token-rebuild`
-
-UID/PWD changed, Server/Database unchanged:
-
-1. `fui db list -p <projectId>` — confirm the connection has `sqlServer` and `database` (missing → full `fui db add` instead).
-2. `fui db token-rebuild --db <alias> --uid <login> --pwd -` — rebuilds, tests, saves.
-
-`--db` REQUIRED with >1 connection (overwrites credentials; wrong guess clobbers another DB's token).
-
-## 6. userToken
-
-- `userToken` = user's Bearer token to call `spAPI_*` after deploy as a real user; `dbToken` = direct SQL Server connection.
-
-```
-dbToken   → SQL Server connection to run schema/SP
-userToken → call tAPI REST API as an end-user (test spAPI_*)
-```
-
-- Shareable across projects with the same `GroupName` in `_projectInfo.json` (`{ "GroupName": "GroupA" }`): `fui db user-token --db <alias> --from <project/alias>` — no re-login. `fui db user-token` with no source lists workspace tokens.
-- Stored PER CONNECTION in `_connections.json`. Multi-DB → one token per connection; pass `--db <alias>` (omitted → default).
-- `fui right …` calls `acc` with the userToken of the connection matching the current apiName (else default); missing there → rights commands fail even if other connections have tokens.
-- Not set at `fui db add` → `fui db user-token --db <alias> --token -`.
-
-## 6a. Domain SSO — same parent domain: token works, don't ask
-
-SSO is by parent domain: all APIs under e.g. `*.lhu.edu.vn` (`tapi.lhu.edu.vn`, `api.lhu.edu.vn`, `capnhatluong.lhu.edu.vn`…) accept the same `userToken`.
-
-- Have a token for that parent domain → use it for other projects/aliases there. Do NOT ask the user, do NOT test-call to "verify", do NOT make them log in.
-- Scanning the workspace for tokens (`fui db user-token` without a token) is valid and recommended.
-
-| Case                                              | Action                                       |
-| ------------------------------------------------- | -------------------------------------------- |
-| Same parent domain                                | Use now, no asking/testing                   |
-| Different parent domain (`*.dhlh.vn`, `*.fap.vn`) | Token invalid — need that domain's token     |
-| `domainSetting` hosts on different parent domains | Each parent domain is its own SSO zone (§2a) |
-
-> `GroupName` is admin grouping; the parent domain decides acceptance. If they differ, trust the domain.
-
-## 7. Schema refresh
-
-| When                                                            | Command                        |
-| --------------------------------------------------------------- | ------------------------------ |
-| After `fui db add`                                              | Not needed                     |
-| User asks / table or SP created, renamed, dropped / cache stale | `fui schema pull --db <alias>` |
-
-Read cache (no DB call): `fui schema [--db <alias>] [--type Table|View|API|"API File"|Procedure|Function] [--search text]`.
-
-- Each connection has its own `schema.json`; both commands act on one connection. Pulling one alias doesn't refresh others — check `fui db list`, pull each. Object missing in `fui schema` usually = wrong connection.
-- `fui schema pull` also reloads every `_db/{alias}/{name}.sql`; local copies differing from server go to `_history/` first. Don't trust local files as latest before a pull.
-
-Orphans: `fui db add`/`fui schema pull` scan actual `.sql` files in that connection's `_db/{alias}/` only:
-
-| Group             | Condition       | Behavior                                                                                                       |
-| ----------------- | --------------- | -------------------------------------------------------------------------------------------------------------- |
-| Alive             | in NEW schema   | keep, reload body                                                                                              |
-| Dropped on server | in OLD, not NEW | archive to `_history/{projectId}/_db/{alias}/{name}_{timestamp}_deleted.sql`, remove locally                   |
-| Local only        | in neither      | listed, NOT deleted (likely unsaved draft from `fui sp save`); clean with `fui schema pull --prune-local-only` |
-
-Prints `📋 Archived orphaned local SP file(s)...` when archiving. Name match is case-insensitive.
-
-## 8. SP workflow
-
-```
-1. fui sp list                        → all connections, SPs tagged by alias
-2. fui sp get <name>                  → fetch definition → _db/{alias}/{name}.sql
-3. edit _db/{alias}/{name}.sql
-4. fui sp save <name> -f file.sql     → local only, not deployed
-5. fui sp deploy <name>               → server's RUNNING version saved to _history/ first (rollback copy);
-                                        spAPI_*/spAPIFILE_* → auto /help clears tAPI cache once
-                                        (failure ignored, doesn't block, don't retry)
-6. fui sp help <name>                 → REQUIRED if the SP was ALTERed outside fui sp deploy
-                                        (e.g. ALTER PROCEDURE via fui exec — no auto-clear).
-                                        Also shows input params before wiring IN/OUT in module.json.
-                                        Calls ONCE on the standard URL; failure = one info line.
-                                        Do NOT try URL variants.
-7. fui sp verify <name> [--params …]  → STATIC contract check (read or write API); calls NO endpoint.
-                                        Reads real SP body → response shape, error contract, read/write,
-                                        apiMocks snippet for fui module simulate. REQUIRED before writing
-                                        apiMocks for an existing SP — never invent structure;
-                                        fui module simulate warns on unverified mocks matching real SPs.
-```
-
-- `--db` omitted → inferred from SP name (schema + local `.sql` per connection). One match → silent; zero or several (same name in two DBs) → alias menu, pick and re-run, don't guess.
-- `fui sp save` for a brand-new SP can't infer: multi-connection projects must pass `--db` on first save.
-
-> `fui sp verify` reads the real body, not the name; hard error if unreadable. Write-API testing with `fui module simulate`: [tools-registry.md](tools-registry.md). Guards on `DROP`/`ALTER TABLE`, `DELETE`/`UPDATE` without `WHERE` are enforced in code, no bypass. Writes via `fui query`/`fui exec` need `--confirm-write`.
-
-**Rollback:** read `{FUI_MCP_WORKDIR}/_history/{projectId}/_db/{alias}/{name}_{timestamp}.sql` → `fui sp save <name> -f <old file>` → `fui sp deploy <name>`.
-
-## 8a. Linked Server — `spIO_IN_` / `spIO_OUT_`
-
-Linked servers exist, but for security you can NOT query another DB's tables through them — only call a predefined SP on the other side:
-
-```sql
-EXEC XDATA23.Calendar2015.dbo.spIO_IN_DeleteMonHocInfo @MonHocID, @ErrorDKMH OUTPUT
---   ^^^^^^^^^^^^^^^^^^^^^^^^^                         ← 4 parts: linked-server.database.schema.sp-name
-```
-
-| Prefix      | Direction         | Use                                                       |
-| ----------- | ----------------- | --------------------------------------------------------- |
-| `spIO_IN_`  | Into current DB   | Receives commands from an external DB, acts on current DB |
-| `spIO_OUT_` | Out of current DB | Provides data for an external DB to call                  |
-
-- These are boundary SPs, NOT tAPI endpoints (despite `spIO_`). Never wire into `"API":` in module.json.
-- New SPs acting across a linked server MUST use the prefix matching data direction.
-- `fui sp deploy` can't deploy them to the other DB; they run on the current DB and `EXEC` across. Deploy to the owning DB's alias.
-
-## 9. List connections
-
-`fui db list -p <projectId>` — every connection: alias, `apiDomain`, `sqlServer`, `database`, `_db/{alias}/`, dbToken/userToken present or not (never values), which is `default`. Run first when unsure which `--db` to use. Also lists `_db/` folders with no connection (leftovers, nothing reads them) — delete manually when sure.
-
-## 10. Cheat sheet
-
-| Situation                                         | Command                                                                                                                    |
-| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| DB doesn't exist (from scratch)                   | [project-provisioning.md](project-provisioning.md): 2 permission gates → CREATE DATABASE → 2 accounts → `fui db alias new` |
-| Check `CREATE DATABASE`/`CREATE LOGIN` rights     | [project-provisioning.md](project-provisioning.md) §Step 0 — `IS_SRVROLEMEMBER` + `HAS_PERMS_BY_NAME`, read-only           |
-| DB exists, no alias in `acc`                      | `fui db alias new` ([project-provisioning.md](project-provisioning.md) §Step 5)                                            |
-| First connect, have dbToken                       | `fui db add`                                                                                                               |
-| Alias only, no dbToken                            | `fui db alias list` → `fui db add-by-name`                                                                                 |
-| Which DBs am I granted                            | `fui db alias list`                                                                                                        |
-| Another DB (new alias)                            | `fui db add-by-name` again                                                                                                 |
-| Connections + default                             | `fui db list`                                                                                                              |
-| UID/PWD changed                                   | `fui db token-rebuild` (`--db` if several)                                                                                 |
-| Set userToken                                     | `fui db user-token` (`--db` if several)                                                                                    |
-| List tables/SPs                                   | `fui sp list`                                                                                                              |
-| Get SP body                                       | `fui sp get`                                                                                                               |
-| Refresh / read schema                             | `fui schema pull` / `fui schema`                                                                                           |
-| Save SQL locally                                  | `fui sp save`                                                                                                              |
-| Deploy (auto cache clear for spAPI__/spAPIFILE__) | `fui sp deploy`                                                                                                            |
-| API input params before wiring                    | `fui sp help`                                                                                                              |
-| Clear tAPI cache after ALTER via `fui exec`       | `fui sp help` (required)                                                                                                   |
-| Static check of deployed API                      | `fui sp verify`                                                                                                            |
-| Drop / rename SP                                  | `fui sp delete` / `fui sp rename`                                                                                          |
-| SQLServer + DatabaseName of an alias              | `fui db alias list --search <text>`                                                                                        |
-| dbToken via borrowed UID/PWD                      | `fui db add-by-name` — never decode by hand in PowerShell                                                                  |
-
-## 11. Table design
-
-Naming, primary keys, timestamps, audit columns: [db-table-design.md](db-table-design.md) — load when designing a schema.