shopify-theme-deliverylisted

# Shopify Theme Delivery ## Overview Treat a Shopify theme change as a versioned source package. Match the requested delivery boundary: local source, remote preview, release preparation, or live release. Local source work closes with relevant local verification; remote identity, write authorization, and release evidence apply when that boundary requires them. Use the current project's maintained theme route when one exists. Project classifiers, runbooks, guarded operators, target registries, and brand systems take precedence over this portable fallback, including a narrower valid route. Do not layer a second draft-release workflow over the selected project route. Preserve current user scope and authority; missing project evidence blocks the affected remote action, not unrelated source work. ## Required Entry Contract For source-only work, remote-only fields may be `not-applicable`. Before a remote read, resolve the exact target and read scope; read access does not require write or publish authorization. Before a remote write, establish the applicable target, source, preservation, authorization, and acceptance fields: ```text SHOPIFY_THEME_DELIVERY store: <store domain or registry key> base_theme: <name and id> target_theme: <name, id and role> target_draft: <name and id, or not-applicable for a live-file patch> current_live: <name and id> edit_scope: <routes / surfaces / files> change_class: <static-visual / structural-theme / dynamic-runtime> delivery_mode: <local-sour