viepilot 2.45.4 → 2.45.6

package/CHANGELOG.md

@@ -7,6 +7,28 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.45.6] - 2026-04-27
+
+### Fixed
+- **BUG-026**: `vp-brainstorm` internal session sub-commands (`/save`, `/research-ui`,
+  `/review-arch`, `/sync-ui`) conflicted with Claude Code's `/` command prefix —
+  typed as slash commands they were intercepted as unknown skill invocations.
+  Fix: removed all slash sub-command documentation; replaced with proactive AUQ
+  triggers that fire on intent detection (multi-language save signals: "save",
+  "done", "xong", "lưu"; UI walkthrough offered on research intent; arch review
+  offered on review intent). Consistent behavior across ALL adapters — no
+  adapter-specific typing rules (BUG-026)
+
+## [2.45.5] - 2026-04-27
+
+### Enhanced
+- **ENH-078**: `npx viepilot install` now prompts users to select their preferred
+  communication language (the language ViePilot uses for banners and AI prompts)
+  via keyboard selector or numbered-list fallback; chosen language written to
+  `~/.viepilot/config.json → language.communication`; supports 10 languages
+  (en, vi, fr, ja, de, es, zh, ko, pt, id); `--yes` mode skips prompt and
+  defaults to `en` (ENH-078)
+
 ## [2.45.4] - 2026-04-27
 
 ### Fixed

package/bin/viepilot.cjs

@@ -17,6 +17,19 @@ const { buildInstallPlan, applyInstallPlan, resolveViepilotPackageRoot } = requi
 const { adapters: adapterMap } = require(path.join(__dirname, '..', 'lib', 'adapters', 'index.cjs'));
 
 // UI target list — keep cursor-agent and cursor-ide as distinct choices for users.
+const LANGUAGES = [
+  { id: 'en', label: 'English (en)' },
+  { id: 'vi', label: 'Vietnamese — Tiếng Việt (vi)' },
+  { id: 'fr', label: 'French — Français (fr)' },
+  { id: 'ja', label: 'Japanese — 日本語 (ja)' },
+  { id: 'de', label: 'German — Deutsch (de)' },
+  { id: 'es', label: 'Spanish — Español (es)' },
+  { id: 'zh', label: 'Chinese Simplified — 中文 (zh)' },
+  { id: 'ko', label: 'Korean — 한국어 (ko)' },
+  { id: 'pt', label: 'Portuguese — Português (pt)' },
+  { id: 'id', label: 'Indonesian — Bahasa Indonesia (id)' },
+];
+
 const TARGETS = [
   { id: 'claude-code',  label: adapterMap['claude-code'].name + ' (default)' },
   { id: 'cursor-agent', label: 'Cursor Agent' },
@@ -235,6 +248,19 @@ function ask(question) {
   });
 }
 
+async function interactiveLanguageSelection() {
+  if (!process.stdin.isTTY || !process.stdout.isTTY) {
+    console.log('\nSelect communication language (ViePilot banners and prompts):');
+    LANGUAGES.forEach((l, idx) => console.log(`  ${idx + 1}. ${l.label}`));
+    const answer = await ask('Language [1 = English]: ');
+    const idx = parseInt(answer, 10);
+    const lang = LANGUAGES[Number.isInteger(idx) && idx >= 1 && idx <= LANGUAGES.length ? idx - 1 : 0];
+    return lang.id;
+  }
+  const selected = await runKeyboardSelector(LANGUAGES, 'single', 'Select communication language');
+  return (selected && selected[0]) || 'en';
+}
+
 async function interactiveTargetSelection() {
   if (!process.stdin.isTTY || !process.stdout.isTTY) {
     console.log('\nSelect install targets (comma-separated numbers):');
@@ -261,7 +287,7 @@ async function interactiveTargetSelection() {
  * @param {boolean} dryRun
  * @returns {{ ok: boolean, code: number }}
  */
-function runInstallViaNode(selectedTargets, dryRun) {
+function runInstallViaNode(selectedTargets, dryRun, communicationLang = 'en') {
   const fallbackRoot = path.join(__dirname, '..');
   const pkgRoot = resolveViepilotPackageRoot(fallbackRoot) || fallbackRoot;
   const profile = selectedTargets[0] || 'claude-code';
@@ -269,6 +295,7 @@ function runInstallViaNode(selectedTargets, dryRun) {
     ...process.env,
     VIEPILOT_AUTO_YES: '1',
     VIEPILOT_INSTALL_PROFILE: profile,
+    VIEPILOT_COMM_LANG: communicationLang,
   };
   const wantPathShim = env.VIEPILOT_ADD_PATH === '1';
 
@@ -328,8 +355,14 @@ async function installCommand(rawArgs) {
     }
   }
 
+  let communicationLang = 'en';
+  if (!options.yes) {
+    communicationLang = await interactiveLanguageSelection();
+  }
+
   console.log(`\nSelected targets: ${selectedTargets.join(', ')}`);
-  const run = runInstallViaNode(selectedTargets, options.dryRun);
+  console.log(`Communication language: ${communicationLang}`);
+  const run = runInstallViaNode(selectedTargets, options.dryRun, communicationLang);
   const results = selectedTargets.map((target) => ({
     ok: run.ok,
     target,

package/lib/viepilot-install.cjs

@@ -29,6 +29,7 @@ function normalizeInstallEnv(envSource = process.env) {
     profile: envSource.VIEPILOT_INSTALL_PROFILE || 'claude-code',
     addPath: envSource.VIEPILOT_ADD_PATH === '1',
     symlinkSkills: envSource.VIEPILOT_SYMLINK_SKILLS === '1',
+    communicationLang: envSource.VIEPILOT_COMM_LANG || 'en',
   };
 }
 
@@ -241,9 +242,10 @@ function buildInstallPlan(packageRoot, envSource = process.env, opts = {}) {
     });
   }
 
-  // ENH-032: prompt for language config at end of install
+  // ENH-032 / ENH-078: write selected communication language; lang chosen interactively in CLI
   steps.push({
     kind: 'language_config_prompt',
+    communicationLang: env.communicationLang,
     autoYes: env.autoYes,
     home,
   });
@@ -519,13 +521,13 @@ function applyInstallPlan(plan, options = {}) {
           break;
         }
         case 'language_config_prompt': {
+          const commLang = step.communicationLang ?? 'en';
           if (dryRun) {
-            logs.push(`[dry-run] language_config_prompt: would write ~/.viepilot/config.json with communication=en, document=en`);
+            logs.push(`[dry-run] language_config_prompt: would write ~/.viepilot/config.json with communication=${commLang}, document=en`);
             break;
           }
-          // Write defaults; future interactive installer can prompt here
-          writeConfig({ language: { communication: 'en', document: 'en' } }, step.home);
-          logs.push(`language_config_prompt: wrote ${step.home}/.viepilot/config.json (communication=en, document=en)`);
+          writeConfig({ language: { communication: commLang, document: 'en' } }, step.home);
+          logs.push(`language_config_prompt: wrote ${step.home}/.viepilot/config.json (communication=${commLang}, document=en)`);
           break;
         }
         default:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "viepilot",
-  "version": "2.45.4",
+  "version": "2.45.6",
   "description": "**Autonomous Vibe Coding Framework / Bộ khung phát triển tự động có kiểm soát**",
   "main": "index.js",
   "bin": {

package/skills/vp-brainstorm/SKILL.md

@@ -63,6 +63,19 @@ Prompt user conversationally with numbered list options.
 
 ## C. Tool Usage
 Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
+
+## D. Session Actions — Proactive AUQ Triggers (BUG-026)
+**No slash sub-commands.** All session actions are triggered proactively by the AI via
+`AskUserQuestion` at the right moment — no user typing required.
+
+| Action | Trigger condition | AUQ prompt |
+|--------|-------------------|------------|
+| **Save + crystallize handoff** | User signals done: "save", "done", "xong", "lưu", "finished", "ready", "crystallize", or equivalent intent | "Save session and prepare for /vp-crystallize?" |
+| **UX walkthrough** | In UI session AND user mentions "research", "test", "UX", "walkthrough" — OR ≥1 UI signals accumulated | "Run UX walkthrough (3-phase simulate + research + update HTML)?" |
+| **Architecture review** | User asks "review decisions", "check arch", "summarize choices", or equivalent intent | "Generate architecture review summary table?" |
+| **Sync UI → Arch** | After arch update when UI workspace also active | "Sync architecture changes to UI Direction workspace?" |
+
+**Why:** In Claude Code terminal, any `/command` is intercepted by the shell as a skill invocation. Using proactive AUQ triggers works identically on ALL adapters — no adapter-specific typing rules needed.
 </cursor_skill_adapter>
 <scope_policy>
 ## ViePilot Namespace Guard (BUG-004)
@@ -90,15 +103,15 @@ Supports:
 - UI Direction mode: create/update HTML prototype + notes under `.viepilot/ui-direction/{session-id}/` — supports **multi-page** (`pages/{slug}.html` + hub `index.html`) and the **`## Pages inventory`** hook in `notes.md` when `pages/` exists (FEAT-007)
 - **Phase assignment (ENH-030):** in every session, features/capabilities are assigned directly to Phase 1, Phase 2, Phase 3... — no MVP/Post-MVP/Future tiers. Session file stores assignments in the `## Phases` section.
 - **Project meta intake (FEAT-009):** after **scope locked**, **before** `Completed` / `/end`, if `.viepilot/META.md` (`viepilot_profile_id`) is missing — run **sequential** Q&A with proposals; read/write `~/.viepilot/profile-map.md`; create `~/.viepilot/profiles/<slug>.md` + binding per **`docs/dev/global-profiles.md`**. If a profile is already bound — skip intake by default (ask if change needed).
-- **UX walkthrough (FEAT-010 + ENH-019 + ENH-020):** in **`--ui`** mode, command **`/research-ui`** or **`/research ui`** runs 3 phases — simulates **end-user** (with **content stress pass** + **stress recipes by archetype** → **Stress findings**) → **UX designer + web research** → update `index.html` / `pages/*.html` / `style.css` and write **`## UX walkthrough log`** in `notes.md` (sync hub + **Pages inventory** for multi-page).
-- **Background UI extraction (ENH-026 + ENH-060):** automatically detects UI signal keywords in every brainstorm session (no `--ui` flag required). **Auto-suggests itself (ENH-060):** if the initial message contains ≥1 UI keyword, shows a proactive 🎨 banner immediately — mirrors Architect Design Mode's 🏗️ proactive activation. Accumulation starts at ≥1 signal (was ≥3); surfaces for confirmation when topic ends, `/save`, or **≥2 unique signals** accumulated (was ≥5) — does not interrupt the main conversation.
-- **Idea → Architecture breakdown loop (ENH-061):** structured 8-step flow from free idea collection → scope lock → **Feature → Coverage mapping** (maps each Phase 1 feature to an architect page + UI screen, outputs `## Coverage` matrix in `notes.md`) → Architect Design → **`arch_to_ui_sync`** reverse sync (surfaces UI implications of architectural decisions; `/sync-ui` command) → UI Direction → **completeness gate** (CHECK 4: warns if any Phase 1 feature has no coverage in either mode, non-blocking). See `Recommended Breakdown Ordering` section in `workflows/brainstorm.md`.
+- **UX walkthrough (FEAT-010 + ENH-019 + ENH-020):** in **`--ui`** mode, proactively offered via AUQ when user mentions "research", "test UX", "walkthrough" — or when ≥1 UI signals accumulated. Runs 3 phases: simulates **end-user** (with **content stress pass** + **stress recipes by archetype** → **Stress findings**) → **UX designer + web research** → update `index.html` / `pages/*.html` / `style.css` and write **`## UX walkthrough log`** in `notes.md` (sync hub + **Pages inventory** for multi-page).
+- **Background UI extraction (ENH-026 + ENH-060):** automatically detects UI signal keywords in every brainstorm session (no `--ui` flag required). **Auto-suggests itself (ENH-060):** if the initial message contains ≥1 UI keyword, shows a proactive 🎨 banner immediately — mirrors Architect Design Mode's 🏗️ proactive activation. Accumulation starts at ≥1 signal (was ≥3); surfaces for confirmation when topic ends, user signals done, or **≥2 unique signals** accumulated (was ≥5) — does not interrupt the main conversation.
+- **Idea → Architecture breakdown loop (ENH-061):** structured 8-step flow from free idea collection → scope lock → **Feature → Coverage mapping** (maps each Phase 1 feature to an architect page + UI screen, outputs `## Coverage` matrix in `notes.md`) → Architect Design → **`arch_to_ui_sync`** reverse sync (surfaces UI implications of architectural decisions; proactively offered via AUQ after arch updates) → UI Direction → **completeness gate** (CHECK 4: warns if any Phase 1 feature has no coverage in either mode, non-blocking). See `Recommended Breakdown Ordering` section in `workflows/brainstorm.md`.
 - **Unified workspace mode selection (BUG-018):** after scope lock, before any design workspace is created, an AUQ prompt offers: Both / Architect only / UI Direction only / Neither. Architect auto-activate heuristic is deferred until after this selection; suppressed if user selects "Neither" or "UI Direction only".
 - **Admin & Governance coverage (ENH-063):** Topic 6 in brainstorm template; proactive 🔐 heuristic fires on admin/governance keywords; admin coverage gate before /save for multi-user/SaaS/compliance projects; `admin.html` added to Architect workspace when applicable; `notes.md ## admin` YAML exported via crystallize.
 - **Content Management coverage (ENH-065):** Topic 7 in brainstorm template; proactive 🗂️ heuristic fires on content-type/media/SEO keywords; content coverage gate before /save for projects with content layer; `content.html` added to Architect workspace; `notes.md ## content` YAML exported via crystallize.
 - **Admin Entity Management coverage (ENH-068):** Topic 7 in brainstorm template; proactive 🗄️ heuristic fires on CRUD/entity/admin panel keywords; entity management coverage gate before /save for projects with DB entities (cross-references ERD); `entity-mgmt.html` added to Architect workspace; `notes.md ## entity_mgmt` YAML exported via crystallize.
 - **User Data Management coverage (ENH-066):** Topic 9 in brainstorm template; proactive 👤 heuristic fires on user-account/privacy/auth keywords; user data coverage gate before /save for B2C/SaaS/GDPR projects; `user-data.html` added to Architect workspace; `notes.md ## user_data` YAML exported via crystallize.
-- **Architect Design Mode (FEAT-011):** `/vp-brainstorm --architect` or auto-activate when ≥3 components/services detected; generate HTML workspace (architecture, data-flow, decisions, tech-stack, tech-notes, feature-map) with Mermaid diagrams; incremental update per decision; `/review-arch` command; machine-readable `notes.md` YAML schema.
+- **Architect Design Mode (FEAT-011):** `/vp-brainstorm --architect` or auto-activate when ≥3 components/services detected; generate HTML workspace (architecture, data-flow, decisions, tech-stack, tech-notes, feature-map) with Mermaid diagrams; incremental update per decision; architecture review offered via AUQ when user asks to review decisions; machine-readable `notes.md` YAML schema.
 - **ERD page (ENH-027):** Architect workspace includes `erd.html` — Mermaid `erDiagram`, entity list table, relationship summary; triggered by DB/entity/table/relationship keywords; notes.md `## erd` YAML section exported to ARCHITECTURE.md `## Database Schema` via crystallize Step 1D.
 - **User Use Cases page (ENH-028):** Architect workspace includes `user-use-cases.html` — actor/use-case diagram (Mermaid flowchart), use case table; triggered by user/role/actor/story keywords; notes.md `## use_cases` YAML section exported to PROJECT-CONTEXT.md `## User Stories & Use Cases` via crystallize Step 1D.
 - **C4Context/Sequence/Deployment/APIs pages (ENH-029, 12-page workspace):** Architect workspace expanded to 12 pages — `sequence-diagram.html` (per-scenario sequenceDiagram), `deployment.html` (infra graph + environments + CI/CD pipeline), `apis.html` (endpoint tables with HTTP method badges); page boundary rules table; trigger keywords for sequence/deploy/API; notes.md `## apis` YAML section; deployment+APIs exported to ARCHITECTURE.md via crystallize Step 1D (sequence excluded — scenario docs are not architecture artifacts).

package/workflows/brainstorm.md

@@ -1178,7 +1178,7 @@ When the user mentions: `user story`, `use case`, `actor`, `persona`, `as a user
 
 1. After each **major decision** (tech stack, service boundary, data model) → update the related HTML section + update `notes.md`.
 2. When the user **changes a decision** → **incremental update**: only edit the related section; keep all other sections unchanged. Add `data-updated="true"` attribute + class `.updated` CSS highlight (yellow left border + "updated" badge) to the changed element.
-3. **`/review-arch`** command → ViePilot outputs a summary table of all `decisions` (from `notes.md`) + list of `open_questions` with status; ask the user to confirm before continuing.
+3. **Architecture review trigger** — when user asks to review decisions ("review", "check architecture", "summarize choices", "what did we decide", or equivalent intent): ViePilot proactively outputs a summary table of all `decisions` (from `notes.md`) + list of `open_questions` with status, then asks the user to confirm before continuing. **Claude Code (terminal) — REQUIRED:** use `AskUserQuestion` to offer the review; text fallback on other adapters.
 
 #### Incremental update rule
 
@@ -1457,8 +1457,8 @@ This mirrors **Architect Design Mode** which proactively banners when system arc
 
 #### Surface triggers (when to ask the user)
 Display a confirmation dialogue when any of the following conditions occur:
-- (a) **Topic ends** — user types `/topic` to switch to a new topic or says "next"
-- (b) **User types `/save` or `/review`**
+- (a) **Topic ends** — user says "next", "next topic", or switches subject
+- (b) **User signals session end** — says "save", "done", "xong", "finished", "ready", "crystallize", "ready for crystallize", or equivalent intent in any language
 - (c) **≥2 unique signals accumulated** in the buffer
 
 #### Confirmation dialogue template
@@ -1490,12 +1490,16 @@ mkdir -p .viepilot/ui-direction/{session-id}
 
 ### UI Direction — UX walkthrough & upgrade (FEAT-010)
 
-When inside **`/vp-brainstorm --ui`** or a `.viepilot/ui-direction/{session-id}/` already exists for the current session, the user can invoke:
+When inside **`/vp-brainstorm --ui`** or a `.viepilot/ui-direction/{session-id}/` already exists for the current session, the UX walkthrough pipeline is **proactively triggered via AUQ** (BUG-026) when:
+- User mentions "research", "test", "UX review", "walkthrough", "simulate user", or equivalent intent
+- OR: ≥1 UI signal accumulated AND user signals topic end
 
-- **`/research-ui`** — runs the full pipeline below
-- **`/research ui`** — **alias** of `/research-ui` (space after `research`; does not conflict with `/research {free topic}`)
+**Claude Code (terminal) — REQUIRED:** Call `AskUserQuestion`:
+- question: "Run UX walkthrough? (3-phase: simulate user → UX research → update HTML)"
+- header: "UX Walkthrough"
+- options: [{ label: "Yes — run full walkthrough (Recommended)", description: "Simulate end-user + content stress + research + update prototype" }, { label: "Skip for now", description: "Continue brainstorm; offer again at session end" }]
 
-The user can include one line of context (e.g., product name **Trips**, persona, priority flow) — entered in the same message as the command.
+The user can include one line of context (e.g., product name, persona, priority flow) — in the same message or as a follow-up after selecting "Yes".
 
 Apply **the phases sequentially** (assistant does not skip a phase unless the user explicitly says “phase 1 only”):
 
@@ -1623,6 +1627,23 @@ After intake is **completed** or a **valid skip** (META already has profile) →
 <step name="save_session">
 ## 6. Save Session
 
+### Save Trigger (BUG-026)
+
+The save step fires when the AI detects session-end intent — **no slash command required**.
+
+**Save intent signals** (any language):
+- "save", "done", "finished", "ready", "crystallize", "ready for crystallize", "let's save", "that's it", "wrap up"
+- Equivalent phrases in the session language (e.g. "xong", "luu", or any clear session-end signal)
+- Or: conversation reaches natural end (all topics covered, no new questions)
+
+**Claude Code (terminal) — REQUIRED:** Call `AskUserQuestion`:
+- question: "Save session and prepare for /vp-crystallize?"
+- header: "Save Session"
+- options: [{ label: "Save + prepare for crystallize (Recommended)", description: "Write session file, then offer /vp-crystallize handoff" }, { label: "Continue brainstorming", description: "Not done yet — keep going" }]
+
+On "Save + prepare": proceed to Pre-Save validation below, then write file, then offer crystallize handoff.
+On "Continue brainstorming": resume conversation.
+
 ### Pre-Save Phase Assignment Validation (ENH-052)
 
 Before writing the session file, validate phase assignment completeness:
@@ -1648,7 +1669,7 @@ CHECK 4 (ENH-061): If both Architect workspace AND UI Direction workspace are ac
     1. Assign all features to phases (## Phases section)
     2. Ensure Phase 1 has at least one feature
 
-  Return to the conversation to assign phases, then /save again.
+  Return to the conversation to assign phases, then signal done when ready (e.g. "save" or "xong").
   ```
 - If scope is **not** locked (exploratory session — no feature assignments):
   → **Allow save** with `Status: In Progress` and add advisory note to session file:
@@ -1660,7 +1681,7 @@ CHECK 4 (ENH-061): If both Architect workspace AND UI Direction workspace are ac
   ```
   ⚠️  Coverage gap detected — these Phase 1 features have no Architect or UI coverage:
   - {feature name}
-  Consider running /sync-ui or adding these features to a workspace before /vp-crystallize.
+  Consider asking to sync UI or adding these features to a workspace before /vp-crystallize.
   Proceed with save? (yes / skip coverage for now)
   ```
 - If brownfield stub session (`IS_BROWNFIELD=true`): **skip this gate** — brownfield stubs intentionally have no phases.