CONTRACTS: Sorphera Passport deployment integration and release rehearsal

Continue https://github.com/identity-md-launches/launch-961-build-sorphera-smart-contracts

Start from latest main after PR #9; preserve newer work.

ONE Contracts task: finish deployment wiring, integration verification and release artifacts for the existing Passport. No new features, website work, live signing/funding/broadcast, mainnet deployment or production sales. Local test transactions are allowed. Do not retarget parked launch 961.

The previous pass reports 103 offline tests but no fresh integration run. Entry processing, ABI layouts, refund divisors and entitlements changed, so "buy is unchanged" cannot justify skipping integration. Deployers/manifests still omit Passport.

Read PASSPORT-HANDOFF, TESTING, DEPLOYMENT, CANARY, KEEPER and current source. Preserve reward rules, 10% paid-sale fees, custody protections, strict cutoffs, separate NFT tie VRF and immutable accepted requests.

1. DEPLOYMENT WIRING

Update actual deployers/decoders: Rehearse.s.sol, SepoliaCanary preparation, canary/release CLIs and manifest consumers, not just wrappers.

Deploy Router -> VaultFactory -> Sorphera -> SorpheraPassport(lottery, qualifyingPriceWei). Complete both owner bindings: factory.setLottery(lottery) and lottery.setPassport(passport).

Qualifying price is an explicit input; 5000000000000000 wei (0.005 ETH) is only a local fixture. Production price/owner remain unapproved inputs. Validate the price under lottery rules and against both intended qualifying games. Other-priced rounds remain ineligible; never reprice earned rewards.

Add fail-closed preflight/rehearsal checks for:

• Correct chain, owner and dependency/configuration bindings.
• Expected Passport code, passport.lottery() == lottery, lottery.passport() == passport and expected qualifyingPrice.
• Missing/wrong addresses, incompatible code, wrong price and repeated binding.
• Missing/misbound Passport blocks release readiness even though ordinary buy can work without it.
• Sales remain disabled during release setup and at rehearsal completion. Lifecycle tests may enable only isolated local fixtures.

Prefer script/preflight fixes; change lottery code only for a reproduced need. Preserve launch guards and the absence of privileged reward grants.

2. MANIFESTS AND RELEASE ARTIFACTS

Use the permitted release workflow to include Passport, constructor inputs and post-deployment actions in manifests/configuration.

Preserve protected launch.json and historical records unless the platform permits edits. If blocked, provide a concrete candidate patch/template and exact release commands for IMD. Do not bypass protection, remove hashes or claim unapplied changes are complete. Keep mainnet drafts separate from Sepolia rehearsals.

Regenerate canonical ABIs, size reports and permitted release metadata from final source. Include Passport in address discovery, exports and required configuration. Check keeper/canary decoding of appended Round fields, Ticket.reward, Cancelled's paid count and reward issuance.

Validate runtime hashes against locally deployed code, including constructor immutables/addresses. Label fixture values local; leave unknown production values unset. Never fake hashes. List website ABI/config updates for the later Website task.

Enforce production size limits with pinned compiler/settings. Sorphera was 24,366 bytes against 24,576, leaving 210 bytes. Report final sizes and fail on oversize. Do not raise limits or weaken safeguards; put extra logic outside the lottery where practical.

3. COMPLETE LIFECYCLE VERIFICATION

Run fresh offline, tooling and relevant fork/integration suites against this candidate and deployment path. Historical passes are not current evidence.

Extend integration tests to deploy/bind Passport and cover:

• Direct buy and paid entry through Passport; correct player ownership and exact ETH forwarding.
• 12 qualifying paid entries -> own round Won/Rolled -> finalization -> reward, with remainders across games/rounds.
• Free-only/mixed entries; total/paid/reward counts, fees and FWA acquisition budget.
• Paid/reward ETH winners, a reward winner in the separate NFT tie-break and vault claims.
• Cancellation: paid-only refunds/FWA tokens/exceptional NFT recovery rights; reward restoration once.
• Zero-paid cancelled cohorts, same-game carry-forward and late recoveries. Prove which vaults/groups can receive late ETH/tokens/NFTs, including prior-group assets; an empty new-vault test alone is insufficient.
• Reverts, cutoff/pause, retries, duplicate processing/restoration, wallet isolation and keeper continuation.

Exercise real FWA pool/rewards/helper paths on a pinned fork without replacing deployed dependency code. Verify chain, block hash and bindings. Label test funding, impersonation and simulated callbacks; a fork pass is not live VRF proof. Check custody, token delivery, liabilities and claim balances, not only successful transactions.

Keep tests bounded. Add focused regressions for reproduced defects; preserve existing assertions/guards. Record gas/batch limits and deployed sizes.

4. NETWORK AND LIVE-CANARY BOUNDARY

Check permitted RPC/network access early, using documented endpoints or configured inputs. Never bypass controls or expose API keys.

If fork access is blocked, finish local implementation, deployment rehearsal and offline/tooling checks. Supply runnable fork commands, required environment-variable names, the actual connection failure and the runner/RPC capability needed. Mark those checks BLOCKED/NOT RUN, not passed or unnecessary. Missing RPC access does not require wallet funding.

Update the resumable Sepolia canary for Passport deployment/binding and rewards; rehearse locally only. Do not run it live. Keep actual coordinator fulfillment/proof/billing receipts separate from simulations. A company signer, subscription, test funds and separate live authorization remain later inputs.

Do not address permanent accepted-VRF nonfulfillment with a reroll, replacement seed, discretionary cancellation or winner change. Record that existing issue separately. Never bypass or claim a private IMD gate rerun without its runner.

5. DELIVERABLES AND COMPLETION

Deliver code/tooling fixes, interfaces, permitted manifest edits or concrete protected-change patches, plus concise integration/release instructions in existing docs. Keep these within the Contracts task.

Provide a validation table: command, source revision, toolchain, network/block, result, evidence and blocker. Separate historical results, current offline/fork passes and unperformed live steps. Automated checks are not a professional audit.

Completion checklist: A. Fresh local deployment includes Passport, verifies both bindings/price and ends with sales disabled.

B. Rewards, both games' claims and cancellation/restoration pass the updated integration path. Any external RPC blocker is explicitly recorded as outstanding, not successful comple