01 — Precheck, live survey, backup, gates

• Macro: IU_CORE_480X_COMPOSER_EVENT_TEXTCODE_ROUNDTRIP_PRODUCTION_READINESS_OPEN_GOAL
• Date: 2026-05-22
• Host: MacBook/dev /Users/nmhuyen/iu-cutter-build/repo/iu-cutter
• Production: VPS vmi3080463, container postgres (postgres:16), DB directus

Repo precheck

• Branch main, HEAD before macro bdf6559 (the 240x KB-report commit) — clean tree (git status empty). Code baseline 9e7fbbf.
• Test baseline re-run: 792 passed.

Live production survey — 240x state verified intact

Metric	Value	240x report	Verdict
information_unit live	158	158	match
iu_structure_operation	57	57	match
iu_piece_collection	1	1	match
iu_piece_membership	3	3	match
iu_metadata_tag	330	330	match
iu_tree_path	158	158	match
event_outbox iu	56	56	match
iu_route_attempt	56	56	match
iu_route_dead_letter open	0	0	match
iu_tree_change_log	1	1	match

DOT baseline scan (runtime/110, read-only): table 14/14, view 12/12, function 34/34, trigger 3/3, config 6/6, event_type 7/7, route 8/8 — 84/84 PASS.

Gate state: routes_master_enabled=true, route_worker_enabled=true, structure_ops_enabled=false, delivery_enabled=false, delivery_live_routes='', composer_enabled=false. IU Gateway mode=enforced, allowlist fn_iu_create,fn_iu_apply_edit_draft,fn_iu_enact,fn_iu_structure_op.

240x AgentData reports verified present — 7 documents under v0.6-iu-core-240x-piece-native-authoring-composer-textcode-autocut-delivery-open-goal/. No repair needed — the 240x state is fully intact.

Backup — EXACT GATE BLOCKER

Gate 3 (a fresh pg_dump -Fc backup with sha verification) could not be satisfied this session: the Incomex VPS MCP surface available is query_pg (read-only SELECT, AST-validated, no writes/DDL), pg_schema, list_docker, read_file, write_file (narrow allowlist) — there is no shell / docker-exec / pg_dump tool. A backup cannot be taken.

Per the mandatory-gate protocol: no production mutation is performed this macro. All 480x feature code is authored, statically + test-proven, and read-only-verified against production, and is handed to GPT/User as a single gated apply runbook. This is a tooling boundary, not a safety failure — no unsafe production state exists.

16 mandatory gates

1. Host correct ✓. 2. Target identity — container postgres, DB directus, host vmi3080463 ✓. 3. Fresh backup ✗ — no pg_dump tool (see above).
2. DOT/no-hardcode/five-layer baseline clean — DOT 84/84 ✓. 5–16: the feature work is bounded, reversible, registry-backed, fail-closed, with a known disable path — but gate 3 alone blocks any durable production mutation, so the durable apply is deferred to GPT/User. All safe repo/authoring/read-only work continued per the gate-failure rule.