@ngocsangairvds/vsaf 3.2.6 → 3.2.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ngocsangairvds/vsaf",
3
- "version": "3.2.6",
3
+ "version": "3.2.8",
4
4
  "description": "improve confluence format",
5
5
  "keywords": ["claude", "claude-code", "ai", "sdlc", "framework", "bmad", "gitnexus", "superpowers"],
6
6
  "bin": {
package/src/project.js CHANGED
@@ -5,9 +5,10 @@ const { ok, info, warn, step, hasCommand, exec, copyDir, copyFile, cleanStaleWal
5
5
 
6
6
  const PKG_ROOT = path.join(__dirname, '..');
7
7
  const TEMPLATES = path.join(PKG_ROOT, 'assets', 'templates');
8
- const SKILLS_SRC = path.join(PKG_ROOT, 'tools', 'skills');
9
- const BMAD_SRC = path.join(PKG_ROOT, 'tools', 'bmad');
10
- const CWD = process.cwd();
8
+ const SKILLS_SRC = path.join(PKG_ROOT, 'tools', 'skills');
9
+ const BMAD_SRC = path.join(PKG_ROOT, 'tools', 'bmad');
10
+ const VDS_SCRIPTS_SRC = path.join(PKG_ROOT, 'tools', 'vds-scripts');
11
+ const CWD = process.cwd();
11
12
 
12
13
  async function installProject() {
13
14
  console.log('\n\x1b[1m╔══════════════════════════════════════════╗\x1b[0m');
@@ -17,6 +18,7 @@ async function installProject() {
17
18
  scaffoldFiles();
18
19
  scaffoldBmadWorkspace();
19
20
  syncLocalBmadSkills();
21
+ syncVdsScripts();
20
22
  initGitNexus();
21
23
 
22
24
  console.log('\n\x1b[32m\x1b[1m✓ Project ready.\x1b[0m');
@@ -157,6 +159,19 @@ function syncLocalBmadSkills() {
157
159
  ok(`${installed} BMAD skill(s) installed/updated`);
158
160
  }
159
161
 
162
+ function syncVdsScripts() {
163
+ step('VDS Scripts → .claude/vds-scripts/');
164
+
165
+ if (!fs.existsSync(VDS_SCRIPTS_SRC)) {
166
+ warn('vds-scripts not found in package — skipping');
167
+ return;
168
+ }
169
+
170
+ const dst = path.join(CWD, '.claude', 'vds-scripts');
171
+ copyDir(VDS_SCRIPTS_SRC, dst);
172
+ ok('vds-scripts — synced to .claude/vds-scripts/');
173
+ }
174
+
160
175
  function initGitNexus() {
161
176
  step('GitNexus');
162
177
  if (!hasCommand('gitnexus')) { warn('gitnexus not found — run: vsaf global'); return; }
@@ -18,9 +18,7 @@ metadata:
18
18
 
19
19
  Use this skill as the **platform-routing entrypoint** for the WHO scripts ecosystem.
20
20
 
21
- `WHO-project` is the canonical VDS ecosystem for both reusable skills and routed scripts:
22
- - skills live under `WHO-project/vds-skills/skills/`
23
- - scripts and orchestrators live under `WHO-project/vds-scripts/`
21
+ The VDS scripts ecosystem lives at `~/.claude/vds-scripts/` (installed via `vsaf global`).
24
22
 
25
23
  This skill helps you:
26
24
  - find the right `vds-cli` command family
@@ -46,27 +44,22 @@ Do **not** use this skill as the authoritative deep runbook for:
46
44
 
47
45
  ## Canonical Sources
48
46
 
49
- - Scripts workspace: `WHO-project/vds-scripts/`
50
- - Skills catalog: `WHO-project/vds-skills/skills/`
51
- - Skill registry: `WHO-project/vds-skills/registry.yaml`
52
- - Alignment workflow: `WHO-project/vds-skills/ALIGNMENT.md`
47
+ - Scripts workspace: `~/.claude/vds-scripts/`
53
48
 
54
49
  ## Primary Command Entry Points
55
50
 
56
- ```/dev/null/vds-scripts-skill-entrypoints.sh#L1-12
57
- # Interactive monorepo-root usage
58
- ./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli --help
59
- ./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package audit_orchestrator vds-audit --help
60
- ./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package spec_orchestrator vds-spec --help
61
-
62
- # Dedicated vds-scripts worktree usage
63
- ./scripts/worktree_uv.sh run --package vds_cli vds-cli --help
64
- ./scripts/worktree_uv.sh run --package audit_orchestrator vds-audit --help
65
- ./scripts/worktree_uv.sh run --package spec_orchestrator vds-spec --help
66
-
67
- # Maintained shell scripts must not copy the plain patterns above.
68
- # They should source scripts/vds_sh_helpers.sh and use vds_uv_run_package
69
- # / vds_uv_sync_package / vds_uv_sync_all instead.
51
+ ```bash
52
+ # Via vds-cli (recommended — MCP-registered)
53
+ vds-cli --help
54
+ vds-cli confluence --help
55
+ vds-cli jira --help
56
+ vds-cli bitbucket --help
57
+ vds-cli git --help
58
+
59
+ # Direct uv invocation from vds-scripts root
60
+ ~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package vds-cli vds-cli --help
61
+ ~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package audit_orchestrator vds-audit --help
62
+ ~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package spec_orchestrator vds-spec --help
70
63
  ```
71
64
 
72
65
  ## Platform Command Families
@@ -128,8 +121,6 @@ Use these bundled references for depth:
128
121
 
129
122
  ## Notes
130
123
 
131
- - Edit this skill only under `WHO-project/vds-skills/skills/vds-scripts-skill/`.
132
- - Do not edit `.agent/skills/` directly.
133
124
  - Keep this file concise and routing-oriented; push deeper command catalogs into `references/`.
134
- - For integrated `WHO-project/vds-scripts` workspace usage, Python 3.14+ is the preferred baseline for humans and AI agents.
135
- - After updates, sync generated agent surfaces from the monorepo root.
125
+ - For integrated `~/.claude/vds-scripts` workspace usage, Python 3.10+ is the preferred baseline.
126
+ - After updates, re-run `vsaf global` to sync skills to all agent surfaces.
@@ -64,10 +64,8 @@ vds-cli google-sheets -- --json-only read \
64
64
 
65
65
  Interactive monorepo-root usage commonly uses:
66
66
 
67
- ```/dev/null/google-sheets-prefix.sh#L1-1
68
- ./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package vds-cli vds-cli google-sheets <command>
67
+ ```bash
68
+ vds-cli google-sheets <command>
69
+ # Or direct uv invocation:
70
+ ~/.claude/vds-scripts/scripts/worktree_uv.sh run --directory ~/.claude/vds-scripts --package vds-cli vds-cli google-sheets <command>
69
71
  ```
70
-
71
- Inside a dedicated `vds-scripts` worktree, the equivalent form is `./scripts/worktree_uv.sh run --package vds_cli vds-cli google-sheets <command>`.
72
-
73
- For maintained shell scripts inside `WHO-project/vds-scripts`, do not copy raw operator forms. Source `scripts/vds_sh_helpers.sh` and use the helper contract instead.
@@ -2,10 +2,10 @@
2
2
 
3
3
  vds Representative WHO integration command families.
4
4
 
5
- These examples are interactive operator examples. From the umbrella monorepo root, prefer `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package <uv-package-name> ...`. Inside a dedicated `vds-scripts` worktree, prefer `./scripts/worktree_uv.sh run --package <member-dir> ...`. Maintained shell scripts inside `WHO-project/vds-scripts` should source `scripts/vds_sh_helpers.sh` instead of copying raw operator forms.
5
+ 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> ...`.
6
6
 
7
7
  - `vds-cli jira ...`
8
- - JQL search example: `./WHO-project/vds-scripts/scripts/worktree_uv.sh run --directory WHO-project/vds-scripts --package jira_orchestrator vds-jira-cli search "project = CBDC ORDER BY updated DESC" --limit 5 --json-only`
8
+ - JQL search example: `vds-cli jira search "project = CBDC ORDER BY updated DESC" --limit 5 --json-only`
9
9
  - Note: `vds-jira-cli search` now accepts `--json-only` as a command-local flag after `search`, in addition to the global pre-subcommand form.
10
10
  - `vds-cli confluence ...`
11
11
  - `vds-cli bitbucket ...`
@@ -2,7 +2,7 @@
2
2
 
3
3
  Audit orchestrator: **8439 tests**, spec v4.93.0 (Phase 152 Planned)
4
4
 
5
- Operational rules for `WHO-project/vds-scripts`.
5
+ Operational rules for `~/.claude/vds-scripts`.
6
6
 
7
7
  ## Scope
8
8
 
@@ -121,7 +121,7 @@ newman run "BRD-Validation-API.postman_collection.json" \
121
121
 
122
122
  ```bash
123
123
  # Run the BRD validation script directly
124
- cd WHO-project/vds-scripts/scripts
124
+ cd ~/.claude/vds-scripts/scripts
125
125
  python3 validate_brd_coverage.py
126
126
 
127
127
  # View generated report
@@ -196,7 +196,7 @@ cat brd_coverage_report.json | jq '.'
196
196
  2. **Script Path Issues**:
197
197
  ```bash
198
198
  # Verify script exists
199
- ls -la WHO-project/vds-scripts/scripts/validate_brd_coverage.py
199
+ ls -la ~/.claude/vds-scripts/scripts/validate_brd_coverage.py
200
200
  ```
201
201
 
202
202
  3. **Newman Installation**:
@@ -229,7 +229,7 @@ jobs:
229
229
  run: npm install -g newman
230
230
  - name: Run BRD Validation Tests
231
231
  run: |
232
- cd WHO-project/vds-scripts/scripts
232
+ cd ~/.claude/vds-scripts/scripts
233
233
  newman run "BRD-Validation-API.postman_collection.json" \
234
234
  -e "brd-validation-environment.json" \
235
235
  --reporters cli,junit \
@@ -253,7 +253,7 @@ pipeline {
253
253
  steps {
254
254
  script {
255
255
  sh '''
256
- cd WHO-project/vds-scripts/scripts
256
+ cd ~/.claude/vds-scripts/scripts
257
257
  newman run "BRD-Validation-API.postman_collection.json" \
258
258
  -e "brd-validation-environment.json" \
259
259
  --reporters cli,json \
@@ -289,7 +289,7 @@ pipeline {
289
289
  - **Target State Documentation Update**: `.kiro/specs/target-state-documentation-update/`
290
290
  - **BRD Coverage Report**: `projects/INSURANCE/analysis/target-state/BRD_COVERAGE_REPORT.md`
291
291
  - **Service Specifications**: `projects/INSURANCE/analysis/target-state/service-specifications/`
292
- - **VDS Scripts Documentation**: `WHO-project/vds-scripts/docs/README.md`
292
+ - **VDS Scripts Documentation**: `~/.claude/vds-scripts/docs/README.md`
293
293
 
294
294
  ## Support
295
295
 
@@ -34,7 +34,7 @@ scripts/vds_sh_helpers.sh # runtime helpers: bind --directory and resolve pac
34
34
 
35
35
  ```bash
36
36
  SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
37
- # shellcheck source=WHO-project/vds-scripts/scripts/vds_sh_helpers.sh
37
+ # shellcheck source=~/.claude/vds-scripts/scripts/vds_sh_helpers.sh
38
38
  source "$SCRIPT_DIR/../vds_sh_helpers.sh" # adjust depth as needed
39
39
  ```
40
40
 
@@ -49,7 +49,7 @@ disk — not where the calling script lives.
49
49
  vds_uv_run_package vds_cli vds-cli doctor
50
50
 
51
51
  # WRONG — path-coupled, breaks in worktrees and alternate checkouts
52
- uv run --project WHO-project/vds-scripts/vds_cli vds-cli schema convert ...
52
+ uv run --project ~/.claude/vds-scripts/vds_cli vds-cli schema convert ...
53
53
  ```
54
54
 
55
55
  ### Syncing environments
@@ -84,7 +84,7 @@ The helper accepts either:
84
84
  - a workspace member directory name such as `vds_cli`, `audit_orchestrator`, or `markdown_orchestrator`, or
85
85
  - an explicit uv project/package name such as `vds-cli` or `vds-spec-orchestrator`
86
86
 
87
- For maintained scripts, prefer passing the directory/member name to the helper and let it resolve the uv project name from the member `pyproject.toml`. Do not pass filesystem paths like `WHO-project/vds-scripts/vds_cli`.
87
+ For maintained scripts, prefer passing the directory/member name to the helper and let it resolve the uv project name from the member `pyproject.toml`. Do not pass filesystem paths like `~/.claude/vds-scripts/vds_cli`.
88
88
 
89
89
  ---
90
90
 
@@ -17,11 +17,11 @@ set -euo pipefail
17
17
  # See scripts/vds_sh_helpers.sh for the canonical UV invocation helpers.
18
18
 
19
19
  SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
20
- # shellcheck source=WHO-project/vds-scripts/scripts/target-state-automation/docs_root.sh
20
+ # shellcheck source=~/.claude/vds-scripts/scripts/target-state-automation/docs_root.sh
21
21
  source "$SCRIPT_DIR/docs_root.sh"
22
22
 
23
23
  ROOT="$(resolve_repo_root)"
24
- VDS_SCRIPTS="$ROOT/WHO-project/vds-scripts"
24
+ VDS_SCRIPTS="$ROOT/~/.claude/vds-scripts"
25
25
  DOCS_ROOT="$(resolve_insurance_docs_root "$ROOT")"
26
26
  TARGET_STATE="$DOCS_ROOT/projects/INSURANCE/analysis/target-state"
27
27
 
@@ -11,7 +11,7 @@ set -euo pipefail
11
11
  # - each architecture service has a matching service-spec folder
12
12
 
13
13
  SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
14
- # shellcheck source=WHO-project/vds-scripts/scripts/target-state-automation/docs_root.sh
14
+ # shellcheck source=~/.claude/vds-scripts/scripts/target-state-automation/docs_root.sh
15
15
  source "$SCRIPT_DIR/docs_root.sh"
16
16
 
17
17
  ROOT="$(resolve_repo_root)"
@@ -2,7 +2,7 @@
2
2
 
3
3
  Date: 2026-03-25
4
4
  Branch: `feat/scripts-uv-workspace-alignment`
5
- Scope: helper/bootstrap/script-shell alignment for `WHO-project/vds-scripts/scripts/`
5
+ Scope: helper/bootstrap/script-shell alignment for `~/.claude/vds-scripts/scripts/`
6
6
 
7
7
  ## Summary
8
8
 
@@ -163,7 +163,7 @@ def test_output(captured_output):
163
163
  ## Development
164
164
 
165
165
  ```bash
166
- cd WHO-project/vds-scripts/vds_cli_common
166
+ cd ~/.claude/vds-scripts/vds_cli_common
167
167
 
168
168
  # Install with dev dependencies
169
169
  uv sync --group dev