@ngocsangairvds/vsaf 3.2.16 → 4.0.1

package/tools/vds-scripts/mcp_server/tests/verification/conftest.py

@@ -1,51 +0,0 @@
-"""Manual verification tests — skipped by default.
-
-These tests hit real external services (Confluence, Jira) via the MCP server
-and require ambient credentials.  They are NOT part of the default pytest suite.
-
-Run explicitly with::
-
-    pytest --run-verification mcp_server/tests/verification/
-
-Or set the environment variable::
-
-    VDS_RUN_VERIFICATION=1 pytest mcp_server/tests/verification/
-"""
-
-from __future__ import annotations
-
-import os
-
-import pytest
-
-
-def pytest_addoption(parser: pytest.Parser) -> None:
-    """Register ``--run-verification`` CLI flag."""
-    try:
-        parser.addoption(
-            "--run-verification",
-            action="store_true",
-            default=False,
-            help="Run manual verification tests that hit real services.",
-        )
-    except ValueError:
-        pass  # already registered by another conftest
-
-
-def pytest_collection_modifyitems(config: pytest.Config, items: list[pytest.Item]) -> None:
-    """Skip verification tests unless explicitly opted in.
-
-    Only targets items whose node ID contains ``verification/`` so that
-    the hook never accidentally skips non-verification tests when pytest
-    collects from a parent directory.
-    """
-    if os.environ.get("VDS_RUN_VERIFICATION") == "1":
-        return
-    if config.getoption("--run-verification", default=False):
-        return
-    skip_marker = pytest.mark.skip(
-        reason="Verification tests require --run-verification or VDS_RUN_VERIFICATION=1",
-    )
-    for item in items:
-        if "verification" in item.nodeid:
-            item.add_marker(skip_marker)

package/tools/vds-scripts/mcp_server/tests/verification/test_mcp_confluence_tools.py

@@ -1,40 +0,0 @@
-"""Real API verification tests for Confluence tools via MCP.
-
-Based on pytest v8.3.3+ API
-Context7: /pytest-dev/pytest
-Key Features: @pytest.mark.skipif, real API calls via MCP
-"""
-
-import os
-from typing import TYPE_CHECKING
-
-import pytest
-
-if TYPE_CHECKING:
-    from mcp.client.session import ClientSession
-
-# Skip if credentials not available
-pytestmark = pytest.mark.skipif(
-    not os.getenv("INTERNAL_CONFLUENCE_TOKEN") or not os.getenv("EXTERNAL_CONFLUENCE_TOKEN"),
-    reason="Confluence tokens not available",
-)
-
-
-@pytest.mark.anyio
-async def test_confluence_search_via_mcp(client_session: ClientSession) -> None:
-    """Verify Confluence search tool via MCP with real API."""
-    result = await client_session.call_tool(
-        "confluence_search", {"query": "space = TDOV", "server": "internal", "limit": 5}
-    )
-    # Verify result structure
-    assert result is not None
-
-
-@pytest.mark.anyio
-async def test_confluence_get_page_via_mcp(client_session: ClientSession) -> None:
-    """Verify Confluence get page tool via MCP with real API."""
-    # Note: This will fail if page ID doesn't exist
-    # In real scenario, use a valid page ID
-    result = await client_session.call_tool("confluence_get_page", {"page_id": "99647801", "server": "external"})
-    # Verify result structure
-    assert result is not None

package/tools/vds-scripts/mcp_server/tests/verification/test_mcp_jira_tools.py

@@ -1,39 +0,0 @@
-"""Real API verification tests for JIRA tools via MCP.
-
-Based on pytest v8.3.3+ API
-Context7: /pytest-dev/pytest
-Key Features: @pytest.mark.skipif, real API calls via MCP
-"""
-
-import os
-from typing import TYPE_CHECKING
-
-import pytest
-
-if TYPE_CHECKING:
-    from mcp.client.session import ClientSession
-
-# Skip if credentials not available
-pytestmark = pytest.mark.skipif(
-    not os.getenv("VDS_USERNAME") or not os.getenv("VDS_PASSWORD"),
-    reason="VDS credentials not available",
-)
-
-
-@pytest.mark.anyio
-async def test_jira_search_via_mcp(client_session: ClientSession) -> None:
-    """Verify JIRA search tool via MCP with real API."""
-    # Note: This will fail if vds-cli is not available or credentials are invalid
-    # In real scenario, this should return search results
-    result = await client_session.call_tool("jira_search", {"query": "project = NTTC", "limit": 5})
-    # Verify result structure
-    assert result is not None
-    # Note: Actual content depends on API response
-
-
-@pytest.mark.anyio
-async def test_jira_list_projects_via_mcp(client_session: ClientSession) -> None:
-    """Verify JIRA list projects tool via MCP with real API."""
-    result = await client_session.call_tool("jira_list_projects", {})
-    # Verify result structure
-    assert result is not None

package/tools/vds-scripts/mcp_server/tests/verification/test_mcp_tool_registration.py

@@ -1,50 +0,0 @@
-"""Verify MCP tool registration and discovery.
-
-Based on pytest v8.3.3+ API
-Context7: /pytest-dev/pytest
-"""
-
-from typing import TYPE_CHECKING
-
-import pytest
-
-if TYPE_CHECKING:
-    from mcp.client.session import ClientSession
-
-pytestmark = pytest.mark.anyio
-
-
-async def test_all_tools_registered(client_session: ClientSession) -> None:
-    """Verify all expected tools are registered."""
-    tools = await client_session.list_tools()
-    tool_names = {tool.name for tool in tools.tools}
-
-    # Expected tools
-    expected_tools = {
-        # JIRA tools
-        "jira_search",
-        "jira_get_issue",
-        "jira_list_projects",
-        # Confluence tools
-        "confluence_search",
-        "confluence_get_page",
-        # Bitbucket tools
-        "bitbucket_list_projects",
-        "bitbucket_list_repositories",
-        # Git tools
-        "git_clone",
-        "git_status",
-        "git_pull",
-    }
-
-    assert expected_tools.issubset(tool_names), f"Missing tools: {expected_tools - tool_names}"
-
-
-async def test_tool_schemas_valid(client_session: ClientSession) -> None:
-    """Verify tool schemas are valid."""
-    tools = await client_session.list_tools()
-
-    for tool in tools.tools:
-        assert tool.name, f"Tool missing name: {tool}"
-        assert tool.description, f"Tool {tool.name} missing description"
-        assert tool.inputSchema, f"Tool {tool.name} missing inputSchema"

package/tools/vds-scripts/memory_orchestrator/.env.example

@@ -1,109 +0,0 @@
-# =============================================================================
-# VDS Memory Orchestrator - Environment Configuration
-# =============================================================================
-# P0 Change (2026-04-25): Uses shared vds-postgres with memory schema.
-# Uses shared vds-redis with explicit DB allocation.
-# See docker/MIGRATION.md for migration details.
-# =============================================================================
-# Copy this file to .env and fill in your values
-# DO NOT commit .env to version control
-# =============================================================================
-
-# -----------------------------------------------------------------------------
-# Shared PostgreSQL (P0: Uses vds-postgres with memory schema)
-# -----------------------------------------------------------------------------
-# Connection uses search_path=memory for schema isolation.
-
-# Shared postgres password (from ~/.vds/.env or docker/infrastructure/.env)
-VDS_POSTGRES_PASSWORD=vds_postgres_secret
-
-# Memory orchestrator DSN (auto-constructed from template)
-# Format: postgresql://user:password@host:port/database?options=-c%20search_path=schema
-DATABASE_URL=postgresql://postgres:${VDS_POSTGRES_PASSWORD}@localhost:5432/vds_platform?options=-c%20search_path%3Dmemory
-
-# -----------------------------------------------------------------------------
-# Shared Redis Configuration (P0: Explicit DB allocation)
-# -----------------------------------------------------------------------------
-# Redis DB Allocation:
-#   DB 0: memory_orchestrator Celery broker
-#   DB 1: memory cache, sweeper
-#   DB 2: session store, ai_memory_service
-#   DB 3: analytics, tracker, search
-#   DB 4: search cache
-#   DB 5: rate limiting
-#   DB 6: tool discovery
-
-# Base Redis URL
-REDIS_URL=redis://localhost:6379
-
-# Individual Redis DB connections
-REDIS_CELERY_BROKER_DB=0
-REDIS_MEMORY_CACHE_DB=1
-REDIS_SESSION_STORE_DB=2
-REDIS_ANALYTICS_DB=3
-REDIS_SEARCH_CACHE_DB=4
-REDIS_RATE_LIMITING_DB=5
-REDIS_TOOL_DISCOVERY_DB=6
-
-# -----------------------------------------------------------------------------
-# Qdrant Configuration (P0: Uses shared vds-qdrant)
-# -----------------------------------------------------------------------------
-# VDS-internal Qdrant for mem0 (separate from grepai Qdrant)
-QDRANT_HOST=localhost
-QDRANT_PORT=6335
-QDRANT_GRPC_PORT=6336
-
-# -----------------------------------------------------------------------------
-# Embedding Configuration (Phase 225 — Pluggable Embedding via vds_agent_core)
-# -----------------------------------------------------------------------------
-# Phase 225 (DEPLOYED 2026-05-02, vds-scripts master 41798074) hoists embedding
-# provider config into vds_agent_core.llm.embedding via a 9-provider registry
-# (ollama / openai / cohere / voyage / mistral / jina / litellm / local / hash).
-# Operator config uses the canonical VDS_AGENT_CORE_EMBED__* namespace; the
-# legacy EMBEDDING_* names below remain for one cycle of back-compat per
-# FR-225.12 but are NOT consumed by the new pipeline — they only feed mem0's
-# own embedder config in mem0_adapter.py.
-#
-# See vds_agent_core/docs/embedding.md for provider matrix + cloud-failover
-# playbook + per-agent 3-layer cascade.
-
-# === Phase 225 canonical (preferred) ===
-VDS_AGENT_CORE_EMBED__PROVIDER=ollama
-VDS_AGENT_CORE_EMBED__BASE_URL=http://host.docker.internal:11434
-VDS_AGENT_CORE_EMBED__MODEL_STANDARD=bge-m3
-VDS_AGENT_CORE_EMBED__DIMENSION=1024
-# Set ``true`` to fail-open on Ollama unreachable (dev only):
-VDS_AGENT_CORE_EMBED__FAIL_OPEN=false
-# Set ``false`` to silence the Qdrant dim-stability validator at startup
-# (NFR-225.11 — emits WARN to logs and surfaces in vds-cli doctor):
-VDS_AGENT_CORE_EMBED__VERIFY_DIM_AGAINST_QDRANT=true
-
-# === Legacy back-compat (mem0 self-hosted embedder config only) ===
-# These continue to feed memory_orchestrator.service.services.mem0_adapter
-# until that adapter's own embedder is similarly hoisted.
-EMBEDDING_PROVIDER=ollama
-EMBEDDING_OLLAMA_URL=http://host.docker.internal:11434
-EMBEDDING_OLLAMA_MODEL=bge-m3
-EMBEDDING_LOCAL_MODEL=BAAI/bge-m3
-EMBEDDING_DIMENSION=1024
-
-# Mem0 API (for cloud-based mem0)
-MEM0_API_KEY=your_mem0_api_key_here
-
-# -----------------------------------------------------------------------------
-# Service Configuration
-# -----------------------------------------------------------------------------
-SERVICE_NAME=VDS AI Memory Service
-SERVICE_ENVIRONMENT=development
-PYTHONWARNINGS=ignore::DeprecationWarning:backoff.*:0,ignore::DeprecationWarning:fastapi_limiter.*:0,ignore::UserWarning:openai.*:0
-
-# -----------------------------------------------------------------------------
-# Celery Worker Configuration
-# -----------------------------------------------------------------------------
-CELERY_WORKER_CONCURRENCY=4
-MAX_TASKS_PER_CHILD=20
-
-# -----------------------------------------------------------------------------
-# MCP Server (Optional)
-# -----------------------------------------------------------------------------
-MCP_ENABLE_MCP_SERVER=false

package/tools/vds-scripts/memory_orchestrator/Dockerfile

@@ -1,103 +0,0 @@
-# syntax=docker/dockerfile:1.7-labs
-# =============================================================================
-# VDS Memory Orchestrator - Dockerfile
-# Build context: vds-scripts workspace root (one level above memory_orchestrator/)
-# Example: docker build -f memory_orchestrator/Dockerfile .. (from memory_orchestrator/)
-#          docker build -f WHO-project/vds-scripts/memory_orchestrator/Dockerfile WHO-project/vds-scripts/ (from vds/ root)
-# =============================================================================
-
-# VAMI-023 (FR-21.15, FR-21.23): pinned Python 3.13 — spaCy 3.8.14 has
-# no cp314 wheels, blocking `mem0ai[nlp]` + entity-linking auto-creation.
-# Only memory_orchestrator's container is pinned to the 3.13 line (latest
-# patch); rest of workspace runs 3.14.x. Deps (vds_agent_core/vds_cli_common/
-# vds_memory_client/platform_core) all support >=3.13 after the vds_agent_core
-# floor relaxation. Pin reason: heavy ML dep stack (mem0, sentence-transformers)
-# tested on 3.13; bumping to 3.14 requires retest.
-#
-# v2.15.14 standardization audit confirmed: STANDARDIZE-blocked. The single-
-# Dockerfile-with-3.13 vs all-others-on-3.14 asymmetry is intentional and
-# load-bearing on upstream cp314 wheel availability for spaCy + mem0ai[nlp].
-# Revisit when spaCy publishes cp314 wheels (track upstream).
-FROM python:3.13.13-slim
-
-ENV PYTHONDONTWRITEBYTECODE=1 \
-    PYTHONUNBUFFERED=1 \
-    UV_LINK_MODE=copy \
-    UV_COMPILE_BYTECODE=1 \
-    UV_PROJECT_ENVIRONMENT=/opt/venv \
-    UV_PYTHON=python3.13 \
-    PATH="/opt/venv/bin:$PATH" \
-    FASTEMBED_CACHE_DIR=/model-cache \
-    HF_HOME=/model-cache
-
-WORKDIR /app
-
-# Install system deps. Phase 224 deploy-hygiene removes postgresql-client:
-# the entrypoint's Postgres-liveness probe + advisory-lock now use python+psycopg
-# (already in /opt/venv via psycopg[binary]>=3.3.3) so no system psql is needed.
-# Saves ~20MB image size and one fewer DSN-format constraint to manage.
-RUN apt-get update && apt-get install -y --no-install-recommends \
-    git curl build-essential gcc g++ \
-    && rm -rf /var/lib/apt/lists/*
-
-# Install uv
-COPY --from=ghcr.io/astral-sh/uv:latest /uv /bin/uv
-
-# Copy entire vds-scripts workspace (needed for workspace dependency resolution)
-# Context is the workspace root; COPY . copies its contents into /app/
-COPY . /app/
-
-# Install memory_orchestrator with all extras using workspace-aware sync.
-# uv sync resolves workspace deps and installs them into /opt/venv.
-# Then we reinstall workspace packages from built wheels to guarantee site-packages
-# installation rather than editable links — editable links break at runtime when
-# compose.yaml mounts `- .:/app:cached` (memory_orchestrator/ only) over /app/,
-# orphaning paths like /app/platform_core/src/ that editable .pth files point to.
-RUN --mount=type=cache,target=/root/.cache/uv \
-    mkdir -p /app/logs /app/data /model-cache && \
-    uv venv --python 3.13 /opt/venv && \
-    uv pip install --python /opt/venv/bin/python \
-        /app/memory_orchestrator[server,celery,mem0,auth,nlp,embeddings] \
-        /app/vds_cli_common \
-        /app/vds_memory_client \
-        /app/vds_agent_core \
-        /app/platform_core && \
-    # Build wheels for packages that uv sync installs as editable links.
-    # Installing from .whl (not a directory path) forces site-packages placement —
-    # no editable variant possible — surviving the compose volume overlay.
-    uv build --wheel /app/platform_core --out-dir /tmp/wheels && \
-    uv build --wheel /app/vds_cli_common --out-dir /tmp/wheels && \
-    uv build --wheel /app/vds_memory_client --out-dir /tmp/wheels && \
-    uv pip install --python /opt/venv/bin/python --reinstall /tmp/wheels/*.whl
-
-# VAMI-024 B3 fix: pre-warm the Qdrant/bm25 fastembed model into /model-cache
-# during image build so the first `memory search` query after container start
-# doesn't stall downloading 18 stopword files from HuggingFace. The subsequent
-# chown step gives appuser read access. Without this the first post-restart
-# search can take tens of seconds on a cold HF cache.
-RUN /opt/venv/bin/python -c "from fastembed import SparseTextEmbedding; SparseTextEmbedding('Qdrant/bm25'); print('fastembed BM25 model pre-warmed into /model-cache')"
-
-# Phase 225 (ADR-98) removed bge-m3 bake — embeddings now ride host Ollama
-# via vds_agent_core.llm.embedding.EmbeddingClient. Image <=14 GB target.
-
-# Create non-root user for runtime security
-RUN groupadd -r appuser && useradd -r -g appuser -d /home/appuser -s /sbin/nologin appuser && \
-    mkdir -p /home/appuser /app/logs /app/data /model-cache && \
-    chown -R appuser:appuser /home/appuser /app/logs /app/data /model-cache /opt/venv
-
-# Health check: start_period bumped to 60s to absorb alembic upgrade window
-# on first-time bring-up against an empty vds_platform.memory schema.
-HEALTHCHECK --interval=30s --timeout=10s --start-period=60s --retries=3 \
-    CMD curl -f http://localhost:8000/health || exit 1
-
-EXPOSE 8000
-
-USER appuser
-
-ENTRYPOINT ["/app/memory_orchestrator/scripts/entrypoint.sh"]
-# Default CMD is uvicorn (memory-api). memory-worker overrides via compose
-# `command:` to run celery (FR-224.6 dispatch contract). The entrypoint
-# exec's "$@", so any CMD reaches the runtime as PID 1 child.
-CMD ["/opt/venv/bin/python", "-m", "uvicorn", \
-     "vds_memory_orchestrator.service.main:app", \
-     "--host", "0.0.0.0", "--port", "8000"]

package/tools/vds-scripts/memory_orchestrator/README.md

@@ -1,203 +0,0 @@
-# VDS Memory Orchestrator
-
-CLI client for VDS AI Memory (`WHO-project/vds-ai-memory/`) — search, store, and manage cross-session memories from Claude Code.
-
-Spec: `VAMI-001` (v1.2.0) at `.gpt-5.4/specs/vds-ai-memory-integration/`.
-
-## Quick Start
-
-```bash
-# Prerequisite: start the Docker stack (cross-worktree safe; Phase 176 wrapper)
-./scripts/worktree_compose.sh up
-# Note: post ecosystem-infrastructure-evolution v2.10.0, the canonical entry
-# is the unified Makefile + three-tier compose (`make up-memory` from
-# vds-scripts/). `worktree_compose.sh` and the `vds-ai-memory` standalone
-# compose project remain for the parallel mem0 deploy stack documented by
-# mem0-deploy-skill (separate runtime, port 6380 redis, kept for legacy ops).
-
-# Health check
-vds-cli memory health
-
-# Store a decision
-vds-cli memory store "PAR billing uses Spring Boot 3.2" \
-  --category code --importance high --tags spring-boot,PAR
-
-# Search by meaning (semantic, cross-session)
-vds-cli memory search "PAR billing architecture" --limit 5
-
-# Retrieve by ID
-vds-cli memory get pg_abc123-...
-
-# List sessions / stats
-vds-cli memory sessions
-vds-cli memory --json-only stats
-```
-
-## Commands
-
-| Command | Description | Session Required |
-|---------|-------------|:---:|
-| `search <query>` | Semantic search across all sessions (~450ms, Mem0/pgvector) | No |
-| `store <content>` | Store a decision, fact, or evidence | Yes (auto-created) |
-| `get <id>` | Retrieve a specific memory by ID | No |
-| `sessions` | List sessions for the current user | No |
-| `health` | Check Docker stack and API health | No |
-| `stats` | Show memory count, session count, Redis status | No |
-
-## Configuration
-
-| Option | Env Var | Default | Description |
-|--------|---------|---------|-------------|
-| `--api-url` | `VDS_MEMORY_API_URL` | `VDS_MEMORY_API_URL` → `http://localhost:${API_PORT}` → `http://localhost:8000` | API base URL |
-| `--user-id` | `VDS_MEMORY_USER_ID` | `claude-agent` | User ID for API calls |
-| `--json-only` | — | `false` | Machine-readable JSON output |
-| `--quiet` | — | `false` | Suppress non-essential output |
-| `--category` | — | `general` | Memory category (store) |
-| `--importance` | — | `medium` | low / medium / high / critical (store) |
-| `--tags` | — | — | Comma-separated, stored in `metadata.tags` |
-| `--limit` | — | `10` | Max search results |
-
-**UX note**: `--json-only` and `--quiet` are global callback options — place them before the subcommand: `./scripts/worktree_uv.sh run --project vds_cli vds-cli memory --json-only search "query"`.
-
-## Session Management
-
-`store` requires `session_id` (API returns 422 without one). The client handles this automatically:
-
-1. In-memory cache hit → return immediately
-2. File cache (`~/.vds/.memory-session.json`) → validate with API → return if active
-3. Expired or missing → `POST /api/v1/sessions` (24h TTL, API cap)
-4. Atomic write: `tempfile` → `os.replace()` to prevent corruption
-5. JSON parse error → graceful recovery (treats as expired, creates new)
-
-`search` does NOT require a session — returns results globally across all sessions.
-
-## Tags
-
-Tags are stored in `metadata.tags`. The API accepts a top-level `tags` field syntactically but does not persist it (live-verified). The CLI maps `--tags` to `metadata.tags` automatically.
-
-Valid categories: `general`, `validation`, `security`, `session-summary`, `error`, `performance`, `hook-insight`, `business-logic`, `api-call`, `debug`, `user-preference`, `personal`, `work`, `project`, `meeting`, `research`, `note`, `idea`, `task`, `reference`, `tutorial`, `code`, `document`, `email`, `chat`, `web`, `other`.
-
-## Architecture
-
-```
-vds-cli memory search "query"
-    ↓
-vds_cli/router.py → ORCHESTRATORS["memory"]
-    ↓
-./scripts/worktree_uv.sh run --project vds_cli vds-cli memory search "query"
-    ↓
-cli.py (202L) → asyncio.run(client.search(...))
-    ↓
-client.py (236L) → httpx POST ${VDS_MEMORY_API_URL:-http://localhost:${API_PORT:-8000}}/api/v1/memories/search
-    ↓
-VDS AI Memory API → Mem0/pgvector semantic search (~450ms)
-    ↓
-formatters.py (82L) → Rich table with importance color-coding
-```
-
-This is a **thin HTTP client** (~520 lines total). The VDS AI Memory service runs as a separate Docker stack (56K LOC, Python 3.12, FastAPI + PostgreSQL/pgvector + Redis + Celery).
-
-## Multi-Agent Integration
-
-The `multi_agent_orchestrator` in the same workspace has its own VDS AI Memory client (`vds_ai_memory_client.py`, 319 lines) with convenience methods:
-
-- `store_agent_decision()` — importance=HIGH, category=BUSINESS_LOGIC
-- `store_critical_milestone()` — importance=CRITICAL, category=SESSION_SUMMARY
-- `store_error()` — importance=HIGH, category=ERROR
-- `search_agent_context()` — cross-agent memory search
-
-Both clients call the same API. A decision stored by a 16-agent team is searchable from `vds-cli memory search`.
-
-## Auto-Persistence Hooks
-
-Three Claude Code hooks complement the CLI (registered in `.claude/settings.local.json`):
-
-| Hook | Event | Timeout | Purpose |
-|------|-------|---------|---------|
-| `memory_session_context.py` | SessionStart | 5s | Pre-load relevant prior decisions at session start |
-| `memory_persist_stop.py` (153L) | Stop | 30s | Auto-persist session summary + extract up to 5 decisions |
-| `memory_intent_detect.py` (40L) | UserPromptSubmit | 3s | Detect "remember/save to memory/store this" → inject CLI hint |
-
-Both are fail-open (exit 0 on any error). The Stop hook imports httpx (scoped exception to the stdlib-only hook convention).
-
-## Testing
-
-```bash
-# Unit tests (mocked, fast)
-uv run --project memory_orchestrator pytest memory_orchestrator/tests/ -v
-# → 31 passed, 3 skipped, 88% coverage (client 93%, cli 84%, formatters 91%)
-
-# Live verification (requires running API)
-VDS_MEMORY_LIVE_TESTS=1 uv run --project memory_orchestrator \
-  pytest memory_orchestrator/tests/verification/ --run-verification
-# → 3 passed (health, store+search, sessions)
-
-# Health check (16 checks across 5 Docker containers)
-bash scripts/vds-memory-health.sh
-
-# E2E integration (25 checks, 4 phases)
-bash scripts/test-vami-001.sh
-```
-
-## Port Allocation
-
-| Port | Service | Notes |
-|------|---------|-------|
-| 5432 | vds-postgres (shared) | VDS AI Memory database (memory schema) |
-| 6379 | vds-redis (shared) | Cache and session store |
-| 8000 | memory-api (FastAPI) | REST API |
-
-## Dependencies
-
-- `typer>=0.24.1` — CLI framework
-- `httpx>=0.28.1` — Async HTTP client
-- `rich>=14.3.3` — Terminal formatting
-- `vds-cli-common` — Shared CLI infrastructure (CLIContext, OutputManager, ErrorHandler)
-- `pytest-asyncio>=0.25.0` (dev) — Async test support
-
-## Operational Notes
-
-### Logging
-
-#### SQLAlchemy SQL Echo (G3 — Phase 177)
-
-By default, SQLAlchemy **does not echo SQL statements** regardless of the `ENVIRONMENT` setting.
-SQL echo is now gated behind a dedicated opt-in env var so debug environments no longer flood
-logs with every query.
-
-| Env Var | Effect | Default |
-|---------|--------|---------|
-| `VDS_DB_ECHO=true` | Enable SQLAlchemy `echo=True` for all engines | Off |
-| `SQLALCHEMY_ECHO=true` | Legacy alias (honoured when `VDS_DB_ECHO` is absent) | Off |
-
-To enable SQL echo for a debugging session:
-
-```bash
-export VDS_DB_ECHO=true
-docker compose restart api worker beat
-```
-
-To disable again:
-
-```bash
-unset VDS_DB_ECHO
-docker compose restart api worker beat
-```
-
-**Why this changed**: Previously `echo` was tied to `service.debug`, which is `True` in all
-`development` and `testing` environments. This produced hundreds of DEBUG lines per request and
-made it hard to spot actual errors in `docker compose logs api`.
-
-#### Celery Worker stdout Redirect Level (G3 — Phase 177)
-
-`worker_redirect_stdouts_level` is set to `"INFO"` (Celery default is `"WARNING"`).
-
-Third-party libraries inside worker processes often call `print()` for informational output.
-With the default `WARNING`, these appear in alert channels as false positives. At `INFO` they
-are visible in logs but do not trigger severity-based alerts.
-
-To observe worker stdout output at INFO level:
-
-```bash
-docker compose logs worker --follow | grep INFO
-```

package/tools/vds-scripts/memory_orchestrator/alembic/env.py

@@ -1,35 +0,0 @@
-"""memory_orchestrator Alembic env — see ADR-INF-11 + ADR-INF-12.
-
-Refactored from 170 LOC to ~25 LOC by WP-5.2. All boilerplate delegated to
-vds_platform_core.alembic.runtime. Design choices and SA2.0 implicit-tx
-gotcha documented in ADR-INF-11. Full history at commit 8997f8ca.
-"""
-
-from logging.config import fileConfig
-
-from vds_platform_core.alembic import (
-    resolve_database_url,
-    run_migrations_offline,
-    run_migrations_online,
-)
-
-from alembic import context
-from vds_memory_orchestrator.db.alembic_filters import include_name
-from vds_memory_orchestrator.service.models.database import Base
-
-config = context.config
-if config.config_file_name is not None:
-    fileConfig(config.config_file_name)
-
-URL = resolve_database_url(env_var="DATABASE_URL")
-KW = {
-    "target_metadata": Base.metadata,
-    "schema": "memory",
-    "url": URL,
-    "include_name": include_name,
-}
-
-if context.is_offline_mode():
-    run_migrations_offline(**KW)
-else:
-    run_migrations_online(**KW, alembic_config=config)

package/tools/vds-scripts/memory_orchestrator/alembic/script.py.mako

@@ -1,28 +0,0 @@
-"""${message}
-
-Revision ID: ${up_revision}
-Revises: ${down_revision | comma,n}
-Create Date: ${create_date}
-
-"""
-from __future__ import annotations
-
-from typing import Sequence, Union
-
-from alembic import op
-import sqlalchemy as sa
-${imports if imports else ""}
-
-# revision identifiers, used by Alembic.
-revision: str = ${repr(up_revision)}
-down_revision: Union[str, None] = ${repr(down_revision)}
-branch_labels: Union[str, Sequence[str], None] = ${repr(branch_labels)}
-depends_on: Union[str, Sequence[str], None] = ${repr(depends_on)}
-
-
-def upgrade() -> None:
-    ${upgrades if upgrades else "pass"}
-
-
-def downgrade() -> None:
-    ${downgrades if downgrades else "pass"}