@ngocsangairvds/vsaf 4.1.12 → 4.1.15

package/skills/vds-skill/runtime/docs/agents/how-to/phase131-all-project-preparation.md

@@ -4,7 +4,7 @@
 
 Use this guide when you want to prepare multiple projects for parent `workflow-projects` execution before or during bounded analysis.
 For shared env/config/cache path behavior and portable cache-root conventions, see `../reference/portable-paths-and-config.md`.
-When running from a dedicated `vds-scripts` worktree, prefer `./scripts/worktree_uv.sh run --project audit_orchestrator ...` over plain `uv run ...` so a different checkout's active `.venv` does not leak into the current worktree.
+When running from a dedicated `vds-scripts` worktree, prefer `uv run --directory ~/.claude/vds-scripts --package audit_orchestrator ...` over plain `uv run ...` so a different checkout's active `.venv` does not leak into the current worktree.
 
 > **Note — interactive use vs. shell scripts**: The `uv run --project <path>` commands below are for interactive terminal or agent use from the repo root. When writing shell scripts, use `vds_uv_run_package <member>` from `scripts/vds_sh_helpers.sh` instead — see `scripts/README.md` for the canonical contract.
 
@@ -33,7 +33,7 @@ Do not treat these files as a replacement for centralized readiness, completenes
 Use `--registry-page` when the registry page should decide project scope.
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --registry-page <REGISTRY_PAGE_ID> \
   --prepare-materials \
@@ -50,11 +50,11 @@ Use `--project-storage-keys` when you already know the exact project page IDs.
 
 ```bash
 # If projects are new (Confluence-only), parse first:
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit parse-registry --registry-page <PARENT_PAGE_ID> --state-dsn env
 
 # Then run workflow-projects with explicit keys:
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --project-storage-keys 88727304,88718940 \
   --prepare-materials \
@@ -77,7 +77,7 @@ Pass `--checklist-page-id` to `workflow-projects` and it is forwarded to all chi
 # Payment department example — checklist page is at root, not under each project
 # Repo-page publication defaults to the canonical project page as the hierarchy anchor.
 # Omit --confluence-parent; the publisher creates the shared Project Audit node under each project page.
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --project-storage-keys 91334048,91335346 \
   --checklist-page-id 88722450 \
@@ -90,7 +90,7 @@ Pass `--checklist-page-id` to `workflow-projects` and it is forwarded to all chi
 The same flag works on `workflow-project` (single project):
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-project \
   --project-storage-key 91334048 \
   --thread-id <thread_id> \
@@ -100,7 +100,7 @@ The same flag works on `workflow-project` (single project):
 For repo-page publication on a single Payment project, omit `--confluence-parent` in the normal case. The project page is the default hierarchy anchor; `88716694` remains the department discovery page, not the upload parent:
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-project \
   --project-storage-key 91334048 \
   --thread-id <thread_id> \
@@ -127,7 +127,7 @@ That means each selected project is prepared before child project analysis is la
 Use `--skip-materials` only when the project set is already ready or when a resume-driven rerun should rely on current centralized state instead of re-preparing everything.
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --project-storage-keys 88727304,88718940 \
   --skip-materials \
@@ -140,7 +140,7 @@ Use `--skip-materials` only when the project set is already ready or when a resu
 Use `--require-all-materials` when any failed preparation/readiness result should block analysis launch for the selected scope.
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --registry-page <REGISTRY_PAGE_ID> \
   --prepare-materials \
@@ -191,16 +191,16 @@ Before a large run, it is still safer to verify:
 Recommended checks:
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit --json-only doctor profile-availability --mode active
 
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit --json-only state readiness --project 88727304
 
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit --json-only state completeness --project 88727304
 
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit query-checklist --checklist-page 88722450 --summary-only
 ```
 

package/skills/vds-skill/runtime/docs/agents/how-to/phase131-bounded-parallel-analysis.md

@@ -3,7 +3,7 @@
 # Phase 131 Bounded Parallel Analysis
 
 Use this guide when running the landed `workflow-projects` parent command with explicit outer-project and inner child concurrency settings.
-When running from a dedicated `vds-scripts` worktree, prefer `./scripts/worktree_uv.sh run --project audit_orchestrator ...` over plain `uv run ...` so a different checkout's active `.venv` does not leak into the current worktree.
+When running from a dedicated `vds-scripts` worktree, prefer `uv run --directory ~/.claude/vds-scripts --package audit_orchestrator ...` over plain `uv run ...` so a different checkout's active `.venv` does not leak into the current worktree.
 
 > **Note — interactive use vs. shell scripts**: The `uv run --project <path>` commands below are for interactive terminal or agent use from the repo root. When writing shell scripts, use `vds_uv_run_package <member>` from `scripts/vds_sh_helpers.sh` instead — see `scripts/README.md` for the canonical contract.
 
@@ -25,7 +25,7 @@ The parent runtime now surfaces pressure diagnostics in parent artifacts so oper
 For bounded verification, start conservatively:
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --registry-page <REGISTRY_PAGE_ID> \
   --prepare-materials \
@@ -46,7 +46,7 @@ Then increase only after checking:
 ### Small explicit slice
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --project-storage-keys 88727304,88718940 \
   --profiles zai-openai \
@@ -60,7 +60,7 @@ Then increase only after checking:
 ### Registry-driven bounded run
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --registry-page <REGISTRY_PAGE_ID> \
   --max-projects 3 \
@@ -102,7 +102,7 @@ Use resume when you want to continue from an existing parent manifest scope whil
 Use the effective VDS cache root for your environment as defined by the portable Phase 2 contract in `../reference/portable-paths-and-config.md`.
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --resume \
   --report-dir <cache-root>/audit_runs/workflow-projects/<thread_id>
@@ -111,7 +111,7 @@ Use the effective VDS cache root for your environment as defined by the portable
 Or explicitly:
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --resume-dispatch-manifest <cache-root>/audit_runs/workflow-projects/<thread_id>/dispatch-manifest.json
 ```

package/skills/vds-skill/runtime/docs/agents/how-to/phase131-confluence-upload-recovery.md

@@ -3,7 +3,7 @@
 # Phase 131 Confluence Upload and Recovery
 
 Use this guide when enabling Confluence publication through `workflow-projects`.
-When running from a dedicated `vds-scripts` worktree, prefer `./scripts/worktree_uv.sh run --project audit_orchestrator ...` over plain `uv run ...` so a different checkout's active `.venv` does not leak into the current worktree.
+When running from a dedicated `vds-scripts` worktree, prefer `uv run --directory ~/.claude/vds-scripts --package audit_orchestrator ...` over plain `uv run ...` so a different checkout's active `.venv` does not leak into the current worktree.
 
 > **Note — interactive use vs. shell scripts**: The `uv run --project <path>` commands below are for interactive terminal or agent use from the repo root. When writing shell scripts, use `vds_uv_run_package <member>` from `scripts/vds_sh_helpers.sh` instead — see `scripts/README.md` for the canonical contract.
 
@@ -36,7 +36,7 @@ Default publication should still produce rich Confluence storage-format page bod
 Normal upload invocation (no explicit parent needed):
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --project-storage-keys 88727304,88718940 \
   --prepare-materials \
@@ -49,7 +49,7 @@ Normal upload invocation (no explicit parent needed):
 Use `--confluence-parent` only as a manual override when auto-resolution is insufficient (e.g., routing a project to a non-department parent page):
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --project-storage-keys 88727304 \
   --prepare-materials \
@@ -175,7 +175,7 @@ If a parent run produced the expected manifest, prefer resuming from it rather t
 Use the effective VDS cache root for your environment as defined by the portable Phase 2 contract in `../reference/portable-paths-and-config.md`.
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow-projects \
   --resume-dispatch-manifest <cache-root>/audit_runs/workflow-projects/<thread_id>/dispatch-manifest.json
 ```

package/skills/vds-skill/runtime/docs/agents/how-to/run-ecosystem-daily-report.md

@@ -64,7 +64,7 @@ Status:      PENDING
 
 **Command (diagnose a single collector):**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python scheduler_orchestrator/scripts/collector-diagnostics.py "Prometheus"
 ```
 
@@ -80,7 +80,7 @@ Status:      PENDING
 
 **Command (all collectors, JSON):**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python scheduler_orchestrator/scripts/collector-diagnostics.py --all --json
 ```
 
@@ -142,7 +142,7 @@ vds-cli scheduler events tail --topic ecosystem.daily.failed
 
 **Step 5 (2 min) — Programmatic check:**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python -c "from scheduler_orchestrator.tasks.ecosystem_report import check_missed_run; check_missed_run()"
 ```
 
@@ -150,7 +150,7 @@ vds-cli scheduler events tail --topic ecosystem.daily.failed
 
 **Step 1 (1 min) — Read the full report for triage hints:**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python scheduler_orchestrator/scripts/generate-report.py --mode full --output /tmp/triage.md
 cat /tmp/triage.md
 ```
@@ -160,7 +160,7 @@ Look for `[unavailable]` placeholders in the report output.
 
 **Step 3 (2 min) — Diagnose the failing collector:**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python scheduler_orchestrator/scripts/collector-diagnostics.py <CollectorName>
 ```
 
@@ -179,7 +179,7 @@ export VDS_ECOSYSTEM_DAILY__COMMIT_THRESHOLD=75
 ```bash
 # Confirm the collector works with longer timeout
 VDS_ECOSYSTEM_DAILY__COLLECTOR_TIMEOUT_S=30 \
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python scheduler_orchestrator/scripts/collector-diagnostics.py "<Name>"
 ```
 
@@ -195,7 +195,7 @@ VDS_ECOSYSTEM_DAILY__COLLECTOR_TIMEOUT_S=30 \
 
 **Step 1 (1 min) — Check migration status:**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   alembic -c scheduler_orchestrator/alembic.ini current
 ```
 
@@ -203,7 +203,7 @@ VDS_ECOSYSTEM_DAILY__COLLECTOR_TIMEOUT_S=30 \
 
 **Step 2 (3 min) — Apply migration:**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   alembic -c scheduler_orchestrator/alembic.ini upgrade head
 ```
 

package/skills/vds-skill/runtime/docs/agents/reference/audit-triage-playbook.md

@@ -17,13 +17,13 @@ Use the audit orchestrator as the authoritative triage entrypoint.
 Use `query-checklist` to inspect source checklist content directly before a rerun when the operator needs to confirm row ids, category placement, or checklist bootstrap behavior without launching workflow evaluation.
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit query-checklist --checklist-page 88722450 --summary-only
 
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit query-checklist --checklist-page 88722450 --target row-1
 
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit query-checklist --checklist-page 88722450 --target chk_1
 ```
 
@@ -36,7 +36,7 @@ Selector rule:
 If the checklist page should be inferred from centralized state instead of passed explicitly:
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit query-checklist \
   --project-storage-key 88727304 \
   --checklist-profile default \
@@ -55,7 +55,7 @@ When calling from a shell script, use `vds_uv_run_package audit_orchestrator` in
 [`scripts/README.md`](../../scripts/README.md#uv-contract--canonical-usage).
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow <repo-cache-root>/PAR-project/merchant-report \
   --profile zai-openai \
   --project-storage-key 88727304 \
@@ -123,15 +123,15 @@ mismatch explicitly instead of assuming convenience commands exist.
 
 ```bash
 # Credentials
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit --json-only doctor credentials --require-state-dsn
 
 # Profile / provider availability
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit --json-only doctor profile-availability --mode active
 
 # Project readiness
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit --json-only state readiness --project <PROJECT_PAGE_ID>
 ```
 
@@ -158,7 +158,7 @@ For the full runtime-discovery and gap-reporting contract, see
 For Payment department projects, the verified working command is:
 
 ```bash
-./scripts/worktree_uv.sh run --project audit_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package audit_orchestrator \
   vds-cli audit workflow <repo-cache-root>/<PROJECT-KEY>-project/<repo> \
   --project-storage-key <PSK> \
   --checklist-page-id 88722450 \

package/skills/vds-skill/runtime/docs/agents/reference/cli-commands.md

@@ -3,7 +3,7 @@
 # CLI Commands
 
 Current command surface is WHO-owned and runs from `WHO-project/vds-scripts`.
-When operating from a dedicated `vds-scripts` worktree, prefer `./scripts/worktree_uv.sh ...` so a different checkout's active `.venv` does not leak into the current worktree.
+When operating from a dedicated `vds-scripts` worktree, prefer `uv run --directory ~/.claude/vds-scripts ...` so a different checkout's active `.venv` does not leak into the current worktree.
 `worktree_uv.sh` also bootstraps missing shared runtime env from `~/.vds/.env` (or `VDS_ENV_FILE`) and re-roots execution to the owning repo, so detached shells and tmux sessions do not depend on manual `source ~/.vds/.env`.
 
 > **Interactive use vs. shell scripts**
@@ -32,7 +32,7 @@ Use `scripts/run-audit-in-tmux.sh` to run any `vds-cli audit` command in a persi
 ./scripts/run-audit-in-tmux.sh --kill <name>
 ```
 
-The tmux runner delegates to `./scripts/worktree_uv.sh`, so shared env bootstrap follows the same precedence contract:
+The tmux runner delegates to `uv run --directory ~/.claude/vds-scripts`, so shared env bootstrap follows the same precedence contract:
 - explicit CLI flags win over everything else;
 - explicitly exported shell env wins over shared env file values;
 - `VDS_ENV_FILE` overrides the default `~/.vds/.env` path;
@@ -109,13 +109,13 @@ The shell runners are operator convenience wrappers. `workflow-project` and `wor
 
 ## Key Commands
 
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli env status`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit query-checklist --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli tasks --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli progress --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli env status`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit query-checklist --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli spec --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli tasks --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli progress --help`
 
 ## Direct executable naming notes
 
@@ -159,20 +159,20 @@ Operational implications:
 Normal analysis should keep readiness enabled. Use this sequence:
 
 1. Discovery + persist to Postgres (requires `--state-dsn env`):
-   `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit parse-registry --registry-page <PROJECT_OR_DEPARTMENT_OR_ROOT_PAGE> --state-dsn env`
+   `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit parse-registry --registry-page <PROJECT_OR_DEPARTMENT_OR_ROOT_PAGE> --state-dsn env`
 
    > **Critical**: Without `--state-dsn env`, `parse-registry` only outputs JSON and does NOT save discovered projects to the Postgres state backend. Omitting this flag means `prepare` and `state readiness` will not find the projects.
 
 2. Materials preparation:
-   `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit prepare --project <PROJECT_PAGE_ID>`
+   `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit prepare --project <PROJECT_PAGE_ID>`
 3. Readiness proof:
-   `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --json-only state readiness --project <PROJECT_PAGE_ID> [--repo <REPO_STORAGE_KEY_OR_SLUG>]`
+   `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit --json-only state readiness --project <PROJECT_PAGE_ID> [--repo <REPO_STORAGE_KEY_OR_SLUG>]`
 4. Analysis:
-   `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit workflow <REPO_PATH> --project-storage-key <PROJECT_PAGE_ID> --thread-id <THREAD_ID>`
+   `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit workflow <REPO_PATH> --project-storage-key <PROJECT_PAGE_ID> --thread-id <THREAD_ID>`
    (Full canonical 56-row evaluation is the default. Use `--target row-1` or another selector verified through `query-checklist` for specific rows. Use `--no-canonical-checklist` only to opt out — this produces incomplete reports.)
 
    When checklist auto-discovery fails (i.e. the checklist page is not a direct child of the project page), add `--checklist-page-id` to restore full canonical evaluation. For Payment department projects, the verified working command is:
-   `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit workflow <REPO_PATH> --project-storage-key <PROJECT_PAGE_ID> --checklist-page-id 88722450 --thread-id <THREAD_ID>`
+   `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit workflow <REPO_PATH> --project-storage-key <PROJECT_PAGE_ID> --checklist-page-id 88722450 --thread-id <THREAD_ID>`
    Confirmed bootstrap signal: `canonical_checklist_bootstrap_preflight_passed: source=explicit_page_id`
 
 Guard rules:
@@ -182,8 +182,8 @@ Guard rules:
 - If you start from a department/root page, resolve child project pages first, then prepare and run analysis per project.
 
 Current provider launch-readiness commands:
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --json-only doctor profile-availability --mode active`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --json-only doctor profile-availability --profiles zai-openai --mode active`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit --json-only doctor profile-availability --mode active`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit --json-only doctor profile-availability --profiles zai-openai --mode active`
 
 ## Live Debug Logging
 
@@ -196,8 +196,8 @@ Current provider launch-readiness commands:
 - Full payload trace logging remains a heavier mode and is auto-enabled only for `--trace`, `--debug-evidence-context`, or `--debug-batch-timing`.
 
 Current Confluence connectivity commands:
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit doctor check-confluence --json`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli confluence search -s internal -q 'type=page' --limit 2 --json`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit doctor check-confluence --json`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli confluence search -s internal -q 'type=page' --limit 2 --json`
 
 Current Confluence operator notes:
 - Checklist-heavy reads default to the internal server because that is where the authoritative checklist pages live.
@@ -213,18 +213,18 @@ Current Confluence operator notes:
 - Probe failures stay in the structured doctor output and do not emit warning-level Confluence transport logs during the diagnostic command itself.
 
 Current checklist inspection command surface:
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit query-checklist --checklist-page 88722450 --summary-only`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit query-checklist --checklist-page 88722450 --target row-1`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit query-checklist --checklist-page 88722450 --target chk_1`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit query-checklist --project-storage-key 88727304 --checklist-profile default --summary-only`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit query-checklist --checklist-page 88722450 --summary-only`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit query-checklist --checklist-page 88722450 --target row-1`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit query-checklist --checklist-page 88722450 --target chk_1`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit query-checklist --project-storage-key 88727304 --checklist-profile default --summary-only`
 
 Use `query-checklist` when you need to inspect source checklist rows directly without launching workflow evaluation. It accepts an explicit checklist page or can bootstrap from a project storage key plus checklist profile.
 For source-checklist pages, derive operator-facing `--target` selectors from `query-checklist` output itself. Prefer numeric row selectors (`1`) or row ids (`row-1`) for a unique row. Parser check ids (`chk_1`) are valid but may repeat across sections on the same checklist page. Do not copy `dispatch-manifest.json` internal `explicit:<page>:...` payloads into `workflow --target` or `query-checklist --target`; those are internal dispatch row-key bundles, not CLI selector forms.
 
 Current Phase 131 multi-project command surface (initial landed runtime):
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit workflow-projects --registry-page <REGISTRY_PAGE_ID> --prepare-materials --max-projects-prepare-concurrent 3 --max-projects-concurrent 3 --max-concurrent 16`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit workflow-projects --project-storage-keys 88727304,88718940 --profiles zai-openai --profile-availability active --max-projects-concurrent 2 --max-concurrent 16`
-- With explicit checklist page for department-level projects where checklist auto-discovery fails: `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit workflow-projects --project-storage-keys 91334048,91335346 --checklist-page-id 88722450 --prepare-materials --max-projects-concurrent 2 --max-concurrent 4`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit workflow-projects --registry-page <REGISTRY_PAGE_ID> --prepare-materials --max-projects-prepare-concurrent 3 --max-projects-concurrent 3 --max-concurrent 16`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit workflow-projects --project-storage-keys 88727304,88718940 --profiles zai-openai --profile-availability active --max-projects-concurrent 2 --max-concurrent 16`
+- With explicit checklist page for department-level projects where checklist auto-discovery fails: `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit workflow-projects --project-storage-keys 91334048,91335346 --checklist-page-id 88722450 --prepare-materials --max-projects-concurrent 2 --max-concurrent 4`
 
 > **`--checklist-page-id` is required when running from department or registry pages**: When `workflow-project` or `workflow-projects` is invoked against a project whose checklist page is not a direct child of that project page, auto-discovery fails and evaluation falls back to targeted mode (1-3 rows) instead of the full canonical 56-row run. Pass `--checklist-page-id <CHECKLIST_PAGE_ID>` explicitly to restore full canonical evaluation. For Payment department projects, the checklist page is `88722450` — it lives at the root level, not under each child project.
 
@@ -247,20 +247,20 @@ Phase 131 current runtime guidance:
 
 ## Phase 124 Closure Pack
 
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec validate audit-orchestrator`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec check-alignment audit-orchestrator`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec consolidate audit-orchestrator`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec validate-sync audit-orchestrator --agents-file AGENTS.md --agents-label "Audit orchestrator" --json-only`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli spec validate audit-orchestrator`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli spec check-alignment audit-orchestrator`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli spec consolidate audit-orchestrator`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli spec validate-sync audit-orchestrator --agents-file AGENTS.md --agents-label "Audit orchestrator" --json-only`
 - `python3 WHO-project/vds-scripts/audit_orchestrator/scripts/verify_phase124_handoff.py --output-json reports/verification/phase124/command-pack.json`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit publish-system-doc --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit publish-system-doc --help`
 
 The audit-orchestrator package still exposes `validate-spec-sync` for compatibility, but the shared `vds-cli spec validate-sync` gate is the preferred sync command after the WHO migration.
 
 ## Targeted Workflow Reruns
 
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --profile zai-openai workflow <repo-cache-root>/PAR-project/merchant-report --project-storage-key 88727304 --thread-id phase124-row2-par-mr-zai --target row-2`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit workflow-project --project-storage-key 88727304 --thread-id <thread_id>`
-- With explicit checklist page (required when checklist auto-discovery fails from a department/project page): `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit workflow-project --project-storage-key 88727304 --thread-id <thread_id> --checklist-page-id 88722450`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit --profile zai-openai workflow <repo-cache-root>/PAR-project/merchant-report --project-storage-key 88727304 --thread-id phase124-row2-par-mr-zai --target row-2`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit workflow-project --project-storage-key 88727304 --thread-id <thread_id>`
+- With explicit checklist page (required when checklist auto-discovery fails from a department/project page): `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit workflow-project --project-storage-key 88727304 --thread-id <thread_id> --checklist-page-id 88722450`
 
 Current Phase 130 live verification also validated a narrow control-aware security preflight exception for `CL-014`, `CL-042`, `CL-051`, `CL-052`, and `CL-053` when code anchors are present but current indexed docs do not provide document anchors. The machine-readable preflight payload records this as `code_anchor_exception_applied=true`.
 

package/skills/vds-skill/runtime/docs/agents/reference/cli-help-matrix.md

@@ -13,7 +13,7 @@ are internal router implementation details and must never be invoked by users.
    these are internal to the router.
 3. Treat `--help` as the authoritative discovery surface before assuming an
    command name.
-4. In dedicated `vds-scripts` worktrees, prefer `./scripts/worktree_uv.sh ...`
+4. In dedicated `vds-scripts` worktrees, prefer `uv run --directory ~/.claude/vds-scripts ...`
    for `uv` commands so inherited parent `VIRTUAL_ENV` state does not leak into
    the wrong worktree.
 
@@ -69,11 +69,11 @@ Commands built into `vds-cli` (not routed to orchestrators):
 
 > All examples **must** use `vds-cli` routing — direct executables are internal.
 
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli tasks --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli schema --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli spec --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli tasks --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli schema --help`
 
 ## Source notes
 

package/skills/vds-skill/runtime/docs/agents/reference/ecosystem-daily-report.md

@@ -212,18 +212,18 @@ vds-cli scheduler schedules trigger-now ecosystem-daily-report
 
 **Generate a local report on-demand:**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python scheduler_orchestrator/scripts/generate-report.py --mode full
 ```
 
 **Diagnose a specific collector:**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   python scheduler_orchestrator/scripts/collector-diagnostics.py "Prometheus"
 ```
 
 **CI verification (all Phase 2 tests + collectors):**
 ```bash
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
+uv run --directory ~/.claude/vds-scripts --package scheduler_orchestrator \
   bash scheduler_orchestrator/scripts/verify-phase2.sh
 ```

package/skills/vds-skill/runtime/docs/agents/reference/portable-paths-validation-matrix.md

@@ -36,8 +36,8 @@ Run on the active development host.
 
 Recommended checks:
 - `uv run --project vds_cli_common pytest vds_cli_common/tests/test_paths.py vds_cli_common/tests/test_env.py`
-- `PYTHONPATH=audit_orchestrator/src:vds_cli_common/src:bitbucket_orchestrator/src:confluence_orchestrator/src:sonarqube_orchestrator/src:google_sheets_orchestrator/src:excel_orchestrator/src:git_orchestrator/src:vds_cli/src:spec_orchestrator/src ./scripts/worktree_uv.sh run --project audit_orchestrator pytest audit_orchestrator/tests/test_paths_config_phase2.py audit_orchestrator/tests/test_cli_paths_phase2.py audit_orchestrator/tests/unit/scripts/test_verify_phase124_handoff.py`
-- optional smoke: `./scripts/worktree_uv.sh run --project vds_cli vds-cli env status`
+- `PYTHONPATH=audit_orchestrator/src:vds_cli_common/src:bitbucket_orchestrator/src:confluence_orchestrator/src:sonarqube_orchestrator/src:google_sheets_orchestrator/src:excel_orchestrator/src:git_orchestrator/src:vds_cli/src:spec_orchestrator/src uv run --directory ~/.claude/vds-scripts --package audit_orchestrator pytest audit_orchestrator/tests/test_paths_config_phase2.py audit_orchestrator/tests/test_cli_paths_phase2.py audit_orchestrator/tests/unit/scripts/test_verify_phase124_handoff.py`
+- optional smoke: `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli env status`
 
 Expected evidence:
 - shared helper tests pass

package/skills/vds-skill/runtime/docs/agents/reference/vds-ai-memory-api.md

@@ -23,7 +23,7 @@ vds-cli memory health
 vds-cli memory --json-only stats
 ```
 
-Use the routed form for normal execution. Place global flags like `--json-only` before the subcommand. For detailed subcommand help, use `./scripts/worktree_uv.sh run --project memory_orchestrator vds-memory --help`.
+Use the routed form for normal execution. Place global flags like `--json-only` before the subcommand. For detailed subcommand help, use `uv run --directory ~/.claude/vds-scripts --package memory_orchestrator vds-memory --help`.
 
 ## REST API (curl fallback)
 

package/skills/vds-skill/runtime/docs/agents/tutorials/who-skills-and-scripts-onboarding.md

@@ -23,10 +23,10 @@ Before deeper task routing, follow `../how-to/install-and-bootstrap-who-scripts-
 
 If you are inside a dedicated `vds-scripts` worktree, prefer the worktree-safe wrapper:
 
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli env status`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli audit --help`
-- `./scripts/worktree_uv.sh run --project vds_cli vds-cli spec --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli env status`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli audit --help`
+- `uv run --directory ~/.claude/vds-scripts --package vds_cli vds-cli spec --help`
 
 ## 5. Edit only canonical sources