cabloy 5.1.202 → 5.1.203

package/.cabloy-version

@@ -1 +1 @@
-5.1.202
+5.1.203

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## 5.1.203
+
+### Features
+- Update application features.
+
+### Improvements
+- Refactor end-to-end tests.
+- Clarify managed E2E resource authorization documentation.
+- Add a video demonstrating second-level tabs for admin multitasking.
+- Update the demo documentation.
+
 ## 5.1.202
 
 ### Features

package/CONTRIBUTING.md

@@ -27,23 +27,24 @@ Current CI workflows run on Ubuntu with Node.js 24 after pushes to `main`; do no
 
 Start with the narrowest meaningful check, then broaden validation when a change crosses a shared boundary.
 
-| Purpose                                  | Command                    |
-| ---------------------------------------- | -------------------------- |
-| Start Vona development                   | `npm run dev`              |
-| Start one Vona development process       | `npm run dev:one`          |
-| Start Basic Admin SSR development        | `npm run dev:zova:admin`   |
-| Start Basic Web SSR development          | `npm run dev:zova:web`     |
-| Check formatting                         | `npm run format`           |
-| Lint                                     | `npm run lint`             |
-| Type-check Vona and Zova                 | `npm run tsc`              |
-| Run backend tests                        | `npm run test`             |
-| Run the full E2E suite                   | `npm run test:e2e`         |
-| Rerun E2E tests without reset            | `npm run test:e2e:fast`    |
-| Build required Basic artifacts           | `npm run build`            |
-| Build Basic Admin SSR and REST artifacts | `npm run build:zova:admin` |
-| Build Basic Web SSR and REST artifacts   | `npm run build:zova:web`   |
-| Synchronize Zova dependencies into Vona  | `npm run deps:vona`        |
-| Build the public documentation site      | `npm run docs:build`       |
+| Purpose                                   | Command                    |
+| ----------------------------------------- | -------------------------- |
+| Start Vona development                    | `npm run dev`              |
+| Start one Vona development process        | `npm run dev:one`          |
+| Start Basic Admin SSR development         | `npm run dev:zova:admin`   |
+| Start Basic Web SSR development           | `npm run dev:zova:web`     |
+| Check formatting                          | `npm run format`           |
+| Lint                                      | `npm run lint`             |
+| Type-check Vona and Zova                  | `npm run tsc`              |
+| Run backend tests                         | `npm run test`             |
+| Run the managed local test-mode E2E suite | `npm run test:e2e`         |
+| Build required Basic artifacts            | `npm run build`            |
+| Build Basic Admin SSR and REST artifacts  | `npm run build:zova:admin` |
+| Build Basic Web SSR and REST artifacts    | `npm run build:zova:web`   |
+| Synchronize Zova dependencies into Vona   | `npm run deps:vona`        |
+| Build the public documentation site       | `npm run docs:build`       |
+
+`npm run test:e2e` starts a fresh runner-managed local Vona worker in test mode and runs Playwright against Vona integrated SSR. Select flat spec basenames directly after the script, for example `npm run test:e2e a-commerce`; place Playwright filters after npm's `--` delimiter, for example `npm run test:e2e a-commerce -- --tag @smoke`. Browser commands consume existing SSR/REST artifacts and do not rebuild them. Confirm exclusive ownership of the effective test database, local Redis namespace, public/runtime paths, application identity, API origin, and listener before starting a test-mode runtime; an available port alone is not sufficient. Externally managed `E2E_BASE_URL` targets are unsupported.
 
 The tracked pre-commit hook runs `lint-staged`. It may format staged Markdown and configuration files, and may lint-fix and format staged source files. Review the resulting staged changes and run the relevant explicit checks before submitting.
 

package/README.md

@@ -38,9 +38,9 @@ See the [AI Spec-Driven Development](https://cabloy.com/ai/ai-spec-driven-develo
 
 ## Demonstrations(Videos)
 
-### 1. Can an Admin Site Use SSR? CabloyJS in Three Practical Demos (Duration: 1:16)
+### 1. AI Coding in Action: One Prompt for CRUD, SSR & Multitasking (Duration: 3:50)
 
-[![CabloyJS Admin SSR video](./repo-docs/assets/img/cabloy-admin-ssr-cover-en.png)](https://youtu.be/786IQhRdr1I)
+[![CabloyJS AI CRUD video](./repo-docs/assets/img/cabloy-ai-crud-cover-en.png)](https://youtu.be/PV9_By08hDM)
 
 ## Editions
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cabloy",
-  "version": "5.1.202",
+  "version": "5.1.203",
   "gitHead": "2c5c19284bab738e492856189acb6fad74b8a7b7",
   "description": "A Node.js fullstack framework",
   "keywords": [
@@ -45,8 +45,7 @@
     "start": "cd vona && npm run start",
     "start:one": "cd vona && npm run start:one",
     "test": "cd vona && npm run test",
-    "test:e2e": "node repo-e2e/scripts/runE2e.ts --clean",
-    "test:e2e:fast": "node repo-e2e/scripts/runE2e.ts --fast",
+    "test:e2e": "node repo-e2e/scripts/runE2e.ts",
     "test:docs:e2e": "npm run docs:build && playwright test --config repo-e2e/docs/playwright.config.ts",
     "db:reset": "cd vona && npm run db:reset",
     "tsc": "npm run tsc:zova && pnpm --dir vona run tsc",

package/repo-agent-governance/managed-assets.json

@@ -256,7 +256,7 @@
     {
       "adapter": "codex",
       "category": "skill",
-      "sha256": "b77b5e472c742dd4ab9825c2f6352e47388a0b6d1edf6d7e195b5b03eabdc566",
+      "sha256": "0d1901134f7222902cfc702275ed7bd83a4e3a1d72c3543a77c8ab5d7cabaa55",
       "source": "skills/cabloy-workflow/evals/evals.json",
       "target": ".agents/skills/cabloy-workflow/evals/evals.json"
     },
@@ -277,7 +277,7 @@
     {
       "adapter": "codex",
       "category": "skill",
-      "sha256": "4421d2ef57ffe0c35669a1f1800fd0838363e4e3c1a1a284deadfdb96f0e194d",
+      "sha256": "ff0760f6fa7c24f561fdcfa07094d9d6e8d82fcef358458a36ff0c38a30ea89e",
       "source": "skills/cabloy-workflow/SKILL.md",
       "target": ".agents/skills/cabloy-workflow/SKILL.md"
     },
@@ -291,7 +291,7 @@
     {
       "adapter": "codex",
       "category": "skill",
-      "sha256": "c1a251bffa1c10312300c3ea837df17d9a7dec5a258d028407eeb08dc4a9f75d",
+      "sha256": "791dd8e89b63dfd0714538b3b15d0b4750b6889f538b65f7137bb93f091e02d9",
       "source": "skills/cabloy-worktree-environment/SKILL.md",
       "target": ".agents/skills/cabloy-worktree-environment/SKILL.md"
     },
@@ -592,7 +592,7 @@
     {
       "adapter": "claude",
       "category": "skill",
-      "sha256": "b77b5e472c742dd4ab9825c2f6352e47388a0b6d1edf6d7e195b5b03eabdc566",
+      "sha256": "0d1901134f7222902cfc702275ed7bd83a4e3a1d72c3543a77c8ab5d7cabaa55",
       "source": "skills/cabloy-workflow/evals/evals.json",
       "target": ".claude/skills/cabloy-workflow/evals/evals.json"
     },
@@ -613,7 +613,7 @@
     {
       "adapter": "claude",
       "category": "skill",
-      "sha256": "4421d2ef57ffe0c35669a1f1800fd0838363e4e3c1a1a284deadfdb96f0e194d",
+      "sha256": "ff0760f6fa7c24f561fdcfa07094d9d6e8d82fcef358458a36ff0c38a30ea89e",
       "source": "skills/cabloy-workflow/SKILL.md",
       "target": ".claude/skills/cabloy-workflow/SKILL.md"
     },
@@ -627,7 +627,7 @@
     {
       "adapter": "claude",
       "category": "skill",
-      "sha256": "c1a251bffa1c10312300c3ea837df17d9a7dec5a258d028407eeb08dc4a9f75d",
+      "sha256": "791dd8e89b63dfd0714538b3b15d0b4750b6889f538b65f7137bb93f091e02d9",
       "source": "skills/cabloy-worktree-environment/SKILL.md",
       "target": ".claude/skills/cabloy-worktree-environment/SKILL.md"
     },
@@ -683,7 +683,7 @@
     {
       "adapter": "cursor",
       "category": "policy",
-      "sha256": "f0a6dd9005443bdc194e8a1cd8e8f303a139f9bb838205d68d722379f6889b4f",
+      "sha256": "db2467e225f30b74efb312c45572324f75a6a81077e19b7723ffd640a45793f9",
       "source": "policies/repository.md",
       "target": ".cursor/rules/cabloy-governance.mdc"
     },
@@ -942,7 +942,7 @@
     {
       "adapter": "cursor",
       "category": "skill",
-      "sha256": "b77b5e472c742dd4ab9825c2f6352e47388a0b6d1edf6d7e195b5b03eabdc566",
+      "sha256": "0d1901134f7222902cfc702275ed7bd83a4e3a1d72c3543a77c8ab5d7cabaa55",
       "source": "skills/cabloy-workflow/evals/evals.json",
       "target": ".cursor/skills/cabloy-workflow/evals/evals.json"
     },
@@ -963,7 +963,7 @@
     {
       "adapter": "cursor",
       "category": "skill",
-      "sha256": "4421d2ef57ffe0c35669a1f1800fd0838363e4e3c1a1a284deadfdb96f0e194d",
+      "sha256": "ff0760f6fa7c24f561fdcfa07094d9d6e8d82fcef358458a36ff0c38a30ea89e",
       "source": "skills/cabloy-workflow/SKILL.md",
       "target": ".cursor/skills/cabloy-workflow/SKILL.md"
     },
@@ -977,7 +977,7 @@
     {
       "adapter": "cursor",
       "category": "skill",
-      "sha256": "c1a251bffa1c10312300c3ea837df17d9a7dec5a258d028407eeb08dc4a9f75d",
+      "sha256": "791dd8e89b63dfd0714538b3b15d0b4750b6889f538b65f7137bb93f091e02d9",
       "source": "skills/cabloy-worktree-environment/SKILL.md",
       "target": ".cursor/skills/cabloy-worktree-environment/SKILL.md"
     },
@@ -1005,14 +1005,14 @@
     {
       "adapter": "codex",
       "category": "policy",
-      "sha256": "c87071f6f34adaaaf25aac5cb41d9ff10daea1743a31bd3344517d68a3d4082a",
+      "sha256": "307edb0409d7d723c213c534713d2477ba000f19571e054d5498aeb9578b22bb",
       "source": "policies/repository.md",
       "target": "AGENTS.md"
     },
     {
       "adapter": "claude",
       "category": "policy",
-      "sha256": "c87071f6f34adaaaf25aac5cb41d9ff10daea1743a31bd3344517d68a3d4082a",
+      "sha256": "307edb0409d7d723c213c534713d2477ba000f19571e054d5498aeb9578b22bb",
       "source": "policies/repository.md",
       "target": "CLAUDE.md"
     }

package/repo-agent-governance/policies/repository.md

@@ -71,6 +71,7 @@ Before inventing a custom implementation path:
 - Treat hooks, permissions, local settings, credentials, MCP registration, command discovery, and automatic command execution as platform-specific integrations, not portable rule or skill capabilities.
 - After implementation, do not launch broad reviews automatically; when review is needed, scope it to the current diff and report only high-confidence issues.
 - Do not modify shared environment identity or ports merely to bypass a busy resource. For intentional parallel worktree setup, follow `repo-docs/fullstack/parallel-worktree-environment.md`; otherwise wait for the shared resource or ask the user. Create or change worktree-local environment overrides only through the explicitly invoked `cabloy-worktree-environment` skill and its confirmation phase, and only in `vona/env/.env.local` and `zova/env/.env.local`; never modify flavor-, mode-, app-mode-, or runtime-specific `.env.*.local` files. The skill derives the standard `APP_NAME`, `SERVER_LISTEN_PORT`, `DEV_SERVER_PORT`, `DEV_SERVER_HMR_PORT`, and API-derived `API_BASE_URL` tuple only from Git worktree metadata and fixed port baselines; never read or expose `.env*` content while recommending values. Admin and Web are alternative commands using this shared tuple and must not run concurrently in one worktree; use another linked worktree for concurrent use. Detect the active edition before choosing scripts, and never run `npm run init` as an automatic follow-up.
+- Before `npm run test:e2e`, verify exclusive use of the effective test-database cleanup scope, Redis cleanup namespace, public/runtime paths, and listener; a free port or separate worktree alone is insufficient. If a standing authorization covers this checkout and its resources remain exclusively assigned with no conflicting process, do not repeatedly ask to run the managed suite; if scope or ownership changes or is uncertain, wait or ask. This does not authorize manual resets, broader cleanup, or changing shared configuration. See `repo-docs/reference/repo-scripts.md`.
 - For SSR theme-sensitive frontend work, detect the active edition marker and UI library before making assumptions. Cabloy Basic currently means DaisyUI + Tailwind CSS assumptions; Cabloy Start currently means Vuetify assumptions.
 - In Web SSR without cookie-backed theme resolution, do not treat server reads of `$theme.dark`, `$theme.darkMode`, or `$token` as final browser truth. Keep theme-sensitive SSR branching hydration-tolerant or defer final theme-sensitive decisions to the client.
 - Do not assume Cabloy Basic and Cabloy Start use the same adapter-level SSR theme handoff. Verify the active theme handler and client hydration path before changing SSR theme behavior.

package/repo-agent-governance/skills/cabloy-workflow/SKILL.md

@@ -107,11 +107,11 @@ The reason is simple: these files are where Cabloy already encodes its real work
 
 ### Parallel worktree environment setup
 
-When a request involves a second worktree, concurrent Vona/Zova development, isolated ordinary tests, or managed clean E2E, classify it as fullstack workflow setup. Read [Parallel Worktree Environment](../../../repo-docs/fullstack/parallel-worktree-environment.md), the canonical shared recipe maintained in Cabloy Basic for both editions.
+When a request involves a second worktree, concurrent Vona/Zova development, isolated ordinary tests, or managed E2E, classify it as fullstack workflow setup. Read [Parallel Worktree Environment](../../../repo-docs/fullstack/parallel-worktree-environment.md), the canonical shared recipe maintained in Cabloy Basic for both editions.
 
 This routing skill provides read-only guidance only. Do not infer an `APP_NAME` or ports, edit local overrides, or run `npm run init` from a generic worktree request. When the user wants confirmation-gated local environment setup, ask them to explicitly invoke `/cabloy-worktree-environment`.
 
-The invoked skill detects Basic or Start to select the active root scripts and managed clean-E2E command. It uses Git worktree metadata, fixed Vona/Zova port baselines, and the worktree basename to recommend the complete standard tuple for confirmation: `APP_NAME`, `SERVER_LISTEN_PORT`, `DEV_SERVER_PORT`, `DEV_SERVER_HMR_PORT`, and an `API_BASE_URL` derived from the Vona port. After confirmation, it writes both `vona/env/.env.local` and `zova/env/.env.local`; never use flavor-, mode-, app-mode-, or runtime-specific `.env.*.local` files. It does not inspect environment-file content or allocate/reserve a live port. The shared environment is Vona + Zova development: Admin and Web are alternative commands using the same configuration, and they must not run concurrently in one worktree. Concurrent use requires separately configured linked worktrees.
+The invoked skill detects Basic or Start to select the active root scripts and managed E2E command. It uses Git worktree metadata, fixed Vona/Zova port baselines, and the worktree basename to recommend the complete standard tuple for confirmation: `APP_NAME`, `SERVER_LISTEN_PORT`, `DEV_SERVER_PORT`, `DEV_SERVER_HMR_PORT`, and an `API_BASE_URL` derived from the Vona port. After confirmation, it writes both `vona/env/.env.local` and `zova/env/.env.local`; never use flavor-, mode-, app-mode-, or runtime-specific `.env.*.local` files. It does not inspect environment-file content or allocate/reserve a live port. The shared environment is Vona + Zova development: Admin and Web are alternative commands using the same configuration, and they must not run concurrently in one worktree. Concurrent use requires separately configured linked worktrees.
 
 ## Step 4: Prefer CLI-first workflows
 

package/repo-agent-governance/skills/cabloy-workflow/evals/evals.json

@@ -39,7 +39,7 @@
     },
     {
       "id": 7,
-      "prompt": "I created a linked Cabloy Start worktree and need isolated Vona, Zova Web, and managed clean E2E. Which workflow should I use?",
+      "prompt": "I created a linked Cabloy Start worktree and need isolated Vona, Zova Web, and managed E2E. Which workflow should I use?",
       "expected_output": "Routes to the canonical shared guide and explicitly invoked /cabloy-worktree-environment skill. It recognizes that the invoked skill selects the Start command npm run test:e2e while retaining read-only generic routing, a deterministic Git-metadata recommendation, no environment-content inspection, no automatic initialization, and the universal five-setting tuple written to both permitted broad local files only after confirmation.",
       "files": []
     },

package/repo-agent-governance/skills/cabloy-worktree-environment/SKILL.md

@@ -29,10 +29,10 @@ Before proposing configuration values or writing files:
 
 Interpretation:
 
-| Marker                  | Edition      | Managed clean E2E command |
-| ----------------------- | ------------ | ------------------------- |
-| `__CABLOY_BASIC__` only | Cabloy Basic | `npm run test:e2e`        |
-| `__CABLOY_START__` only | Cabloy Start | `npm run test:e2e`        |
+| Marker                  | Edition      | Managed E2E command |
+| ----------------------- | ------------ | ------------------- |
+| `__CABLOY_BASIC__` only | Cabloy Basic | `npm run test:e2e`  |
+| `__CABLOY_START__` only | Cabloy Start | `npm run test:e2e`  |
 
 Stop without edits when both markers are present, neither marker is present, the checkout is primary/unregistered, required environment directories are missing, or the selected edition's required scripts are unavailable.
 
@@ -178,7 +178,7 @@ npm run dev:zova:web
 npm run test
 ```
 
-Run the edition-appropriate managed clean E2E command:
+Run the edition-appropriate managed E2E command:
 
 ```bash
 # Cabloy Basic or Cabloy Start

package/repo-docs/demo.md

@@ -10,3 +10,17 @@ Explore the Cabloy demonstration sites:
 | ---------- | ---------------------------------------------------------------- |
 | Web site   | [https://demo.cabloy.com/](https://demo.cabloy.com/)             |
 | Admin site | [https://demo.cabloy.com/admin/](https://demo.cabloy.com/admin/) |
+
+## Videos
+
+### 1. Can an Admin Site Use SSR? CabloyJS in Three Practical Demos (Duration: 1:16)
+
+[![CabloyJS Admin SSR video](./assets/img/cabloy-admin-ssr-cover-en.png)](https://youtu.be/786IQhRdr1I)
+
+### 2. A First: Second-Level Tabs for Admin Multitasking (Duration: 1:50)
+
+[![CabloyJS Admin Tabs video](./assets/img/cabloy-admin-tabs-cover-en.png)](https://youtu.be/L6DxD-JfztQ)
+
+### 3. AI Coding in Action: One Prompt for CRUD, SSR & Multitasking (Duration: 3:50)
+
+[![CabloyJS AI CRUD video](./assets/img/cabloy-ai-crud-cover-en.png)](https://youtu.be/PV9_By08hDM)

package/repo-docs/frontend/scripts.md

@@ -68,23 +68,16 @@ npm run deps:vona
 npm run test:e2e cabloy-basic home-user-account
 ```
 
-The managed clean command resets Vona-managed test data and the local Redis namespace, starts one development Vona worker, and runs the selected specs. Browser commands consume already-built artifacts; they do not rebuild them.
-
-The unified runner uses two commands:
-
-```text
-npm run test:e2e                 clean local run with database reset
-npm run test:e2e:fast            fast run without automatic reset
-```
+The sole managed `npm run test:e2e` command starts a fresh local Vona worker with `--workers=1 --flavor=normal --mode=test`, then runs the selected specs against Vona integrated SSR. Test-mode startup initializes test resources without a separate `db:reset`; browser commands consume already-built artifacts and do not rebuild them. Confirm exclusive ownership of the effective test database, `_local` Redis namespace, public/runtime paths, `APP_NAME`, API origin, and listener before startup; a free port alone is insufficient.
 
 Place flat spec basenames directly after the npm script name. Use npm's `--` delimiter before Playwright options. With no names, every spec in `repo-e2e/specs` runs. Native `--grep` and `--grep-invert` remain available, and repeatable `--tag` values require all listed tags:
 
 ```bash
 npm run test:e2e cabloy-basic home-user-account -- --grep @flow
-npm run test:e2e:fast a-commerce -- --tag @web --tag @smoke
+npm run test:e2e a-commerce -- --tag @web --tag @smoke
 ```
 
-For the complete tag vocabulary, managed-runner argument boundaries, and externally managed-target examples, see [Repo Scripts](/reference/repo-scripts#ssr-browser-checks). A separately managed target uses `E2E_BASE_URL` with `test:e2e:fast`; the caller owns external-target data, cache, and artifact freshness.
+For the complete Basic tag vocabulary and managed-runner argument boundaries, see [Repo Scripts](/reference/repo-scripts#ssr-browser-checks). `E2E_BASE_URL` must be unset: externally managed targets are unsupported.
 
 ## Cabloy Start root wrappers
 
@@ -102,7 +95,7 @@ Cabloy Start does not expose the Basic Commerce wrapper family.
 
 ## Start SSR browser acceptance
 
-The Start Web and Admin browser baseline also exercises Vona SSR dispatch at the effective local server port. Prepare current SSR and REST artifacts, then use the managed local command:
+The Start Web and Admin browser baseline exercises Vona integrated SSR dispatch at the effective local test-mode server port. Prepare current SSR and REST artifacts, then use the managed local command:
 
 ```bash
 npm run build:zova
@@ -110,23 +103,22 @@ npm run deps:vona
 npm run test:e2e
 ```
 
-Start uses the same unified E2E command pair as Basic:
+Start uses one E2E command and one fresh managed local test-mode lifecycle:
 
 ```text
-npm run test:e2e       managed clean local suite run
-npm run test:e2e:fast  fast rerun without an automatic reset
+npm run test:e2e       fresh managed local test-mode suite run
 ```
 
 Select flat spec basenames and filter scenarios or surfaces with runner tags and native Playwright arguments. Current Start scenarios use tags including `@web`, `@admin`, `@smoke`, `@layout`, `@cabloy-admin`, `@account`, `@ssr`, and `@flow`:
 
 ```bash
 npm run test:e2e cabloy-start
-npm run test:e2e:fast cabloy-start -- --tag @web
-npm run test:e2e:fast cabloy-admin -- --tag @admin --tag @cabloy-admin
-npm run test:e2e:fast cabloy-start -- --grep ATP-START-FLOW-01
+npm run test:e2e cabloy-start -- --tag @web
+npm run test:e2e cabloy-admin -- --tag @admin --tag @cabloy-admin
+npm run test:e2e cabloy-start -- --grep ATP-START-FLOW-01
 ```
 
-For a separately managed Start target, set `E2E_BASE_URL` and use `test:e2e:fast`. The target owner is responsible for data, cache, artifact freshness, and process lifecycle.
+Start does not support externally managed E2E targets: `E2E_BASE_URL` must be unset. The command requires the configured local port to be available and starts one Vona worker with `--flavor=normal --mode=test`; Playwright does not reuse an existing process. Test-mode startup initializes test state. Confirm exclusive ownership of the test database, Redis namespace, and public/runtime paths before running it. The command does not replace the paired build/dependency-sync prerequisite; do not change shared environment identity or ports to avoid a busy resource.
 
 ## Zova script model
 

package/repo-docs/fullstack/parallel-worktree-environment.md

@@ -77,12 +77,12 @@ For privacy, the skill writes only to absent or empty permitted broad local file
 
 Use commands from the active repository root.
 
-| Edition      | Marker             | Frontend command                                   | Managed clean E2E  |
+| Edition      | Marker             | Frontend command                                   | Managed E2E        |
 | ------------ | ------------------ | -------------------------------------------------- | ------------------ |
 | Cabloy Basic | `__CABLOY_BASIC__` | `npm run dev:zova:admin` or `npm run dev:zova:web` | `npm run test:e2e` |
 | Cabloy Start | `__CABLOY_START__` | `npm run dev:zova:admin` or `npm run dev:zova:web` | `npm run test:e2e` |
 
-Run one frontend command, not both, in each worktree. Both managed clean E2E workflows read Vona's effective local `SERVER_LISTEN_PORT`, then reset, start, and target that local runtime.
+Run one frontend command, not both, in each worktree. Both managed E2E workflows read Vona's effective local `SERVER_LISTEN_PORT` and start one fresh Vona test-mode worker; startup initializes test resources without a separate reset. Before either command, confirm exclusive ownership of the effective test database, `_local` Redis namespace, public/runtime paths, `APP_NAME`, API origin, and listener. A free port alone does not establish ownership. Do not change shared identity or ports to bypass a collision, and leave `E2E_BASE_URL` unset: externally managed targets are unsupported.
 
 ## What this isolates
 

package/repo-docs/index.md

@@ -32,9 +32,9 @@ features:
 
 ## Demonstrations(Videos)
 
-### 1. Can an Admin Site Use SSR? CabloyJS in Three Practical Demos (Duration: 1:16)
+### 1. AI Coding in Action: One Prompt for CRUD, SSR & Multitasking (Duration: 3:50)
 
-[![CabloyJS Admin SSR video](./assets/img/cabloy-admin-ssr-cover-en.png)](https://youtu.be/786IQhRdr1I)
+[![CabloyJS AI CRUD video](./assets/img/cabloy-ai-crud-cover-en.png)](https://youtu.be/PV9_By08hDM)
 
 ## Choose a reading path
 

package/repo-docs/reference/repo-scripts.md

@@ -40,9 +40,7 @@ Cabloy Basic exposes these shared root scripts:
 - `npm run start`
 - `npm run start:one`
 - `npm run test`
-- `npm run db:reset`
 - `npm run test:e2e`
-- `npm run test:e2e:fast`
 - `npm run tsc`
 - `npm run docs:dev`
 - `npm run docs:build`
@@ -117,7 +115,6 @@ Cabloy Start exposes the equivalent Start repository surface:
 - `npm run test`
 - `npm run db:reset`
 - `npm run test:e2e`
-- `npm run test:e2e:fast`
 - `npm run tsc`
 
 Cabloy Start does not expose Basic Commerce or root documentation wrappers.
@@ -138,7 +135,7 @@ repo-e2e/specs/home-user-account.spec.ts
 repo-e2e/specs/a-commerce.spec.ts
 ```
 
-It also reconciles the two framework E2E scripts and the `@playwright/test` development dependency. Keep additional project browser specs under other filenames in `repo-e2e/specs`; the upgrader updates only the listed framework files. The current fresh baseline is required and is not repaired for unsupported legacy project layouts.
+It reconciles the single framework-owned `test:e2e` script and the `@playwright/test` development dependency. The retired `test:e2e:fast` script is removed only if its value matches the known old framework command; a customized project alias is preserved. Keep additional project browser specs under other filenames in `repo-e2e/specs`; the upgrader updates only the listed framework files. The current fresh baseline is required and is not repaired for unsupported legacy project layouts.
 
 ### Cabloy Start repository
 
@@ -154,31 +151,28 @@ The public-package upgrade flow does not source or reconcile the Start-owned bas
 
 ## SSR browser checks
 
-The unified runner has two modes:
-
-- `npm run test:e2e`: clean local run; checks the managed Vona port, resets the database, starts one development Vona worker, and runs Playwright.
-- `npm run test:e2e:fast`: skips the reset for quick reruns and may target either the local managed Vona server or an externally managed `E2E_BASE_URL`.
+Cabloy Basic and Cabloy Start each use a single managed local `npm run test:e2e` command. In Basic, the runner checks the effective `normal/test/local` Vona listener port and starts one fresh `--workers=1 --flavor=normal --mode=test` worker. Test-mode startup initializes test resources; the runner does not invoke a separate `db:reset` or a development-mode server. Playwright does not reuse an existing process. Confirm exclusive ownership of the effective test database, `_local` Redis namespace, public/runtime paths, `APP_NAME`, API origin, and listener before starting it; port availability alone is insufficient.
 
-These browser checks target Vona integrated SSR. In the Cabloy Basic default environment, the Vona listener is `7102`; the Zova standalone SSR development server uses `9000` and is not an acceptance target.
+Both editions' browser checks target Vona integrated SSR. In the Cabloy Basic default environment, the Vona listener is `7102`; the Zova standalone SSR development server uses `9000` and is not an acceptance target.
 
 Place spec basenames directly after the npm script name; use npm's `--` delimiter only before Playwright options. Multiple spec names are allowed. With no names, every spec in `repo-e2e/specs` is discovered:
 
 ```bash
 npm run test:e2e cabloy-basic home-user-account
 npm run test:e2e a-commerce
-npm run test:e2e:fast home-user-account
-npm run test:e2e:fast a-commerce -- --grep ATP-SSR
-npm run test:e2e:fast a-commerce -- --grep-invert @admin
+npm run test:e2e home-user-account
+npm run test:e2e a-commerce -- --grep ATP-SSR
+npm run test:e2e a-commerce -- --grep-invert @admin
 ```
 
 Tags remain independent from filenames. Repeat `--tag` to require all tags, while native `--grep` and `--grep-invert` remain available:
 
 ```bash
-npm run test:e2e:fast a-commerce -- --tag @web --tag @smoke
-npm run test:e2e:fast home-user-account -- --grep @flow --tag @web
+npm run test:e2e a-commerce -- --tag @web --tag @smoke
+npm run test:e2e home-user-account -- --grep @flow --tag @web
 ```
 
-The existing tags include `@web`, `@admin`, `@smoke`, `@flow`, `@ssr`, `@theme`, and the business tags used by Commerce such as `@cart`, `@payment`, `@shipment`, and `@refund`. No suite tag is required. Clean runs are local-only and reject `E2E_BASE_URL`; fast runs against an external target do not reset, start, stop, or rebuild that target.
+The existing Basic tags include `@web`, `@admin`, `@smoke`, `@flow`, `@ssr`, `@theme`, and the business tags used by Commerce such as `@cart`, `@payment`, `@shipment`, and `@refund`. No suite tag is required. In Cabloy Basic, `E2E_BASE_URL` must be unset: external targets and a fast/no-reset mode are unsupported.
 
 ### Cabloy Basic and Commerce
 
@@ -198,15 +192,9 @@ npm run deps:vona
 npm run test:e2e a-commerce
 ```
 
-For a separately managed target, use the fast command:
-
-```bash
-E2E_BASE_URL=http://127.0.0.1:7102 npm run test:e2e:fast a-commerce -- --tag @smoke
-```
-
 ### Cabloy Start
 
-The Start suite exercises Web at `/` and Admin at `/admin` through Vona integrated SSR dispatch. Prepare current Start artifacts before a managed local run:
+The Start suite exercises Web at `/` and Admin at `/admin` through Vona integrated SSR dispatch. Prepare current Start artifacts before a managed local run. The runner uses the effective local `normal`-flavor, test-mode Vona listener, rather than assuming a fixed port:
 
 ```bash
 npm run build:zova
@@ -216,20 +204,16 @@ npm run test:e2e
 
 ```bash
 # Exact acceptance scenario
-npm run test:e2e:fast cabloy-start -- --grep ATP-START-FLOW-01
+npm run test:e2e cabloy-start -- --grep ATP-START-FLOW-01
 
 # Category or surface selection
-npm run test:e2e:fast cabloy-start -- --tag @smoke
-npm run test:e2e:fast cabloy-admin -- --tag @admin --tag @cabloy-admin
+npm run test:e2e cabloy-start -- --tag @smoke
+npm run test:e2e cabloy-admin -- --tag @admin --tag @cabloy-admin
 ```
 
-For an externally managed Start target, set `E2E_BASE_URL` and use `npm run test:e2e:fast`. The target owner is responsible for data, cache, artifact freshness, and process lifecycle:
+In Cabloy Start, the sole `npm run test:e2e` command checks the configured local port and starts a fresh runner-managed Vona target with `--workers=1 --flavor=normal --mode=test`. Playwright never reuses an existing server. Test-mode startup initializes test resources; the runner does not invoke a separate `db:reset`. Confirm ownership of the test database, Redis namespace, and public/runtime paths before running it; do not change shared environment identity or ports to bypass a busy resource.
 
-```bash
-E2E_BASE_URL=http://127.0.0.1:7102 npm run test:e2e:fast
-E2E_BASE_URL=http://127.0.0.1:7102 npm run test:e2e:fast cabloy-admin -- --tag @admin
-E2E_BASE_URL=http://127.0.0.1:7102 npm run test:e2e:fast cabloy-start -- --tag @web
-```
+`E2E_BASE_URL` is unsupported in Cabloy Start and must be unset, even for a local URL. Externally managed targets are not supported.
 
 Browser commands consume existing SSR and REST artifacts; they never rebuild them. Install Chromium once when needed with `npx playwright install chromium`.
 

package/repo-e2e/config/playwright.config.ts

@@ -2,9 +2,6 @@ import { defineConfig } from '@playwright/test';
 
 import { E2E_LOCAL_BASE_URL, E2E_ROOT_DIR } from '../scripts/e2e.ts';
 
-const externalBaseURL = process.env.E2E_BASE_URL;
-const baseURL = externalBaseURL || E2E_LOCAL_BASE_URL;
-
 export default defineConfig({
   testDir: `${E2E_ROOT_DIR}/repo-e2e/specs`,
   fullyParallel: false,
@@ -13,22 +10,20 @@ export default defineConfig({
   retries: process.env.CI ? 2 : 0,
   reporter: process.env.CI ? [['html', { open: 'never' }], ['list']] : 'list',
   use: {
-    baseURL,
+    baseURL: E2E_LOCAL_BASE_URL,
     trace: 'on-first-retry',
   },
-  webServer: externalBaseURL
-    ? undefined
-    : {
-        command: 'node repo-e2e/scripts/startE2eVona.ts',
-        cwd: E2E_ROOT_DIR,
-        url: `${baseURL}/health/ready`,
-        timeout: 180_000,
-        reuseExistingServer: false,
-        stdout: 'pipe',
-        stderr: 'pipe',
-        gracefulShutdown: {
-          signal: 'SIGINT',
-          timeout: 10_000,
-        },
-      },
+  webServer: {
+    command: 'node repo-e2e/scripts/startE2eVona.ts',
+    cwd: E2E_ROOT_DIR,
+    url: `${E2E_LOCAL_BASE_URL}/health/ready`,
+    timeout: 180_000,
+    reuseExistingServer: false,
+    stdout: 'pipe',
+    stderr: 'pipe',
+    gracefulShutdown: {
+      signal: 'SIGINT',
+      timeout: 10_000,
+    },
+  },
 });

package/repo-e2e/scripts/e2e.test.ts

@@ -0,0 +1,17 @@
+import assert from 'node:assert/strict';
+import { spawnSync } from 'node:child_process';
+import test from 'node:test';
+import { fileURLToPath } from 'node:url';
+
+test('rejects a defined E2E_BASE_URL before loading local configuration', () => {
+  const entrypoint = fileURLToPath(new URL('./e2e.ts', import.meta.url));
+  for (const value of ['', 'http://127.0.0.1:7102']) {
+    const result = spawnSync(process.execPath, [entrypoint], {
+      env: { ...process.env, E2E_BASE_URL: value },
+      encoding: 'utf8',
+    });
+    assert.notEqual(result.status, 0);
+    assert.match(result.stderr, /E2E_BASE_URL is unsupported/);
+    assert.doesNotMatch(result.stderr, /SERVER_LISTEN_PORT/);
+  }
+});

package/repo-e2e/scripts/e2e.ts

@@ -4,8 +4,12 @@ import { fileURLToPath } from 'node:url';
 
 export const E2E_ROOT_DIR = resolve(dirname(fileURLToPath(import.meta.url)), '..', '..');
 
+if (process.env.E2E_BASE_URL !== undefined) {
+  throw new Error('E2E_BASE_URL is unsupported; the E2E runner manages a local test-mode target.');
+}
+
 const vonaEnv = dotenv.loadEnvs(
-  { flavor: 'normal', mode: 'dev', local: 'local' },
+  { flavor: 'normal', mode: 'test', local: 'local' },
   resolve(E2E_ROOT_DIR, 'vona', 'env'),
   '.env',
 );

package/repo-e2e/scripts/runE2e.ts

@@ -34,16 +34,7 @@ async function assertPortAvailable(): Promise<void> {
 }
 
 const parsed = parseE2eArgs(process.argv.slice(2), E2E_SPECS_DIR);
-if (parsed.mode === 'clean' && process.env.E2E_BASE_URL) {
-  throw new Error(
-    'The clean E2E run manages the local target and cannot be used with E2E_BASE_URL. Use test:e2e:fast for an external target.',
-  );
-}
-
-if (parsed.mode === 'clean') {
-  await assertPortAvailable();
-  run('npm', ['run', 'db:reset']);
-}
+await assertPortAvailable();
 
 const playwrightCommand = resolve(
   E2E_ROOT_DIR,
@@ -55,8 +46,5 @@ const specPaths = parsed.specNames.map(name => resolve(E2E_SPECS_DIR, `${name}.s
 const playwrightArgs = combineGreps(parsed.playwrightArgs, parsed.tags);
 run(playwrightCommand, ['test', '--config', E2E_CONFIG_FILE, ...specPaths, ...playwrightArgs]);
 
-// Keep this value referenced in the runner's startup output and make the local target explicit.
-if (!process.env.E2E_BASE_URL) {
-  // eslint-disable-next-line no-console
-  console.log(`E2E target: ${E2E_LOCAL_BASE_URL}`);
-}
+// eslint-disable-next-line no-console
+console.log(`E2E target: ${E2E_LOCAL_BASE_URL}`);