docs(zone-sdk): update Zone SDK guides for logos-blockchain 0.3.2

[kashepavadan]

What this changes

Updates the three Zone SDK guides under docs/blockchain/zone-sdk/ for logos-blockchain 0.3.2, based on the upstream zone-sdk/BRIDGING.md and DECENTRALIZED_SEQUENCING.md at the 0.3.2 tag.

• Inscribe data on-chain: adds the now-mandatory FundingConfig and a run step for finding the funding key; publish is async; drops MempoolPending; handles the new FinalizedOp variants. Removes references to logos-blockchain-node inscribe and the TUI Zone on master, both removed in 0.3.0. Fixes the clone steps, which changed into deployment/tui-zone before checking out the branch that contains it.
• Bridge assets: channel notes replace the channel balance, withdrawals bundle a ChannelTransfer with the ChannelWithdraw, WithdrawInputs selects the notes, transfer_threshold replaces withdraw_threshold, and multi-sig withdrawals use prepare_atomic_withdraw / submit_atomic_bundle. Adds deposit pinning.
• Round-robin rotation: ChannelUpdate is now an enum read via orphaned(); channel_config takes VerifiedChannelKeys and is async; multi-admin config uses prepare_channel_config / submit_channel_config; reference policies moved to tests/src/cucumber/steps/zone/operations/policies.rs. Indents a callout that split a numbered list.

Merge order

The inscription tutorial depends on the updated skeleton in logos-blockchain/logos-blockchain#3812. Merge them together.

This also overlaps with the 0.2.4-era fixes to the same pages on dogfood/blockchain-reapply; resolve any conflict in favour of this branch.

Checks

• npm run build passes.
• vale --minAlertLevel=error reports no errors on the changed files.

🤖 Generated with Claude Code

[kashepavadan]

I followed the three changed Zone SDK pages end to end at e693c71ea7149dea1c91bd7678465f6e62cfffb2 on Ubuntu 24.04.

Inscribe data on-chain: I ran a fresh testnet node with logosctl 0.3.2 and blockchain_module 0.3.2 until it was Online, then mined until the PoWClaim key was funded. Next I cloned tui-zone-tutorial (with logos-blockchain#3812 merged) and filled in the skeleton with the code from the page, exactly as written. It builds with no warnings and matches tui-zone-solution apart from whitespace. The pow_status / auto_claim.targets and balance commands in Step 5 return what the page describes, including the 404 before funds arrive. cargo run --bin tui-sequencer -- --funding-pk … printed Ready., both messages were funded and published, and the channel was created on-chain within a few minutes. The one gap is the long wait before messages move to Finalized (inline comment).

Bridging and round-robin rotation: these are reference snippets rather than a runnable flow, so I compiled every snippet on both pages against the 0.3.2 tag, with stub inputs for the undefined variables. All of them compile except the VerifiedChannelKeys::from(...)? one (inline comment). I also checked the quoted defaults against the source: the 12% priority fee, the 30 s resubmit_interval, the 30-slot stale_refund_slots, and the policy file paths. All are correct. The bridging page still carries the 0.2.4 "withdrawals cannot be completed" warning, which is no longer true (inline comment).