Prelive inventory proof reads runtime safety, stock snapshots, reservations, movement ledger, lineage, and audit surfaces already mounted on this admin page.

Module OFF and runtime guard evidence stays tied to admin-controls and the exact textile registry; no duplicate module route is introduced.

Refund, reservation release, escrow release, wallet, payout, receipt, and audit evidence is represented as guard proof without adding a payout executor.

Verifier locks frontend pages, admin pages, route handlers, and backend registered verbs before and after this admin UI proof patch.

Preview/status GET readback; no apply call is made by this proof.

Operational quantity source is trade_inventory_snapshots.qty_after.

Reservation readiness reads trade_inventory_reservations.

Movement display reads erp_inventory_movement_ledger only.

Existing routes reused; no DB schema or payment path is changed.

Listing stock remains a display mirror; no auto-sync mutation is invoked.

Snapshots, reservations, and movement rows are read back from existing ERP inventory surfaces.

The existing preview/status routes prove readiness without calling apply.

No DB schema, route, payment, logistics, or duplicate stock truth is added.

The fixed listing to audit chain stays one-directional.

Seller labels come from existing listing and reservation readbacks only.

ERP stock remains trade_inventory_snapshots.qty_after with listing stock as display mirror.

Order and reservation visibility uses orders/mine and reservations GET readbacks.

Buyer visibility is exposed through existing buyer order and marketplace readbacks.

Warehouse tags and movement traces stay on ERP reservation and movement readbacks.

Admin audit visibility uses existing ERP inventory execution and audit timeline surfaces.

Reservation guard status is surfaced as readonly ERP execution visibility; release and recompute controls stay on existing endpoints.

Release enforcement remains anchored to the canonical reservation-expiry endpoint already used by this admin page.

Refund policy status is displayed as operational guardrail proof only; no refund route or backend policy is edited.

Buyer visibility rollout stays outside buyer pages and shared marketplace components.

Seller attachment rollout remains an admin-observed status signal with no seller page or attachment runtime change.

Canonical RFQ migration status is compatibility-only readiness metadata; no RFQ backend alias is removed or route count reduced.

Static widget documents the existing runtime-safety readback surface without adding a fetch.

Existing release lane remains the only shown reservation expiry control.

Buyer and seller rollout visibility is admin-only and isolated to observability pages.

RFQ canonical route set is documented only; yarn aliases stay compatibility-only and preserved for buyer/seller safety.

Runtime guard proof is read from the existing admin runtime-safety payload and does not mutate stock, order, escrow, refund, wallet, or payout state. Route: /api/trade-core/erp/inventory/runtime-safety

Escrow release stays behind the existing release-pending/final-release policy gates and admin process-releases route. Route: /api/trade-core/process-releases

Refund guard proof remains backend-owned through the existing refund policy gate; this page adds no refund mutation. Route: /api/trade-core/order/refund

Reservation release/expiry proof remains admin-only, preview-first, and backed by canonical reservation tables. Route: /api/trade-core/erp/inventory/reservation-expiry

Module OFF proof reads the existing DB-backed admin controls and exact 22-module registry without creating route aliases. Route: /api/trade-core/erp/admin-controls

Seller linkage is displayed from backend proof only; the UI does not infer seller ownership. Route: backend/routes/tradeCore.js

CODEX120C expands proof readback on existing backend and admin pages only. Route: /api/trade-core/erp/inventory/runtime-safety

No admin key has been verified in this browser session. Route: /api/trade-core/erp/inventory/runtime-safety

0 reservation rows displayed from /api/trade-core/reservations; guard verification is read-only.

Refund policy enforcement remains backend-owned; this card adds no refund route or mutation.

/api/trade-core/erp/inventory/reservation-expiry remains the only release execution endpoint shown on this admin page.

Seller identity is passed through canonical filters and existing API payloads; the UI does not infer seller ownership.

yarn uses rejectIfModuleDisabled with admin-controls readback.

Exact textile module registry remains the module-control source for this admin execution surface.