@ngocsangairvds/vsaf 3.2.16 → 4.0.0

package/tools/vds-scripts/scheduler_orchestrator/Dockerfile

@@ -1,110 +0,0 @@
-# syntax=docker/dockerfile:1.7-labs
-# =============================================================================
-# VDS Scheduler Orchestrator - Dockerfile
-# Phase: ecosystem-infrastructure-evolution P1 (FR-4)
-#
-# Build context: vds-scripts workspace root
-# Example: docker build -f WHO-project/vds-scripts/scheduler_orchestrator/Dockerfile WHO-project/vds-scripts/
-#
-# Runtime contract:
-#   - DBOS Transact requires CREATE on the `dbos` schema (init-schemas.sql grants this to vds_sched_runtime)
-#   - DATABASE_URL must point to shared postgres with search_path=sched
-#   - REDIS_URL targets shared redis DB 8 (reserved for scheduler)
-#   - VDS_SCHEDULER_ENABLED kill-switch defaults to false in ~/.vds/.env
-# =============================================================================
-
-FROM python:3.14.4-slim
-
-ENV PYTHONDONTWRITEBYTECODE=1 \
-    PYTHONUNBUFFERED=1 \
-    UV_LINK_MODE=copy \
-    UV_COMPILE_BYTECODE=1 \
-    UV_PROJECT_ENVIRONMENT=/opt/venv \
-    PATH="/opt/venv/bin:$PATH"
-
-WORKDIR /app
-
-# System deps: git for any VCS-based pip pulls; curl for healthcheck; psql for liveness wait + advisory-lock SQL
-RUN apt-get update && apt-get install -y --no-install-recommends \
-    git curl build-essential postgresql-client \
-    && rm -rf /var/lib/apt/lists/*
-
-# uv for workspace-aware dependency resolution
-COPY --from=ghcr.io/astral-sh/uv:latest /uv /bin/uv
-
-# Copy scheduler package + workspace deps.
-# v2.0.17 N.39: vds_evolution required for evolution.auto-promote workflow body.
-# v2.0.17 N.56 Option B-lite: vds_cli intentionally NOT copied — it pulls
-#   vds_bitbucket_orchestrator + cascading deps. Instead, vds_evolution.auto_promote
-#   has graceful degradation that fail-softs when vds-cli is not on PATH (logs
-#   warning, returns False). Full automation requires vds-cli; the container
-#   logs the gap so operators can decide to install it later.
-COPY scheduler_orchestrator/pyproject.toml /app/scheduler_orchestrator/
-COPY scheduler_orchestrator/README.md /app/scheduler_orchestrator/
-COPY scheduler_orchestrator/src /app/scheduler_orchestrator/src
-COPY scheduler_orchestrator/alembic /app/scheduler_orchestrator/alembic
-COPY scheduler_orchestrator/alembic.ini /app/scheduler_orchestrator/
-COPY scheduler_orchestrator/scripts /app/scheduler_orchestrator/scripts
-
-COPY vds_cli_common /app/vds_cli_common
-COPY vds_evolution /app/vds_evolution
-# P5 WP-5.2 / ADR-INF-12: scheduler env.py imports from vds_platform_core.alembic.runtime
-COPY platform_core /app/platform_core
-# vds-scheduler v0.2.0+ (ADR-DCP-1): scheduler depends on
-# vds-agent-core[workflows] for the WorkflowProvider Protocol + relocated
-# run_langgraph step. Workspace dep, must be installed alongside the others.
-COPY vds_agent_core /app/vds_agent_core
-
-# Phase 4: workspace uv.lock needed by SecurityAdvisoryCollector to enumerate
-# installed packages and match them against NVD CVEs.
-COPY uv.lock /app/uv.lock
-# Phase 217 (ADR-77/79): Phase 213's memory_orchestrator + vds_memory_client
-# COPY+install was reverted here. Scheduler workflows now POST to memory-api
-# via httpx instead of lazy-importing memory_orchestrator. Net effect: removes
-# ~200-300MB image bloat AND restores the standalone-orchestrator boundary.
-# The 6 memory-evolution workflows in workflows/memory_evolution/*.py call
-# memory-api's /api/v1/maintenance/* endpoints with VDS_SCHEDULER_SERVICE_TOKEN
-# bearer auth (per ADR-77 service-account JWT decision).
-
-# Install scheduler + workspace deps into /opt/venv
-# v2.0.17: psycopg2-binary added as a runtime dep because alembic env.py uses
-# sqlalchemy's sync driver path; the scheduler runtime uses asyncpg (async),
-# but the entrypoint's `alembic upgrade head` requires sync. psycopg2-binary
-# is a wheel-distributed sync driver (no system libpq build deps).
-RUN --mount=type=cache,target=/root/.cache/uv \
-    mkdir -p /app/logs && \
-    uv venv --python 3.14 /opt/venv && \
-    uv pip install --python /opt/venv/bin/python --no-sources \
-        /app/vds_cli_common \
-        /app/vds_evolution \
-        /app/platform_core \
-        /app/vds_agent_core[workflows] \
-        /app/scheduler_orchestrator && \
-    uv pip install --python /opt/venv/bin/python psycopg2-binary httpx
-
-# Non-root user
-# H4 fix: create /opt/reports at build time so Docker populates a fresh named
-# volume with scheduler:scheduler ownership (not root) on first container start.
-RUN groupadd -r scheduler && useradd -r -g scheduler -d /home/scheduler -s /sbin/nologin scheduler && \
-    mkdir -p /home/scheduler /app/logs /opt/reports && \
-    chown -R scheduler:scheduler /home/scheduler /app/logs /opt/venv /opt/reports
-
-# Healthcheck: scheduler exposes a FastAPI /health endpoint on port 8005.
-# v2.0.17 N.40: start_period bumped from 20s -> 60s to absorb the entrypoint's
-# alembic upgrade window on first-time bring-up against an empty vds_platform.sched.
-HEALTHCHECK --interval=30s --timeout=10s --start-period=60s --retries=3 \
-    CMD curl -f http://localhost:8005/health || exit 1
-
-EXPOSE 8005
-
-USER scheduler
-
-# v2.0.17 N.40: entrypoint runs alembic upgrade head (advisory-locked, with
-# Postgres-liveness wait + LangGraph isolation guard + GRANT/REVOKE re-apply
-# per ADR-19) before exec'ing uvicorn. Migration runs with MIGRATION_DATABASE_URL
-# (superuser DSN) if set; runtime uvicorn uses DATABASE_URL (least-privilege).
-CMD ["/app/scheduler_orchestrator/scripts/entrypoint.sh"]
-
-LABEL org.opencontainers.image.title="VDS Scheduler Orchestrator" \
-      org.opencontainers.image.description="DBOS-backed durable scheduler for cron + interval workflows" \
-      org.opencontainers.image.created="2026-04-25"

package/tools/vds-scripts/scheduler_orchestrator/GV-VERIFICATION.md

@@ -1,81 +0,0 @@
-# Graph-Verified Safety Claims — Phase 1 (TSK-N.3)
-
-**Verified**: 2026-04-24  
-**Branch**: `feature/ecosystem-scheduling-phase1`  
-**Canonical record**: `WHO-project/vds-scripts/scheduler_orchestrator/CLOSURE-v2.0.18.md` (Phase 0 of `.gpt-5.4/specs/vds-scheduler/`; predecessor record `CLOSURE-PHASE-1.md` removed with the original `ecosystem-scheduling/` spec dir on 2026-05-01)
-
-These four checks gate Phase 1 merge per `design.md §Graph-Verified Safety Claims`.
-
----
-
-## GV-1: No existing component imports `vds_scheduler_orchestrator`
-
-**Claim**: No existing ecosystem component imports from `scheduler_orchestrator`.  
-**Method**: GitNexus `mcp__mcp-router__impact` + manual grep.  
-**Result**: ✅ `impactedCount: 0`
-
-GitNexus returned `"Target 'vds_scheduler_orchestrator' not found"` — the package is
-new and not yet in the graph index, which itself confirms no consumer relationship exists.
-Manual verification:
-
-```
-grep -r "vds_scheduler_orchestrator" \
-    audit_orchestrator/src memory_orchestrator/src \
-    research_orchestrator/src vds_cli/src platform_core/src \
-    --include="*.py"
-```
-
-→ **zero import matches** across all existing orchestrators.
-
----
-
-## GV-2: `scheduler_orchestrator` only imports public workspace surfaces
-
-**Claim**: `scheduler_orchestrator` does not import from `vds_memory_orchestrator`
-or `audit_orchestrator` internals — only their public Protocol surfaces.  
-**Method**: grep of `scheduler_orchestrator/src/` for cross-package imports.  
-**Result**: ✅ Zero cross-orchestrator imports
-
-```
-grep -r "from vds_|import vds_" scheduler_orchestrator/src/ --include="*.py" \
-    | grep -v "vds_scheduler_orchestrator\|vds_cli_common"
-```
-
-→ **zero matches**. Phase 1 imports only: `dbos`, `langgraph`, `sqlalchemy`,
-`alembic`, `fastapi`, `typer`, `structlog`, `pydantic`, `vds_cli_common`.
-No internal modules from any other orchestrator are referenced.
-
----
-
-## GV-3: Alembic `env.py` filter correctly excludes `dbos.*`
-
-**Claim**: `include_name` callback blocks `dbos.*` from autogenerate.  
-**Method**: Unit tests in `tests/unit/test_alembic_include_name.py`.  
-**Result**: ✅ 17 unit tests pass; filter proven in isolation
-
-Key assertions:
-- `include_name("dbos", "schema", {})` → `False` (AC#2 in test file)
-- `include_name("sched", "schema", {})` → `True` (AC#1)
-- All non-`sched` schemas → `False` (AC#3–#6)
-
-Additionally, Wave 1 TSK-1.3 (commit `c6826e42`) confirmed an **empty autogenerate
-diff** after running all 7 domain-table migrations — proving no `dbos.*` tables
-leaked into the migration output.
-
----
-
-## GV-4: Chain resolver rejects cycles at registration time
-
-**Claim**: `check_no_cycle()` raises `CycleDetectedError` before any cycle is
-committed to `sched.chain_definitions`.  
-**Method**: Unit tests in `tests/unit/test_chains_registry.py`.  
-**Result**: ✅ Kahn's algorithm rejects direct and indirect cycles
-
-Key test coverage:
-- **AC#6** — linear chain A→B→C: no cycle raised (positive path)
-- **AC#7** — direct cycle A→B + B→A: raises `CycleDetectedError`
-- **AC#8** — indirect cycle A→B, B→C, C→A: raises `CycleDetectedError`
-- **AC#10** — `CycleDetectedError.cycle_hint` lists the involved node names
-
-Implementation: `resolver.py` `kahn_topological_sort()` + `check_no_cycle()` called
-by `chains/registry.py` before any `INSERT` into `sched.chain_definitions`.

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

@@ -1,96 +0,0 @@
-# scheduler_orchestrator
-
-Durable ecosystem scheduling for the VDS platform. Built on **DBOS Transact 2.19.x** (L1 durable workflow engine) and **LangGraph 1.1.9** (L2 agent-graph internals), with all state stored in Postgres (`sched.*` schema).
-
-## Single Scheduler (post-2026-04-24)
-
-The VDS platform now runs **one** periodic scheduler: this package. Celery Beat was retired by ADR-14 on 2026-04-24 (commit `a0ba4179`). The 6 ex-Celery `memory_evolution` periodic tasks were migrated to DBOS schedules in `scheduler_orchestrator` per the Phase 3 migration plan (TSK-12.1..12.7). See `WHO-project/vds-scripts/scheduler_orchestrator/CLOSURE-v2.0.18.md` for the cutover record.
-
-| Concern | Owner | Notes |
-|---|---|---|
-| All periodic schedules (cron + interval) | `scheduler_orchestrator` (this package) | Owns 7+ DBOS schedules: `memory.evolution.{dispatch,sweep,replay-dlq}`, `mem0.{resolve-pending-ids,repush-stalled,repush-local-only}`, `evolution.auto-promote`, `scheduler.autoscale`, plus audit/progress/chain workflows |
-| Ad-hoc Celery task dispatch | Celery worker in `memory_orchestrator` (worker only — beat retired) | The Celery worker plumbing is intentionally retained for explicit `.delay()` / `.send_task()` dispatch from production code. Not a scheduler. See RETIREMENT-EXECUTED.md §Scope Clarification. |
-
-**design.md ADR-4 history**: ADR-4 originally documented the two-scheduler coexistence pattern as a Phase 1 simplification with planned Phase 3 migration. ADR-14 superseded the staged-soak migration plan with a direct cutover (user directive: "perform complete migration, do not keep any legacy"). ADR-4 + ADR-14 remain in design.md as decision history.
-
-**Do NOT add new periodic schedules to Celery** — `beat_schedule` is intentionally empty `{}` post-retirement; tests assert this. All new periodic tasks register in `scheduler_orchestrator/workflows/` per the DBOS schedule pattern.
-
-## Master Kill-Switch
-
-This package is a **module library**. It does **NOT** auto-start.
-
-```bash
-# Required to activate the scheduler (default is false):
-VDS_SCHEDULER_ENABLED=true
-```
-
-When `VDS_SCHEDULER_ENABLED=false` (the default), the package imports correctly but all scheduling operations are no-ops. Celery Beat and the Evolution daemon are completely unaffected.
-
-## Quick Start (development)
-
-```bash
-# From the worktree root:
-./scripts/worktree_uv.sh sync --all-packages
-
-# Start the FastAPI dev server (requires Postgres + DBOS_APP_VERSION set):
-VDS_SCHEDULER_ENABLED=true \
-VDS_SCHEDULER_DATABASE_URL=postgresql://... \
-./scripts/worktree_uv.sh run --project scheduler_orchestrator \
-  fastapi dev src/vds_scheduler_orchestrator/app.py
-
-# Health check (liveness):
-curl http://localhost:8005/health
-
-# Detailed health (v2.0.13 TSK-N.21 — DBOS + DB + schedule counts):
-curl http://localhost:8005/api/v1/health/full
-```
-
-## CLI
-
-The scheduler registers as a `vds-cli` subcommand group. All HTTP-mediated
-subcommands default to `http://localhost:8005` (v2.0.13 TSK-N.20 reconciled
-with DEPLOYMENT-RUNBOOK Stage 3); override via `VDS_SCHEDULER_BASE_URL`:
-
-```bash
-./scripts/worktree_uv.sh run --project vds_cli vds-cli scheduler schedules list
-vds-cli scheduler schedules create weekly-audit --cron "0 2 * * 1" --workflow audit.drift.weekly
-vds-cli scheduler workflows registry list
-vds-cli scheduler workflows list
-vds-cli scheduler events tail --topic "audit.*"
-vds-cli scheduler chains list
-```
-
-## HTTP API Surface (v2.0.13 TSK-N.21 — read-only)
-
-| Method | Route | Purpose |
-|---|---|---|
-| GET | `/health` | Liveness probe |
-| GET | `/metrics` | Prometheus scrape |
-| GET | `/api/v1/health/full` | Multi-layer health (DBOS + DB + counts) |
-| GET | `/api/v1/schedules` | List all schedules |
-| GET | `/api/v1/schedules/{name}` | Show one schedule |
-| GET | `/api/v1/chains` | List chain definitions |
-| GET | `/api/v1/chains/{name}` | Show one chain |
-| GET | `/api/v1/workflows` | List recent workflows (filterable by status) |
-| GET | `/api/v1/workflows/{id}` | Show one workflow by DBOS uuid |
-| GET | `/api/v1/workflow-registry` | List alias registry |
-| GET | `/api/v1/workflow-registry/{alias}` | Resolve alias → FQN |
-| GET | `/api/v1/events` | Tail events outbox |
-
-Write endpoints (POST/PATCH/DELETE schedules; POST events) are deferred to
-v2.0.14 per `.gpt-5.4/specs/vds-scheduler/tasks.md` §TSK-N.24..N.27.
-
-## Phase 1 Scope
-
-Phase 1 delivers the MVP: package structure, DBOS wiring, domain tables (Alembic), workflow registry, and CLI scaffolding. See `design.md §Program Phase Plan` for the full 4-phase program.
-
-## Architecture
-
-```
-L0: Postgres (sched.* schema)     — schedules, events outbox, subscriptions, chains
-L1: DBOS Transact                 — durable execution, workflow replay, cron scheduling
-L2: LangGraph                     — agent-graph internals (AsyncPostgresSaver)
-CLI: vds-cli scheduler ...        — operator interface
-```
-
-See `design.md` for ADRs, data model, and component inventory.

package/tools/vds-scripts/scheduler_orchestrator/WAVE-2-GUARDRAILS.md

@@ -1,89 +0,0 @@
-# Wave 2 Guardrails — Inherited from Wave 1 (TSK-N.5 / TSK-1.4)
-
-This file is left for Wave 2 teammates by the Wave 1 scaffolder.
-Read it before implementing TSK-2.1 (schedule CRUD) and TSK-6.1 (`schedule trigger-now` CLI).
-
----
-
-## GUARDRAIL 1: `trigger-now` CLI must NOT use `DBOS.trigger_schedule()`
-
-**Background (TSK-N.5 Check 6, CLOSURE-PHASE-1.md)**
-
-`DBOS.trigger_schedule(schedule_name)` enqueues the workflow on an **internal DBOS queue**, NOT
-the schedule's configured `queue_name`. The method signature is:
-
-```python
-DBOS.trigger_schedule(schedule_name: str) -> WorkflowHandle[None]
-```
-
-There is no `queue_name` parameter. Even if the schedule was created with
-`DBOS.create_schedule(..., queue_name="agent-default")`, calling
-`trigger_schedule()` bypasses that queue and uses an internal queue that
-does NOT respect the configured rate limits or concurrency bounds.
-
-**Required implementation for `vds-cli schedule trigger-now <name>`:**
-
-```python
-# Correct — respects queue_name, rate limits, concurrency
-from dbos import DBOS, Queue, SetEnqueueOptions
-
-schedule_row = fetch_schedule(schedule_name)           # from sched.schedules
-workflow_fn  = resolve_alias(schedule_row.workflow_fqn) # from sched.workflow_registry
-queue        = Queue(schedule_row.queue_name or "ops-default")
-handle       = queue.enqueue(workflow_fn, schedule_row.context_json or {})
-return handle.workflow_id
-
-# WRONG — do NOT do this:
-# handle = DBOS.trigger_schedule(schedule_name)   # bypasses queue_name!
-```
-
-**Spec reference**: design.md §Check 6 note, CLOSURE-PHASE-1.md §Check 6,
-requirements.md FR-12.4 (dedup via dispatch_ack_log lookup).
-
----
-
-## GUARDRAIL 2: Deduplication ID release timing is not explicitly documented
-
-**Background (TSK-N.5 Check 10)**
-
-DBOS documentation confirms that `DBOSQueueDeduplicatedError` is raised when
-a workflow with the same `deduplication_id` is currently `ENQUEUED` or `PENDING`.
-When it reaches a terminal state (SUCCESS / ERROR / CANCELLED), the ID is released
-but this is **not explicitly stated** in public docs — it is inferred.
-
-**For TSK-3.2 (dispatcher deduplication) and FR-12.5 (retention bookkeeping):**
-
-- The dispatcher's idempotency check (`sched.dispatch_ack_log`) is safe regardless
-  of this ambiguity — it is our own table, independent of DBOS deduplication.
-- The `sched.dispatch_ack_log` INSERT uses `ON CONFLICT (subscription_id, event_id) DO NOTHING`
-  — this is the authoritative dedup gate, not DBOS's native dedup.
-- FR-12.5 purge job JOINs `sched.dispatch_ack_log` with `dbos.workflow_status` before
-  deleting rows — safe even if DBOS dedup ID semantics are fuzzy.
-
-**Spec reference**: CLOSURE-PHASE-1.md §Check 10, requirements.md FR-12.5.
-
----
-
-## GUARDRAIL 3: `DBOSQueueDeduplicatedError` — do not rely on `workflow_id` attribute
-
-**Background (TSK-N.5 Check 7)**
-
-The import path is:
-```python
-from dbos import error as dboserror
-# dboserror.DBOSQueueDeduplicatedError
-```
-
-Whether the exception carries the existing workflow's ID is **not documented** in public API.
-Do NOT write code that accesses `e.workflow_id` or `e.existing_workflow_id`. Instead, use the
-`sched.dispatch_ack_log` table to look up the existing enqueue (FR-12.4 design).
-
----
-
-## Context
-
-These guardrails were discovered during TSK-N.5 (DBOS API live-verification, 2026-04-24)
-and confirmed during TSK-1.4 (smoke workflow implementation). See CLOSURE-PHASE-1.md
-§DBOS-API-Verification for the full 10-check evidence record.
-
-Wave 1 commits: 7ea13fd4 (1.1), a091516a (1.2), c6826e42 (1.3), and the TSK-1.4 commit.

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

@@ -1,41 +0,0 @@
-"""scheduler_orchestrator Alembic env — see ADR-INF-11 + ADR-INF-12.
-
-Refactored from 138 LOC to ~25 LOC by WP-5.2. All boilerplate delegated to
-vds_platform_core.alembic.runtime. Design choices documented in ADR-INF-11.
-
-ADR-INF-11 §version_table_schema Policy: version_table_schema="sched" is
-passed EXPLICITLY to both offline and online paths (WP-5.1 contract). Even
-though the schema string equals the schema name, the explicit pass-through
-documents the deliberate in-schema policy for scheduler.
-"""
-
-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_scheduler_orchestrator.db.alembic_filters import include_name
-from vds_scheduler_orchestrator.db.models 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": "sched",
-    "url": URL,
-    "include_name": include_name,
-    # WP-5.1 explicit override — preserve in-schema version table per ADR-INF-11.
-    "version_table_schema": "sched",
-}
-
-if context.is_offline_mode():
-    run_migrations_offline(**KW)
-else:
-    run_migrations_online(**KW, alembic_config=config)

package/tools/vds-scripts/scheduler_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 Union
-
-import sqlalchemy as sa
-from alembic import op
-${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, None] = ${repr(branch_labels)}
-depends_on: Union[str, None] = ${repr(depends_on)}
-
-
-def upgrade() -> None:
-    ${upgrades if upgrades else "pass"}
-
-
-def downgrade() -> None:
-    ${downgrades if downgrades else "pass"}

package/tools/vds-scripts/scheduler_orchestrator/alembic/versions/0001_create_sched_schema.py

@@ -1,57 +0,0 @@
-"""Create sched schema
-
-Revision ID: 0001
-Revises:
-Create Date: 2026-04-24 00:00:00.000000 UTC
-
-TSK-1.2: Creates the 'sched' PostgreSQL schema that all scheduler_orchestrator
-tables live in. This is intentionally a bare-schema migration — the 7 domain
-tables are added by TSK-1.3 (revision 0002).
-
-The 'dbos' schema is managed exclusively by DBOS itself and is NEVER touched
-by these migrations (enforced by the include_name filter in env.py).
-
-Alembic's own version tracking table is stored inside the 'sched' schema
-(version_table_schema='sched' in env.py) so all scheduler migration state
-lives in one place.
-"""
-
-from __future__ import annotations
-
-from alembic import op
-
-# revision identifiers
-revision: str = "0001"
-down_revision: str | None = None
-branch_labels: str | None = None
-depends_on: str | None = None
-
-
-def upgrade() -> None:
-    """Create the sched schema."""
-    op.execute("CREATE SCHEMA IF NOT EXISTS sched")
-
-
-def downgrade() -> None:
-    """Intentional no-op for schema teardown; we deliberately do NOT
-    DROP SCHEMA sched CASCADE (ADR-INF-11 §version_table_schema Policy).
-
-    Rationale: alembic_version lives in the sched schema. Any attempt to
-    drop sched.alembic_version inside this function would cause alembic to
-    fail when it subsequently tries to delete the version row from that same
-    table (alembic updates the version table AFTER calling downgrade()).
-    Using DROP SCHEMA CASCADE would wipe sched.alembic_version mid-tx and
-    abort the downgrade with an inconsistent state.
-
-    By the time alembic reaches this 0001 downgrade, revisions >=0002 have
-    already dropped all domain tables via their own downgrade() methods.
-    After alembic completes downgrade base, the sched schema holds only the
-    now-empty alembic_version table.
-
-    Operators wanting full schema teardown MUST run this OUTSIDE alembic,
-    AFTER alembic downgrade base completes:
-        DROP SCHEMA sched CASCADE;
-    Then re-init with: alembic upgrade head.
-    """
-    # Nothing to drop here — alembic manages sched.alembic_version itself.
-    # The sched schema itself is not dropped; see docstring above.

package/tools/vds-scripts/scheduler_orchestrator/alembic/versions/20260424_04f7169497f6_create_domain_tables.py

@@ -1,166 +0,0 @@
-"""create_domain_tables
-
-Revision ID: 04f7169497f6
-Revises: 0001
-Create Date: 2026-04-24 09:43:20.514865+00:00
-
-"""
-
-from __future__ import annotations
-
-import sqlalchemy as sa
-from sqlalchemy.dialects import postgresql
-
-from alembic import op
-
-# revision identifiers, used by Alembic.
-revision: str = "04f7169497f6"
-down_revision: str | None = "0001"
-branch_labels: str | None = None
-depends_on: str | None = None
-
-
-def upgrade() -> None:
-    # ### commands auto generated by Alembic - please adjust! ###
-    op.create_table(
-        "chain_definitions",
-        sa.Column("chain_name", sa.Text(), nullable=False),
-        sa.Column("trigger_kind", sa.Text(), nullable=False),
-        sa.Column("trigger_source", sa.Text(), nullable=False),
-        sa.Column("target_workflow_fqn", sa.Text(), nullable=False),
-        sa.Column("input_mapping_jsonpath", sa.Text(), nullable=True),
-        sa.Column("filter_expression", sa.Text(), nullable=True),
-        sa.Column("queue_name", sa.Text(), nullable=True),
-        sa.Column("enabled", sa.Boolean(), server_default=sa.text("true"), nullable=False),
-        sa.PrimaryKeyConstraint("chain_name"),
-        schema="sched",
-    )
-    op.create_table(
-        "chain_fire_log",
-        sa.Column("chain_name", sa.Text(), nullable=False),
-        sa.Column("source_key", sa.Text(), nullable=False),
-        sa.Column("target_workflow_id", sa.UUID(as_uuid=False), nullable=False),
-        sa.Column("fired_at", sa.TIMESTAMP(timezone=True), server_default=sa.text("now()"), nullable=False),
-        sa.PrimaryKeyConstraint("chain_name", "source_key"),
-        schema="sched",
-    )
-    op.create_index(
-        "ix_chain_fire_log_fired_at_desc",
-        "chain_fire_log",
-        [sa.literal_column("fired_at DESC")],
-        unique=False,
-        schema="sched",
-    )
-    op.create_table(
-        "dispatch_ack_log",
-        sa.Column("subscription_id", sa.UUID(as_uuid=False), nullable=False),
-        sa.Column("event_id", sa.UUID(as_uuid=False), nullable=False),
-        sa.Column("acked_at", sa.TIMESTAMP(timezone=True), server_default=sa.text("now()"), nullable=False),
-        sa.PrimaryKeyConstraint("subscription_id", "event_id"),
-        schema="sched",
-    )
-    op.create_index(
-        "ix_dispatch_ack_log_sub_event_desc",
-        "dispatch_ack_log",
-        ["subscription_id", sa.literal_column("event_id DESC")],
-        unique=False,
-        schema="sched",
-    )
-    op.create_table(
-        "events_outbox",
-        sa.Column("event_id", sa.UUID(as_uuid=False), nullable=False),
-        sa.Column("topic", sa.Text(), nullable=False),
-        sa.Column("payload", postgresql.JSONB(astext_type=sa.Text()), nullable=False),
-        sa.Column("trace_id", sa.Text(), nullable=True),
-        sa.Column("committed_at", sa.TIMESTAMP(timezone=True), server_default=sa.text("now()"), nullable=False),
-        sa.Column("published_at", sa.TIMESTAMP(timezone=True), nullable=True),
-        sa.PrimaryKeyConstraint("event_id"),
-        schema="sched",
-    )
-    op.create_index(
-        "ix_events_outbox_committed_at_unpublished",
-        "events_outbox",
-        [sa.literal_column("committed_at DESC")],
-        unique=False,
-        schema="sched",
-        postgresql_where=sa.text("published_at IS NULL"),
-    )
-    op.create_index(
-        "ix_events_outbox_topic_committed_at",
-        "events_outbox",
-        ["topic", sa.literal_column("committed_at DESC")],
-        unique=False,
-        schema="sched",
-    )
-    op.create_table(
-        "schedules",
-        sa.Column("schedule_name", sa.Text(), nullable=False),
-        sa.Column("owner_orchestrator", sa.Text(), nullable=False),
-        sa.Column("workflow_fqn", sa.Text(), nullable=False),
-        sa.Column("cron_expr", sa.Text(), nullable=True),
-        sa.Column("interval_seconds", sa.Integer(), nullable=True),
-        sa.Column("run_at", sa.TIMESTAMP(timezone=True), nullable=True),
-        sa.Column("queue_name", sa.Text(), nullable=True),
-        sa.Column("context_json", postgresql.JSONB(astext_type=sa.Text()), nullable=True),
-        sa.Column("automatic_backfill", sa.Boolean(), server_default=sa.text("false"), nullable=False),
-        sa.Column("paused", sa.Boolean(), server_default=sa.text("false"), nullable=False),
-        sa.Column("created_at", sa.TIMESTAMP(timezone=True), server_default=sa.text("now()"), nullable=False),
-        sa.Column("updated_at", sa.TIMESTAMP(timezone=True), server_default=sa.text("now()"), nullable=False),
-        sa.Column("last_run_at", sa.TIMESTAMP(timezone=True), nullable=True),
-        sa.CheckConstraint("num_nonnulls(cron_expr, interval_seconds, run_at) = 1", name="ck_schedules_trigger_kind"),
-        sa.PrimaryKeyConstraint("schedule_name"),
-        schema="sched",
-    )
-    op.create_table(
-        "subscriptions",
-        sa.Column("subscription_id", sa.UUID(as_uuid=False), nullable=False),
-        sa.Column("consumer_name", sa.Text(), nullable=False),
-        sa.Column("topic_pattern", sa.Text(), nullable=False),
-        sa.Column("handler_fqn", sa.Text(), nullable=False),
-        sa.Column("filter_jsonpath", sa.Text(), nullable=True),
-        sa.Column("last_acked_event_id", sa.UUID(as_uuid=False), nullable=True),
-        sa.Column("paused", sa.Boolean(), server_default=sa.text("false"), nullable=False),
-        sa.PrimaryKeyConstraint("subscription_id"),
-        schema="sched",
-    )
-    op.create_table(
-        "workflow_registry",
-        sa.Column("alias", sa.Text(), nullable=False),
-        sa.Column("workflow_fqn", sa.Text(), nullable=False),
-        sa.Column("owner_orchestrator", sa.Text(), nullable=False),
-        sa.Column("version", sa.Text(), nullable=False),
-        sa.Column("registered_at", sa.TIMESTAMP(timezone=True), server_default=sa.text("now()"), nullable=False),
-        sa.Column("last_resolved_at", sa.TIMESTAMP(timezone=True), nullable=True),
-        sa.PrimaryKeyConstraint("alias"),
-        schema="sched",
-    )
-    op.create_index(
-        "ix_workflow_registry_orchestrator_fqn",
-        "workflow_registry",
-        ["owner_orchestrator", "workflow_fqn"],
-        unique=False,
-        schema="sched",
-    )
-    # ### end Alembic commands ###
-
-
-def downgrade() -> None:
-    # ### commands auto generated by Alembic - please adjust! ###
-    op.drop_index("ix_workflow_registry_orchestrator_fqn", table_name="workflow_registry", schema="sched")
-    op.drop_table("workflow_registry", schema="sched")
-    op.drop_table("subscriptions", schema="sched")
-    op.drop_table("schedules", schema="sched")
-    op.drop_index("ix_events_outbox_topic_committed_at", table_name="events_outbox", schema="sched")
-    op.drop_index(
-        "ix_events_outbox_committed_at_unpublished",
-        table_name="events_outbox",
-        schema="sched",
-        postgresql_where=sa.text("published_at IS NULL"),
-    )
-    op.drop_table("events_outbox", schema="sched")
-    op.drop_index("ix_dispatch_ack_log_sub_event_desc", table_name="dispatch_ack_log", schema="sched")
-    op.drop_table("dispatch_ack_log", schema="sched")
-    op.drop_index("ix_chain_fire_log_fired_at_desc", table_name="chain_fire_log", schema="sched")
-    op.drop_table("chain_fire_log", schema="sched")
-    op.drop_table("chain_definitions", schema="sched")
-    # ### end Alembic commands ###