docs/migration-guide.md's "How Soroban contract upgrades work" section and its "General upgrade procedure" walk through calling -- upgrade --admin ... --new_wasm_hash ... followed by -- migrate --admin .... docs/mainnet-runbook.md's "Rollback Procedure" (Option A) is built entirely around the same -- upgrade invocation as the "preferred" rollback path. No upgrade or migrate function is defined anywhere in src/ (verified via a full-crate grep for pub fn upgrade/pub fn migrate — zero matches), consistent with the still-open backlog feature requests for "Soroban contract upgrade support". Both runbooks give operators a step-by-step procedure that will fail with a missing-function error at the exact moment they're trying to roll back or upgrade a live mainnet deployment.
docs/migration-guide.md's "How Soroban contract upgrades work" section and its "General upgrade procedure" walk through calling
-- upgrade --admin ... --new_wasm_hash ...followed by-- migrate --admin .... docs/mainnet-runbook.md's "Rollback Procedure" (Option A) is built entirely around the same-- upgradeinvocation as the "preferred" rollback path. Noupgradeormigratefunction is defined anywhere insrc/(verified via a full-crate grep forpub fn upgrade/pub fn migrate— zero matches), consistent with the still-open backlog feature requests for "Soroban contract upgrade support". Both runbooks give operators a step-by-step procedure that will fail with a missing-function error at the exact moment they're trying to roll back or upgrade a live mainnet deployment.