fix(preprocess): enforce local vector startup chain
This commit is contained in:
@@ -33,3 +33,17 @@ The cleanup boundary now begins immediately after snapshot materialization. Resu
|
||||
validation and `JobSpec` construction are guarded by the same release routine as `run_job`, so
|
||||
corrupt/mismatched resume state or constructor failure clears the pipeline holder, removes the
|
||||
private directory, and restores the snapshot registry to its prior state before propagating.
|
||||
|
||||
## Shipped preprocessing startup contract
|
||||
|
||||
Local-vector preprocessing now uses a dedicated Compose override. Both one-shot jobs depend on a
|
||||
successfully completed `vector-migrate`, whose transitive chain waits for database health and role
|
||||
reconciliation. The generic preprocessing overlay remains independently renderable and contains no
|
||||
local-vector services or password secrets. README commands include the local override and build the
|
||||
job image before running.
|
||||
|
||||
The real clean-project smoke no longer injects dependencies or manually starts, reconciles, or
|
||||
migrates PostgreSQL. Its first shipped `compose run preprocess-evidence` demonstrably creates the
|
||||
database, waits for health, runs reconciliation and migration, then runs the Evidence job. Unchanged
|
||||
rerun, changed-source publish, DWH preprocessing, ACTIVE verification, and injected-failure cleanup
|
||||
all pass through the same shipped dependency path.
|
||||
|
||||
Reference in New Issue
Block a user