IU Core Runtime Activation E2E — 03 H3 reconcile

What H3 was

The prior macro's gate-OPEN probe found production fn_iu_emit_event carried hardcoded event_stream='workflow' and payload_classification='safe', both rejected by event_outbox. The repo's 005 was patched (registry-sourced event_stream/delivery_lane, payload_classification='safe_metadata') but production still ran the pre-fix body.

event_outbox constraints (confirm H3 was real)

• event_outbox_event_stream_check: allows comment, review, update, birth, task, alert, health — not workflow.
• event_outbox_payload_classification_check: allows safe_metadata, restricted — not safe.
• trg_event_outbox_type_validate → fn_event_type_validate: rejects an unknown/inactive (event_domain,event_type) and requires the row's event_stream/delivery_lane to match event_type_registry exactly.

Reconcile action

Re-ran the fully idempotent migration:

docker exec -i 22540b78de8f psql -U directus -d directus -v ON_ERROR_STOP=1 \
  -f sql/iu-core/005_trigger_contracts_and_guards.sql

Output: BEGIN · 7×CREATE FUNCTION · 1×CREATE VIEW · COMMIT.

Verification (V5)

fn_iu_emit_event(text,text,uuid,text,jsonb) body md5:

• before: cd7d1fc4f0b302617a7bb6fc0458a5ed
• after: 7dd8c74a97205c4318b7d9fed8eca62c

Drift flags after re-run: uses_registry_stream=true, no_hardcoded_workflow=true, uses_safe_metadata=true — H3 fix live on production. End-to-end emit proven later in doc 06 (SECTION 2).