KB-D54E

Clone SQL F — Rollback/Drop (sha256 709ecae4…)

1 min read Revision 1
one-roofnonprod-clonesqlrollbackdrop

-- STEP F — ROLLBACK / DROP / RESET (CLONE) -- sha256: 709ecae44df57846c7fec8b9ead74f43d3544e6dabeee344eb447f63bf02fd72 -- Sections 1-2 rehearsed in BEGIN..ROLLBACK so the clone KEEPS its advanced -- state while proving rollback returns to baseline. -- 1. scanner write rollback (FK order): DELETE candidate_object, candidate_state, -- candidate_scan_run (run_id LIKE 'SCAN-CLONE-TEST-%'), gov_worker_cursor -- (worker_name='clone-test-worker'), governance_ruleset (RS-CLONE-TEST-1). -- 2. ownership seed rollback: DELETE FROM governance_object_ownership -- WHERE created_by='CLONE_TEST_F6_SEED' -> own=0, gap back to 210. -- ASSERT clean baseline reachable (own=0 gap=210 candidates=0). ROLLBACK. -- 3. TEARDOWN (on demand, NOT run here): -- docker exec postgres psql -U workflow_admin -d postgres
-- -c 'DROP DATABASE IF EXISTS directus_gov_test_20260602;' -- RESULT: full reversal proven; clone retained (seed=30 gap=0 cand_obj=35 cand_state=5 runs=2) (PASS).

Back to Knowledge Hub knowledge/dev/reports/architecture/one-roof-nonprod-clone-full-coverage-pipeline-2026-06-02/sql/F_rollback_drop_clone.sql