Fix issues #160, #161, #162: database, CLI and Vite docs accuracy

Fixes #160
Fixes #161
Fixes #162

Chapter 11 - Database (#160):
- Migration namespace: V400 → v400 (lowercase, case-sensitive on Linux)
- users.id column type: string → int (auto-increment)
- System tables path: remove UF4/5 app/system/ path, reference Core sprinkle instead
- Sprunje: add note explaining ->like() / ->orLike() are UF-specific builder methods

Chapter 14 - CLI (#161):
- assets:build: remove stale aliases (webpack, build-assets); rewrite description for Vite-first behavior
- assets:webpack: fix npm script names (dev/build/watch → webpack:dev/webpack:build/webpack:watch); add --server option
- assets:install / assets:update: packages.lock → package-lock.json
- bake: remove create:admin-user from built-in list (added by Account sprinkle event listener)

Chapter 15 - Assets/Vite (#162):
- vite:build script: vite build → vue-tsc && vite build (TypeScript type-check runs before build)
- coverage script: vitest --coverage → vitest run --coverage (prevents hanging watch mode in CI)
- Add prose explaining vue-tsc type-check step

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: lcharette

app/pages/6.0/11.database/02.default-tables/docs.md

@@ -5,7 +5,7 @@ description: UserFrosting's installer creates a number of tables by default.  He
 
 When you install UserFrosting with the [Bakery CLI](/cli), a number of tables will automatically added to your database. These tables are required for UserFrosting's built-in features, such as user accounts, request throttling, persistent sessions, and access control.
 
-The [migrations](/database/migrations) for most tables can be found in the `src/Database/Migrations` directory of the Sprinkle that depends on it. The exceptions are the system tables, which are located in `app/system/Database/Migrations`.
+The [migrations](/database/migrations) for most tables can be found in the `src/Database/Migrations` directory of the Sprinkle that depends on it. The exceptions are the system tables, which are located in the [Core sprinkle](/structure/sprinkles#core-sprinkle).
 
 ## System tables
 
@@ -62,7 +62,7 @@ This table contains records for each user.
 
 | Column              | Type           | Description                                                                                                                                               |
 | ------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `id`                | `string`       | The unique identifier for the user.                                                                                                                       |
+| `id`                | `int` (auto-increment) | The unique identifier for the user.                                                                                                                       |
 | `user_name`         | `string(50)`   | A unique text identifier for the user. Only `[a-zA-Z0-9_-]` characters are allowed.                                                                       |
 | `email`             | `string(255)`  | The email address of the user. Must be unique.                                                                                                            |
 | `first_name`        | `string(20)`   | The user's first name. Optional.                                                                                                                          |

app/pages/6.0/11.database/03.migrations/docs.md

@@ -180,9 +180,9 @@ namespace UserFrosting\Sprinkle\MySprinkle\Database\Migrations;
 
 use Illuminate\Database\Schema\Blueprint;
 use UserFrosting\Sprinkle\Core\Database\Migration;
-use UserFrosting\Sprinkle\Account\Database\Migrations\V400\UsersTable;
-use UserFrosting\Sprinkle\Account\Database\Migrations\V400\RolesTable;
-use UserFrosting\Sprinkle\Account\Database\Migrations\V400\RoleUsersTable;
+use UserFrosting\Sprinkle\Account\Database\Migrations\v400\UsersTable;
+use UserFrosting\Sprinkle\Account\Database\Migrations\v400\RolesTable;
+use UserFrosting\Sprinkle\Account\Database\Migrations\v400\RoleUsersTable;
 
 class MembersTable extends Migration
 {

app/pages/6.0/11.database/05.data-sprunjing/docs.md

@@ -211,6 +211,9 @@ To do this, you can define custom methods in your Sprunje:
     }
 ```
 
+> [!NOTE]
+> `->like()` and `->orLike()` are UserFrosting-specific query builder methods defined in `UserFrosting\Sprinkle\Core\Database\Builder`. They generate `LIKE '%value%'` clauses. You can alternatively use standard Eloquent syntax: `$query->where('genus', 'LIKE', "%{$value}%")->orWhere('species', 'LIKE', "%{$value}%")`.
+
 The method name should consist of the field name (converted to StudlyCase), prefixed with `filter` or `sort`.
 
 Thus, in this example a request parameter of `filters[scientific_name]=mega` will invoke the `filterScientificName` method in your Sprunje.

app/pages/6.0/14.cli/01.commands/docs.md

@@ -36,7 +36,7 @@ $ php bakery help
 
 ### assets:build
 
-The `assets:build` (alias : `webpack` & `build-assets`) command is the general assets building command. It combines `assets:install` and `assets:webpack` into a single command:
+The `assets:build` command is the general assets building command. It installs frontend dependencies and triggers a production build. The exact commands run depend on your configured bundler. For Vite (the default), it runs `assets:install` and `assets:vite` depending on the environment:
 
 ```bash
 $ php bakery assets:build [options]
@@ -54,21 +54,22 @@ See the [Asset Management](/assets-vite) chapter for more information about asse
 
 ### assets:install
 
-The `assets:install` command is an alias for the **NPM** scripts used to install all required frontend dependencies locally, based on `packages.lock`. The versions defined in the lock file will be downloaded. Behind the scene, it's an alias for the `npm install` npm command.
+The `assets:install` command is an alias for the **NPM** scripts used to install all required frontend dependencies locally, based on `package-lock.json`. The versions defined in the lock file will be downloaded. Behind the scene, it's an alias for the `npm install` npm command.
 
 ### assets:update
 
-The `assets:update` command is an alias for the **NPM** scripts used to update all frontend dependencies, ignoring the versions defined in `packages.lock`. Behind the scenes, it's an alias for the `npm update` npm command.
+The `assets:update` command is an alias for the **NPM** scripts used to update all frontend dependencies, ignoring the versions defined in `package-lock.json`. Behind the scenes, it's an alias for the `npm update` npm command.
 
 ### assets:webpack
 
-The `assets:webpack` command is an alias for the **Webpack Encore** scripts used to compile frontend dependencies to `/public/assets`. Behind the scenes, it's an alias for the npm commands `npm run dev`, `npm run build` and `npm run watch`. See the table below for more information.
+The `assets:webpack` command is an alias for the **Webpack Encore** scripts used to compile frontend dependencies to `/public/assets`. Behind the scenes, it's an alias for the npm commands `npm run webpack:dev`, `npm run webpack:build` and `npm run webpack:watch`. See the table below for more information.
 
-| Option           | Description                                                                               | Alias of        |
-|------------------|-------------------------------------------------------------------------------------------|-----------------|
-| _no options_     | Compile the assets for development environment                                            | `npm run dev`   |
-| -p, --production | Compile the assets for production environment                                             | `npm run build` |
-| -w, --watch      | Watch for changes and recompile automatically. Only available in development environment. | `npm run watch` |
+| Option           | Description                                                                               | Alias of                 |
+|------------------|-------------------------------------------------------------------------------------------|--------------------------|
+| _no options_     | Compile the assets for development environment                                            | `npm run webpack:dev`    |
+| -p, --production | Compile the assets for production environment                                             | `npm run webpack:build`  |
+| -w, --watch      | Watch for changes and recompile automatically. Only available in development environment. | `npm run webpack:watch`  |
+| -s, --server     | Start the HMR development server.                                                         | `npm run webpack:server` |
 
 > [!NOTE]
 > The `production` option is automatically applied when the [environment mode](/configuration/config-files#environment-modes) is set to `production`.
@@ -101,7 +102,7 @@ See the [Asset Management](/assets-vite) chapter for more information about Vite
 
 ### bake
 
-Bake is the general installation command. It combines `setup:db`, `setup:mail`, `debug`, `migrate`, `create:admin-user`, `assets:build` and `clear-cache` into a single command:
+Bake is the general installation command. It combines `setup:db`, `setup:mail`, `debug`, `migrate`, `assets:build` and `clear-cache` into a single command:
 
 ```bash
 $ php bakery bake

app/pages/6.0/15.assets-vite/04.build-workflow/docs.md

@@ -53,11 +53,13 @@ This launches Vite in development mode with:
 
 When running, your browser loads assets directly from Vite's dev server for the fastest possible feedback loop.
 
-**`npm run vite:build`** - Creates an optimized production build
+**`npm run vite:build`** - Type-checks TypeScript then creates an optimized production build
 ```json
-"vite:build": "vite build"
+"vite:build": "vue-tsc && vite build"
 ```
 
+The `vue-tsc` prefix runs a full TypeScript type-check before building. If there are any type errors, the build will abort. This ensures type safety is enforced in CI as well as locally.
+
 This generates production-ready assets with:
 - **Code minification** - Removes whitespace and shortens variable names
 - **Tree shaking** - Eliminates unused code from bundles
@@ -96,7 +98,7 @@ Executes your test suite using [Vitest](https://vitest.dev/), a fast testing fra
 
 **`npm run coverage`** - Generates a test coverage report
 ```json
-"coverage": "vitest --coverage"
+"coverage": "vitest run --coverage"
 ```
 
 Creates a detailed report showing which parts of your code are tested.