@ngocsangairvds/vsaf 4.1.8 → 4.1.9

package/skills/vds-skill/vds-scripts/docs/agents/reference/excel-orchestrator.md

@@ -1,51 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Excel Orchestrator
-
-> Excel file processing and report generation.
-
-## Scope
-
-- **Does:** Read/write Excel files, format cells, generate reports from templates, and convert between formats.
-- **Does NOT:** Replace Excel UI, edit complex formulas, or manage Excel add-ins.
-- **Primary users:** AI agents (report generation), operators (data export), finance teams.
-
-## CLI Entry
-
-```bash
-# Via unified router
-vds-cli excel --help
-
-# Direct entry
-vds-cli excel --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `read` | Read Excel file | `--input`, `--sheet` |
-| `write` | Write Excel file | `--output`, `--data` |
-| `template` | Generate from template | `--template`, `--data`, `--output` |
-| `convert` | Convert to CSV/JSON | `--input`, `--format` |
-
-## Common Workflows
-
-### Workflow: Generate Report from Template
-
-1. Prepare data as JSON
-2. Run `vds-cli excel template --template report.xlsx --data data.json --output report-filled.xlsx`
-3. Review and distribute
-
-## Related
-
-- **Orchestrators:** [google-sheets](google-sheets-orchestrator.md), [pdf](pdf-orchestrator.md)
-- **Confluence:** [WHO Excel](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)
-
-## Troubleshooting
-
-| Issue | Cause | Resolution |
-|-------|-------|------------|
-| Command not found | Orchestrator not installed | Run `uv sync --all-packages` |
-| Config missing | `~/.vds/.env` unset | Add required credentials per [AGENTS.md](../../../AGENTS.md) |
-| Permission denied | Insufficient privileges | Check Bitbucket/Confluence token scope |

package/skills/vds-skill/vds-scripts/docs/agents/reference/git-orchestrator.md

@@ -1,62 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Git Orchestrator
-
-> Perform git operations: worktrees, branches, status, logs, stashes, and merge workflows as part of VDS monorepo tasks.
-
-## Scope
-
-**What this orchestrator does:**
-- Manage git worktrees (create, list, remove, prune).
-- Check branches and status across repositories.
-- Read commit history and create branches.
-- Rebase, cherry-pick, and merge workflow automation.
-- Run git bisect when a regression is detected.
-
-**What it does NOT do:**
-- Does not provide full repository hosting.
-- Does not replace Bitbucket clone/pull/push (see Bitbucket orchestrator for those).
-
-**Primary users:** AI agents managing worktrees and feature branches; human devops running merge pipelines.
-
-## CLI Entry
-
-```bash
-vds-cli git --help
-vds-cli git-orchestrator --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `worktree-create` | Create a new worktree for a branch | `--branch`, `--path` |
-| `worktree-list` | List active worktrees | `--repo` |
-| `worktree-remove` | Remove a worktree directory | `--path` |
-| `branch` | Create, list, or switch branches | `--name`, `--start-point` |
-| `status` | Show modified, staged, and untracked files | `--repo` |
-| `log` | Show commit history with stats | `--limit`, `--format` |
-| `rebase` | Reapply commits on top of another branch | `--branch` |
-| `merge` | Merge a branch into current | `--branch` |
-| `stash` | Save and restore working changes | `--command` |
-| `bisect` | Binary search to find bad commit | `--start`, `--bad` |
-
-## Common Workflows
-
-### Workflow 1: Feature Branch + Worktree
-1. Create branch: `vds-cli git branch --name feat/who-docs-v2 --start-point master`.
-2. Create worktree: `vds-cli git worktree-create --branch feat/who-docs-v2 --path worktrees/docs-v2`.
-3. Make changes in isolated workspace.
-4. Merge back: `vds-cli git merge --branch feat/who-docs-v2`.
-5. Cleanup: `vds-cli git worktree-remove --path worktrees/docs-v2`.
-
-### Workflow 2: Cherry-pick Fix Across Branches
-1. Identify fix commit: `vds-cli git log --limit=5`.
-2. Switch to target branch: `vds-cli git branch --name main`.
-3. Cherry-pick: `vds-cli git cherry-pick --commit=abc1234`.
-
-## Related
-
-- **Orchestrators:** [bitbucket](bitbucket-orchestrator.md), [tasks](tasks-orchestrator.md), [progress](progress-orchestrator.md)
-- **Skills:** [git-worktree-skill](../../../../vds-skills/skills/git-worktree-skill/SKILL.md)
-- **GitNexus:** [gitnexus-workspace](../../../../vds-skills/skills/gitnexus-workspace-skill/SKILL.md)

package/skills/vds-skill/vds-scripts/docs/agents/reference/google-sheets-orchestrator.md

@@ -1,51 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Google Sheets Orchestrator
-
-> Google Sheets integration for VDS data export and reporting.
-
-## Scope
-
-- **Does:** Read/write sheets, sync data from databases, generate reports, and manage sheet permissions.
-- **Does NOT:** Replace Google Sheets UI, manage Google Workspace, or handle OAuth setup.
-- **Primary users:** AI agents (report generation), operators (data sync), teams needing shared dashboards.
-
-## CLI Entry
-
-```bash
-# Via unified router
-vds-cli google-sheets --help
-
-# Direct entry
-vds-cli google-sheets --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `sync` | Sync data to sheet | `--sheet-id`, `--data`, `--range` |
-| `read` | Read sheet data | `--sheet-id`, `--range` |
-| `export` | Export to sheet | `--sheet-id`, `--input`, `--range` |
-| `clear` | Clear sheet range | `--sheet-id`, `--range` |
-
-## Common Workflows
-
-### Workflow: Sync Database Query to Sheet
-
-1. Run database query: `vds-cli db-query query --sql "SELECT * FROM metrics" --format json`
-2. Sync to sheet: `vds-cli google-sheets sync --sheet-id <id> --data results.json --range A1`
-3. Share sheet with team
-
-## Related
-
-- **Orchestrators:** [excel](excel-orchestrator.md), [db-query](db-query-orchestrator.md), [metabase](metabase-orchestrator.md)
-- **Confluence:** [WHO Google Sheets](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)
-
-## Troubleshooting
-
-| Issue | Cause | Resolution |
-|-------|-------|------------|
-| Command not found | Orchestrator not installed | Run `uv sync --all-packages` |
-| Config missing | `~/.vds/.env` unset | Add required credentials per [AGENTS.md](../../../AGENTS.md) |
-| Permission denied | Insufficient privileges | Check Bitbucket/Confluence token scope |

package/skills/vds-skill/vds-scripts/docs/agents/reference/grafana-orchestrator.md

@@ -1,52 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Grafana Orchestrator
-
-> Grafana logs and metrics operations — query logs, fetch dashboards, check alerts.
-
-## Scope
-
-- **Does:** Query logs via Loki, fetch dashboards, check alert status, export panel data.
-- **Does NOT:** Manage Grafana users, replace Grafana UI, or create new dashboards.
-- **Primary users:** AI agents (log analysis), operators (incident response), SRE.
-
-## CLI Entry
-
-```bash
-# Via unified router
-vds-cli grafana --help
-
-# Direct entry
-vds-cli grafana --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `logs` | Query logs via Loki | `--query`, `--from`, `--to` |
-| `dashboard` | Fetch dashboard JSON | `--uid` |
-| `alert` | Check alert status | `--state` |
-| `panel` | Export panel data | `--dashboard`, `--panel` |
-
-## Common Workflows
-
-### Workflow: Investigate Production Incident
-
-1. Query error logs: `vds-cli grafana logs --query '{app="api"} |= "ERROR"'`
-2. Narrow time window: `--from 2026-04-22T10:00:00Z --to 2026-04-22T11:00:00Z`
-3. Check related alerts: `vds-cli grafana alert --state firing`
-4. Export panel metrics for correlation
-
-## Related
-
-- **Orchestrators:** [elastic](elastic-orchestrator.md), [db-query](db-query-orchestrator.md), [metabase](metabase-orchestrator.md)
-- **Confluence:** [WHO Grafana](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)
-
-## Troubleshooting
-
-| Issue | Cause | Resolution |
-|-------|-------|------------|
-| Command not found | Orchestrator not installed | Run `uv sync --all-packages` |
-| Config missing | `~/.vds/.env` unset | Add required credentials per [AGENTS.md](../../../AGENTS.md) |
-| Permission denied | Insufficient privileges | Check Bitbucket/Confluence token scope |

package/skills/vds-skill/vds-scripts/docs/agents/reference/hexagonal-orchestrator.md

@@ -1,64 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Hexagonal Orchestrator
-
-> Validate hexagonal architecture compliance in Python and Java repositories.
-
-## Scope
-
-- **Does:** Analyze repositories for dependency direction, port/adapter boundaries, domain isolation, and layer violations using AST-based analyzers.
-- **Does NOT:** Auto-refactor code or validate performance.
-- **Primary users:** AI agents (architecture review), tech leads (CI compliance gates).
-
-## CLI Entry
-
-```bash
-# Via unified router
-vds-cli hexagonal --help
-
-# Direct entry
-vds-cli hexagonal --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `analyze` | Run hexagonal compliance analysis | `--config`, `--verbose`, `--timing`, `--cache-dir`, `--no-cache` |
-
-## Analysis Pipeline
-
-1. **Profile repository** — discover source files (`.py`, `.java`, `.kt`)
-2. **Classify layers** — map files to domain, application, infrastructure layers
-3. **Route to analyzers** — Python AST, Java AST, or fallback analyzer
-4. **Generate report** — violations with file paths, line numbers, and severity
-
-## Exit Codes
-
-| Code | Meaning |
-|------|---------|
-| 0 | Analysis completed successfully |
-| 1 | Runtime error (file not found, parse error) |
-| 2 | Configuration error |
-| 3 | Violations found (CI gate) |
-
-## Workflow Examples
-
-```bash
-# Basic analysis
-vds-cli hexagonal analyze /path/to/repo
-
-# With custom config and verbose output
-vds-cli hexagonal analyze /path/to/repo --config hexagonal.yaml --verbose --timing
-
-# JSON-only output for CI
-vds-cli hexagonal analyze /path/to/repo --json-only --quiet
-
-# Disable cache
-vds-cli hexagonal analyze /path/to/repo --no-cache
-```
-
-## Related
-
-- **Orchestrators:** [structure](structure-orchestrator.md), [circular-dependency](circular-dependency-orchestrator.md)
-- **Skills:** [code-review-graph-skill](../../../../vds-skills/skills/code-review-graph-skill/SKILL.md)

package/skills/vds-skill/vds-scripts/docs/agents/reference/index.md

@@ -1,36 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Reference Index
-
-> Quick index of all WHO documentation reference pages.
-
-## By Category
-
-### Orchestrators (28)
-See [Orchestrator Index](orchestrator-index.md)
-
-### Operations
-- [Audit Triage Playbook](audit-triage-playbook.md)
-- [Agent Operational Contract](agent-operational-contract.md)
-- [Progress Report CLI](progress-report-cli.md)
-
-### Platform
-- [VDS AI Memory API](vds-ai-memory-api.md)
-- [Portable Paths and Config](portable-paths-and-config.md)
-- [Validation and Sync Notes](validation-and-sync-notes.md)
-
-### Quality
-- [Capability Coverage Review](capability-coverage-review.md)
-- [Search Tools](search-tools.md)
-- [Skills Reference](skills-reference.md)
-
-```bash
-# Find any reference doc
-grep -i "topic" docs/agents/reference/*.md
-```
-
-## Related
-
-- [Orchestrator Index](orchestrator-index.md)
-- [Explanation Index](../explanation/index.md)
-- [How-To Index](../how-to/index.md)

package/skills/vds-skill/vds-scripts/docs/agents/reference/infrastructure-v2.15.md

@@ -1,67 +0,0 @@
-<!-- diátaxis: reference -->
-# VDS Infrastructure v2.15.x — Operator Reference
-
-> Consolidated delta from v2.14 → v2.15.x (PgBouncer dual-DSN, healthchecks, container cycling, init-schemas).
-
-## Overview
-
-Phase *v2.15.x* introduces PgBouncer fronting for all PostgreSQL access, per-stanza `search_path` pinning, and container-health probe standardization. Prior v2.14.x connected apps directly to `vds-postgres:5432` and relied on per-app URL `?options=search_path` fragments.
-
-## Components
-
-| Component | Location | Purpose |
-|-----------|----------|---------|
-| **PgBouncer** | `docker/infrastructure/pgbouncer/` | 1:1 session-mode pool per schema (`vds_audit`, `vds_memory`, `vds_progress`, `vds_sched`) |
-| **PostgreSQL** | `docker/infrastructure/init-schemas.sql` | Shared `vds_platform` database with schema-per-module (search_path + `connect_query`) |
-| **Healthcheck scripts** | `docker/backends/*/healthcheck.sh` | Standardized `HEALTHCHECK` pattern for orchestrator containers |
-| **Container cycling** | Orchestrator Dockerfiles | Boot-time idempotency: schema init only if `IF NOT EXISTS`; migration drift detection |
-
-## PgBouncer Stanzas
-
-```ini
-[databases]
-vds_audit    = host=vds-postgres port=5432 dbname=vds_platform connect_query='SET search_path TO audit_state, public' pool_size=40
-vds_memory   = host=vds-postgres port=5432 dbname=vds_platform connect_query='SET search_path TO memory, public' pool_size=40
-vds_progress = host=vds-postgres port=5432 dbname=vds_platform connect_query='SET search_path TO progress, public' pool_size=40
-vds_sched    = host=vds-postgres port=5432 dbname=vds_platform connect_query='SET search_path TO sched, public' pool_size=40
-```
-
-> **Note**: `options=` is **not** a valid per-stanza key in PgBouncer ≥1.24. Use `connect_query` for `search_path` pinning.
-
-## Healthcheck Pattern
-
-```dockerfile
-HEALTHCHECK --interval=30s --timeout=5s --start-period=10s --retries=3 \
-  CMD ["/app/healthcheck.sh"]
-```
-
-Each `healthcheck.sh` must:
-1. Validate DSN connectivity (PgBouncer or direct)
-2. Check schema ownership (`SELECT current_schema()`)
-3. Exit `0` = healthy, non-zero = unhealthy → Docker restarts container
-
-## Migration Guide (v2.14 → v2.15)
-
-1. **Update DSNs**: Replace direct postgres ports with PgBouncer stanzas
-2. **Remove `search_path` from URLs**: PgBouncer `connect_query` handles this
-3. **Restart containers**: PgBouncer must be up before apps connect
-4. **Validate `pool_size`**: Monitor `cl_waiting` via `SHOW POOLS`
-
-## Operational Notes
-
-- **Session mode** (1:1 client:backend) is mandatory for `scheduler_orchestrator` (DBOS LISTEN/NOTIFY) and `audit_orchestrator` (advisory locks).
-- **Transaction mode** override may be trialed for `memory_orchestrator` stanzas if `cl_waiting > 0` for 90 days.
-- **Container cycling**: Boot is idempotent (`IF NOT EXISTS`). Migrations run via Alembic after healthcheck passes.
-
-## Caveats
-
-- PgBouncer `connect_query` runs **once per backend** at startup, not per client session.
-- Changing `search_path` mid-session requires a reconnect (or explicit `SET search_path`).
-- `userlist.txt` (pgbouncer auth) is generated from `.env.template`; do not commit real credentials.
-
-## See Also
-
-- [ecosystem-daily-report](ecosystem-daily-report.md) — Health metrics and daily snapshot
-- [env-git-helper](env-git-helper.md) — Credential helper for container lifecycle
-- `docker/infrastructure/pgbouncer/pgbouncer.ini` — Live config
-- `docker/infrastructure/init-schemas.sql` — Schema bootstrap

package/skills/vds-skill/vds-scripts/docs/agents/reference/intellij-orchestrator.md

@@ -1,50 +0,0 @@
-<!-- diátaxis: reference -->
-
-# IntelliJ Orchestrator
-
-> IntelliJ IDEA plugin operations and project configuration.
-
-## Scope
-
-- **Does:** Manage IDE settings, run inspections, generate run configurations, and sync project structure.
-- **Does NOT:** Replace IDE UI, manage licenses, or handle plugin marketplace operations.
-- **Primary users:** Developers (IDE automation), DevOps (standardized configs).
-
-## CLI Entry
-
-```bash
-# Via unified router
-vds-cli intellij --help
-
-# Direct entry
-vds-cli intellij --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `inspect` | Run code inspections | `--profile`, `--output` |
-| `config` | Generate run configuration | `--type`, `--output` |
-| `sync` | Sync project structure | `--path` |
-
-## Common Workflows
-
-### Workflow: Run Inspections in CI
-
-1. Run `vds-cli intellij inspect --profile default --output inspection-results.xml`
-2. Parse results for violations
-3. Fail build if critical issues found
-
-## Related
-
-- **Orchestrators:** [lsp](lsp-orchestrator.md), [structure](structure-orchestrator.md)
-- **Confluence:** [WHO IntelliJ](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)
-
-## Troubleshooting
-
-| Issue | Cause | Resolution |
-|-------|-------|------------|
-| Command not found | Orchestrator not installed | Run `uv sync --all-packages` |
-| Config missing | `~/.vds/.env` unset | Add required credentials per [AGENTS.md](../../../AGENTS.md) |
-| Permission denied | Insufficient privileges | Check Bitbucket/Confluence token scope |

package/skills/vds-skill/vds-scripts/docs/agents/reference/jira-orchestrator.md

@@ -1,60 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Jira Orchestrator
-
-> Manage Jira issues: create, update, query, transition, and comment on tickets within the WHO project.
-
-## Scope
-
-**What this orchestrator does:**
-- Query Jira issues by key, project, Epic, assignee, or JQL.
-- Create or update issues with structured fields.
-- Transition issues through workflow states (e.g., To Do → In Progress → Done).
-- Add worklog entries and comments.
-- Generate Confluence pages from Epic scope data.
-
-**What it does NOT do:**
-- Does not create or modify Jira workflow schemas.
-- Does not send arbitrary REST calls outside the Jira plugin surface.
-
-**Primary users:** AI agents during audit triage; human project leads for progress tracking.
-
-## CLI Entry
-
-```bash
-vds-cli jira --help
-vds-cli jira-cli --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `get-issue` | Fetch a single issue by key | `--issue` |
-| `search-issues` | JQL search with pagination | `--jql` |
-| `create-issue` | Create a new ticket | `--project`, `--summary`, `--type` |
-| `update-issue` | Update fields and labels | `--issue` |
-| `transition-issue` | Move issue to a new status | `--issue`, `--transition-id` |
-| `add-comment` | Append comment to an issue | `--issue`, `--text` |
-| `add-worklog` | Log time on an issue | `--issue`, `--duration` |
-| `from-epic-to-confluence` | Export Epic children to Confluence | `--epic-key` |
-
-## Common Workflows
-
-### Workflow 1: Audit Triage
-1. Run `vds-cli audit` to identify findings.
-2. Use `vds-cli jira create-issue --project=PAR --type=Bug` to create tickets.
-3. Use `vds-cli jira transition-issue` to send tickets to In Review.
-4. Link evidence files from Confluence pages.
-
-### Workflow 2: Sprint Planning
-1. Query open tasks: `vds-cli jira search-issues --jql='PROJECT="TTCN24" AND status="Open"'`.
-2. Create sub-tasks under each Epic.
-3. Assign and set start/end dates via `update-issue`.
-
-## Related
-
-- **Orchestrators:** [confluence](../confluence-workflow.md), [bitbucket](bitbucket-orchestrator.md), [spec](spec-orchestrator.md)
-- **Skills:** [jira-skill](../../../../vds-skills/skills/)
-- **Confluence:** TTCN24 project pages
-- **Bitbucket:** vds-scripts repository

package/skills/vds-skill/vds-scripts/docs/agents/reference/links-orchestrator.md

@@ -1,57 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Links Orchestrator
-
-> Documentation link validation for VDS ecosystem.
-
-## Scope
-
-- **Does:** Validate link integrity across markdown documentation, detect broken internal/external links, and verify target-state documentation cross-references.
-- **Does NOT:** Fix broken links automatically or validate non-markdown content.
-- **Primary users:** AI agents (doc quality checks), documentation maintainers.
-
-## CLI Entry
-
-```bash
-# Via unified router
-vds-cli links --help
-
-# Direct entry
-vds-cli links --help
-```
-
-## Key Commands
-
-| Command | Purpose | Common Flags |
-|---------|---------|-------------|
-| `validate` | Validate links in documentation | `--mode`, `--root`, `--max-files`, `--report` |
-
-## Validation Modes
-
-- `target-state` — validate links within target-state documentation tree (default)
-- `docs` — validate links across general documentation with configurable file limit
-
-## Workflow Examples
-
-```bash
-# Validate target-state links (default)
-vds-cli links validate
-
-# Validate general docs with custom root
-vds-cli links validate --mode docs --root ./docs --max-files 100
-
-# Write JSON report
-vds-cli links validate --report link-report.json
-
-# JSON-only output
-vds-cli links --json-only validate --mode target-state
-```
-
-## Environment
-
-- `VDS_INSURANCE_DOCS_ROOT` — override default documentation root discovery
-
-## Related
-
-- **Orchestrators:** [structure](structure-orchestrator.md), [brd](brd-orchestrator.md)
-- **Confluence:** [WHO Links](http://confluence.digital.vn/display/TTCN24/WHO-Project+Ecosystem+Documentation)

package/skills/vds-skill/vds-scripts/docs/agents/reference/lint-cli.md

@@ -1,99 +0,0 @@
-<!-- diátaxis: reference -->
-
-# Lint CLI Reference
-
-> Compliance diagnostics and governance checks for the VDS CLI platform.
-
-## Summary Box
-
-| Property | Value |
-|---|---|
-| Command family | `vds-cli lint` |
-| Source file | `vds_cli/src/vds_cli/commands/lint_cli.py` |
-| Report scope | CLI surface, orchestrator mappings, doc drift, tool configs, test coverage gates |
-| Target agents | CI pipelines, repository maintainers |
-
-## Table of Contents
-
-- [Quick Reference](#quick-reference)
-- [cli](#cli)
-- [Report Checks](#report-checks)
-- [Exit Codes](#exit-codes)
-- [See Also](#see-also)
-
-## Quick Reference
-
-| Subcommand | Purpose | Key Flags | Example |
-|---|---|---|---|
-| `cli` | Run compliance diagnostics for the vds-cli surface | `--json` | `vds-cli lint cli --json` |
-
-## cli
-
-Run governance checks against the CLI surface and generate a compliance report.
-
-```bash
-vds-cli lint cli [OPTIONS]
-```
-
-#### Flags
-
-| Flag | Type | Default | Description |
-|---|---|---|---|
-| `--json` | bool | `False` | Emit machine-readable JSON output |
-
-#### Report Checks
-
-The report validates these dimensions:
-
-| Check | Pass Criteria |
-|---|---|
-| orchestrator count | Matches `len(ORCHESTRATORS)` in router |
-| legacy alias count | Zero removed aliases in workspace `pyproject.toml` `[project.scripts]` |
-| doc drift | No removed aliases or direct executables referenced in `cli-help-matrix.md` |
-| tool configs | `[tool.ruff]` and `[tool.mypy]` present in workspace `pyproject.toml` |
-| coverage gate | Any scanned `pyproject.toml` has `fail_under` > 0 |
-| anti-patterns | No `sys.exit()`, no `argparse`, no `click`, no bare `RuntimeError()` in `*/cli.py` |
-
-#### Example (human readable)
-
-```bash
-vds-cli lint cli
-```
-
-#### Example (JSON)
-
-```bash
-vds-cli lint cli --json
-```
-
-**Sample JSON output (partial):**
-
-```json
-{
-  "compliant": true,
-  "checks": {
-    "orchestrator_count": { "status": "pass", "value": 33 },
-    "legacy_alias_count": { "status": "pass", "value": 0 },
-    "doc_drift": { "status": "pass", "issues": [] },
-    "tool_configs": { "status": "pass", "ruff": true, "mypy": true },
-    "coverage_gate": { "status": "pass", "threshold": 70 },
-    "anti_patterns": { "status": "pass", "issues": [] }
-  }
-}
-```
-
-## Exit Codes
-
-| Code | Meaning |
-|---|---|
-| `0` | All checks pass |
-| `1` | One or more checks failed |
-
-## See Also
-
-- [CLI Development Standards](cli-development-standards.md) — governance rules and authoring checklist
-- [CLI Help Matrix](cli-help-matrix.md) — verified routed command inventory
-- `vds_cli/src/vds_cli/commands/lint_cli.py` — source implementation
-
----
-*Generated from `lint_cli.py` (Phase 179).*