06 — Rollback Readiness

Staged artifact

sql/f4_seam_rollback.sql — written before the commit (Hard Gate 0 item 14). Restores both seam views to inert WHERE false and clears the comments.

Why reversal is safe and total

• Views project no stored rows → nothing to lose; reversal is byte-for-byte the pre-F-4 definition.
• One CREATE OR REPLACE VIEW … WHERE false per seam is atomic and instantaneous.
• Inert DDL identical to the canonical form in one-roof-phase1-test-mode-deferred-substrate-completion-2026-06-02/sql/sb2_views_ddl.sql, which was the live state at F-4 entry.

How to reverse (one command)

ssh contabo 'docker exec -i postgres psql -U workflow_admin -d directus -v ON_ERROR_STOP=1' < .../sql/f4_seam_rollback.sql

Expected: seamA_inert | 0, seamB_inert | 0.

Dependency note

Nothing reads these seams in an active path yet (scanner OFF, owners empty, no worker). Reversal has no downstream effect — coverage output returns to the pre-F-4 fully-inert state. No data/events/issues affected.

Rollback readiness verdict: PASS — staged, lossless, single-command, dependency-free.