@ngocsangairvds/vsaf 4.0.3 → 4.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ngocsangairvds/vsaf",
-  "version": "4.0.3",
+  "version": "4.0.5",
   "description": "README",
   "main": "packages/core/dist/index.js",
   "types": "packages/core/dist/index.d.ts",

package/skills/vds-skill/create-bitbucket-pr/SKILL.md

@@ -14,6 +14,8 @@ Before doing anything, run this check via Bash tool:
 ```bash
 source .claude/skills/_shared/vds-skill/credentials.sh 2>/dev/null
 MISSING=""
+{ command -v vds-cli >/dev/null 2>&1 || [[ -x .claude/bin/vds-cli ]]; } || MISSING="$MISSING vds-cli"
+[[ -x .claude/bin/vds-cli ]] && export PATH=".claude/bin:$PATH"
 [[ -z "${VDS_BITBUCKET_TOKEN:-}" ]] && MISSING="$MISSING VDS_BITBUCKET_TOKEN"
 if [[ -n "$MISSING" ]]; then
   echo "BLOCKED — missing:$MISSING"

package/skills/vds-skill/create-jira-epic/SKILL.md

@@ -14,6 +14,8 @@ Before doing anything, run this check via Bash tool:
 ```bash
 source .claude/skills/_shared/vds-skill/credentials.sh 2>/dev/null
 MISSING=""
+{ command -v vds-cli >/dev/null 2>&1 || [[ -x .claude/bin/vds-cli ]]; } || MISSING="$MISSING vds-cli"
+[[ -x .claude/bin/vds-cli ]] && export PATH=".claude/bin:$PATH"
 [[ -z "${VDS_JIRA_TOKEN:-}" ]] && MISSING="$MISSING VDS_JIRA_TOKEN"
 [[ -z "${VDS_JIRA_PROJECT_DEFAULT:-}" ]] && MISSING="$MISSING VDS_JIRA_PROJECT_DEFAULT"
 if [[ -n "$MISSING" ]]; then

package/skills/vds-skill/install-deps.mjs

@@ -141,17 +141,92 @@ if (missing.length > 0) {
   log('💡', 'Skills will also lazy-prompt at runtime if values are empty.');
 }
 
-// ── Step 4: Check vds-cli ──
+// ── Step 4: Check vds-cli + create project-local wrapper ──
 
 console.log('');
+const { execSync } = await import('child_process');
+
+// Detect vds-scripts location (project-local preferred, then global)
+const localVdsScripts = join(projectPath, '.claude', 'vds-scripts');
+const globalVdsScripts = join(homedir(), '.claude', 'vds-scripts');
+const vdsScriptsDir = existsSync(localVdsScripts) ? localVdsScripts
+  : existsSync(globalVdsScripts) ? globalVdsScripts
+  : null;
+
+let vdsCliFound = false;
+
+// Check if vds-cli is already on PATH
 try {
-  const { execSync } = await import('child_process');
   const version = execSync('vds-cli --version', { stdio: 'pipe', encoding: 'utf-8' }).trim();
-  log('✅', `vds-cli ${version}`);
+  log('✅', `vds-cli ${version} (on PATH)`);
+  vdsCliFound = true;
 } catch {
+  // Not on PATH — try to create project-local wrapper
+}
+
+// Create project-local vds-cli wrapper if vds-scripts exists but vds-cli not on PATH
+if (!vdsCliFound && vdsScriptsDir) {
+  const wrapperDir = join(projectPath, '.claude', 'bin');
+  const wrapperPath = join(wrapperDir, 'vds-cli');
+  const uvRunner = join(vdsScriptsDir, 'scripts', 'worktree_uv.sh');
+
+  if (existsSync(uvRunner)) {
+    mkdirSync(wrapperDir, { recursive: true });
+    const wrapperContent = `#!/usr/bin/env bash
+# Project-local vds-cli wrapper — created by vsaf install vds-skill
+# Delegates to worktree_uv.sh in the detected vds-scripts directory.
+set -euo pipefail
+exec "${uvRunner}" run --directory "${vdsScriptsDir}" --package vds-cli vds-cli "$@"
+`;
+    writeFileSync(wrapperPath, wrapperContent, { mode: 0o755 });
+    log('✅', `vds-cli wrapper created: ${wrapperPath}`);
+    log('  ', `Points to: ${vdsScriptsDir}`);
+    log('💡', 'Add to PATH:  export PATH=".claude/bin:$PATH"');
+    vdsCliFound = true;
+  }
+}
+
+if (!vdsCliFound) {
   log('⚠️', 'vds-cli not found — required for non-dry-run execution');
-  log('  ', 'Install vds-scripts from Viettel internal repo, then verify:');
-  log('  ', '  command -v vds-cli && vds-cli --version');
+  log('  ', 'Option 1: Clone vds-scripts into .claude/vds-scripts/ then re-run install');
+  log('  ', 'Option 2: Install vds-cli globally (pip install / Viettel internal)');
+  log('  ', 'Verify:   command -v vds-cli && vds-cli --version');
+}
+
+// ── Step 5: Sync all vds-scripts packages (ensures subcommand binaries exist) ──
+
+if (vdsScriptsDir) {
+  log('📂', `vds-scripts: ${vdsScriptsDir}`);
+  const uvRunner = join(vdsScriptsDir, 'scripts', 'worktree_uv.sh');
+  if (existsSync(uvRunner)) {
+    console.log('');
+    log('🔄', 'Syncing vds-scripts packages (uv sync --all-packages)...');
+    try {
+      execSync(`"${uvRunner}" sync --directory "${vdsScriptsDir}" --all-packages`, {
+        stdio: 'pipe',
+        encoding: 'utf-8',
+        timeout: 120000,
+        cwd: vdsScriptsDir,
+      });
+      log('✅', 'All vds-scripts packages synced');
+    } catch (e) {
+      // Fallback: try direct uv sync
+      try {
+        execSync('uv sync --all-packages', {
+          stdio: 'pipe',
+          encoding: 'utf-8',
+          timeout: 120000,
+          cwd: vdsScriptsDir,
+        });
+        log('✅', 'All vds-scripts packages synced (direct uv)');
+      } catch {
+        log('⚠️', 'Failed to sync vds-scripts packages — subcommands like confluence/jira may not work');
+        log('  ', `Fix: cd ${vdsScriptsDir} && uv sync --all-packages`);
+      }
+    }
+  }
+} else {
+  log('⚠️', 'vds-scripts not found at .claude/vds-scripts/ or ~/.claude/vds-scripts/');
 }
 
 console.log('\n[vds-skill] Setup complete ✅\n');

package/skills/vds-skill/push-prd/SKILL.md

@@ -19,7 +19,8 @@ Before doing anything, run this check via Bash tool:
 ```bash
 source .claude/skills/_shared/vds-skill/credentials.sh 2>/dev/null
 MISSING=""
-command -v vds-cli >/dev/null 2>&1 || MISSING="$MISSING vds-cli"
+{ command -v vds-cli >/dev/null 2>&1 || [[ -x .claude/bin/vds-cli ]]; } || MISSING="$MISSING vds-cli"
+[[ -x .claude/bin/vds-cli ]] && export PATH=".claude/bin:$PATH"
 [[ -z "${VDS_CONFLUENCE_TOKEN:-}" ]] && MISSING="$MISSING VDS_CONFLUENCE_TOKEN"
 [[ -z "${VDS_CONFLUENCE_SPACE_DEFAULT:-}" ]] && MISSING="$MISSING VDS_CONFLUENCE_SPACE_DEFAULT"
 if [[ -n "$MISSING" ]]; then

package/skills/vds-skill/push-srs/SKILL.md

@@ -19,7 +19,8 @@ Before doing anything, run this check via Bash tool:
 ```bash
 source .claude/skills/_shared/vds-skill/credentials.sh 2>/dev/null
 MISSING=""
-command -v vds-cli >/dev/null 2>&1 || MISSING="$MISSING vds-cli"
+{ command -v vds-cli >/dev/null 2>&1 || [[ -x .claude/bin/vds-cli ]]; } || MISSING="$MISSING vds-cli"
+[[ -x .claude/bin/vds-cli ]] && export PATH=".claude/bin:$PATH"
 [[ -z "${VDS_CONFLUENCE_TOKEN:-}" ]] && MISSING="$MISSING VDS_CONFLUENCE_TOKEN"
 [[ -z "${VDS_CONFLUENCE_SPACE_DEFAULT:-}" ]] && MISSING="$MISSING VDS_CONFLUENCE_SPACE_DEFAULT"
 if [[ -n "$MISSING" ]]; then

package/skills/vds-skill/search-confluence/SKILL.md

@@ -14,7 +14,8 @@ Before doing anything, run this check via Bash tool:
 ```bash
 source .claude/skills/_shared/vds-skill/credentials.sh 2>/dev/null
 MISSING=""
-command -v vds-cli >/dev/null 2>&1 || MISSING="$MISSING vds-cli"
+{ command -v vds-cli >/dev/null 2>&1 || [[ -x .claude/bin/vds-cli ]]; } || MISSING="$MISSING vds-cli"
+[[ -x .claude/bin/vds-cli ]] && export PATH=".claude/bin:$PATH"
 [[ -z "${VDS_CONFLUENCE_TOKEN:-}" ]] && MISSING="$MISSING VDS_CONFLUENCE_TOKEN"
 [[ -z "${VDS_JIRA_TOKEN:-}" ]] && MISSING="$MISSING VDS_JIRA_TOKEN"
 [[ -z "${VDS_CONFLUENCE_SPACE_DEFAULT:-}" ]] && MISSING="$MISSING VDS_CONFLUENCE_SPACE_DEFAULT"

package/skills/vds-skill/vds-scripts-skill/SKILL.md

@@ -18,7 +18,7 @@ metadata:
 
 Use this skill as the **platform-routing entrypoint** for the WHO scripts ecosystem.
 
-The VDS scripts ecosystem lives at `~/.claude/vds-scripts/` (installed via `vsaf global`).
+The VDS scripts ecosystem can be installed at project-level `.claude/vds-scripts/` (preferred) or global `~/.claude/vds-scripts/`.
 
 This skill helps you:
 - find the right `vds-cli` command family
@@ -44,22 +44,24 @@ Do **not** use this skill as the authoritative deep runbook for:
 
 ## Canonical Sources
 
-- Scripts workspace: `~/.claude/vds-scripts/`
+- Scripts workspace: `.claude/vds-scripts/` (project-local, preferred) or `~/.claude/vds-scripts/` (global)
 
 ## Primary Command Entry Points
 
 ```bash
-# Via vds-cli (recommended — MCP-registered)
+# Via vds-cli on PATH (recommended — MCP-registered)
 vds-cli --help
 vds-cli confluence --help
 vds-cli jira --help
 vds-cli bitbucket --help
 vds-cli git --help
 
-# Direct uv invocation from vds-scripts root
+# Direct uv invocation — project-local
+.claude/vds-scripts/scripts/worktree_uv.sh run --directory .claude/vds-scripts --package vds-cli vds-cli --help
+.claude/vds-scripts/scripts/worktree_uv.sh run --directory .claude/vds-scripts --package audit_orchestrator vds-audit --help
+
+# Direct uv invocation — global fallback
 ~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package vds-cli vds-cli --help
-~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package audit_orchestrator vds-audit --help
-~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package spec_orchestrator vds-spec --help
 ```
 
 ## Platform Command Families
@@ -123,5 +125,5 @@ Use these bundled references for depth:
 ## Notes
 
 - Keep this file concise and routing-oriented; push deeper command catalogs into `references/`.
-- For integrated `~/.claude/vds-scripts` workspace usage, Python 3.10+ is the preferred baseline.
-- After updates, re-run `vsaf global` to sync skills to all agent surfaces.
+- For integrated vds-scripts workspace usage, Python 3.10+ is the preferred baseline.
+- vds-scripts can live at `.claude/vds-scripts/` (project) or `~/.claude/vds-scripts/` (global). Project-local is preferred for portability.

package/skills/vds-skill/vds-scripts-skill/references/google-sheets.md

@@ -66,6 +66,6 @@ Interactive monorepo-root usage commonly uses:
 
 ```bash
 vds-cli google-sheets <command>
-# Or direct uv invocation:
-~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package vds-cli vds-cli google-sheets <command>
+# Or direct uv invocation (project-local):
+.claude/vds-scripts/scripts/worktree_uv.sh run --directory .claude/vds-scripts --package vds-cli vds-cli google-sheets <command>
 ```

package/skills/vds-skill/vds-scripts-skill/references/integration-commands.md

@@ -2,7 +2,7 @@
 
 vds Representative WHO integration command families.
 
-These examples use `vds-cli` (MCP-registered entrypoint). For direct uv invocation, prefer `~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package <uv-package-name> ...`.
+These examples use `vds-cli` (MCP-registered entrypoint). For direct uv invocation, use `.claude/vds-scripts/scripts/worktree_uv.sh run --directory .claude/vds-scripts --package <uv-package-name> ...` (project-local) or `~/.claude/vds-scripts/...` (global fallback).
 
 - `vds-cli jira ...`
   - JQL search example: `vds-cli jira search "project = CBDC ORDER BY updated DESC" --limit 5 --json-only`

package/skills/vds-skill/vds-scripts-skill/references/platform-bootstrap.md

@@ -4,18 +4,18 @@ Use this guide when you need to enter the WHO scripts ecosystem and choose the f
 
 ## Canonical entrypoints
 
+vds-scripts can be installed at **project-local** `.claude/vds-scripts/` (preferred) or **global** `~/.claude/vds-scripts/`.
+
+- Project-local usage (preferred):
+  - `.claude/vds-scripts/scripts/worktree_uv.sh run --directory .claude/vds-scripts --package vds-cli vds-cli --help`
+  - `.claude/vds-scripts/scripts/worktree_uv.sh run --directory .claude/vds-scripts --package vds-cli vds-cli env status`
+  - `.claude/vds-scripts/scripts/worktree_uv.sh run --directory .claude/vds-scripts --package vds-cli vds-cli doctor`
 - Interactive monorepo-root usage:
   - `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli --help`
-  - `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli env status`
-  - `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli status`
-  - `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli doctor`
 - Dedicated `vds-scripts` worktree usage:
   - `./scripts/worktree_uv.sh run --package vds_cli vds-cli --help`
-  - `./scripts/worktree_uv.sh run --package vds_cli vds-cli env status`
-  - `./scripts/worktree_uv.sh run --package vds_cli vds-cli status`
-  - `./scripts/worktree_uv.sh run --package vds_cli vds-cli doctor`
 - Maintained shell scripts should not copy those raw forms. They should source `scripts/vds_sh_helpers.sh` and use the helper contract (`vds_uv_run_package`, `vds_uv_sync_package`, `vds_uv_sync_all`).
-- Preferred integrated baseline for the `WHO-project/vds-scripts` workspace is Python 3.14+.
+- Preferred integrated baseline is Python 3.10+.
 
 ## Common first steps