name: zones-deploy-debug description: Deploy Tempo Zones, start zone nodes, validate router swap-and-deposit flows, and debug zone sync, portal ingestion, withdrawal, sequencer key, and generated zone artifact issues in this repository. Use when working with just deploy-zone, zone-up, deploy-router, demo-swap-and-deposit, or generated/<name>/zone.json.

Zones Deploy Debug

Use this skill for repo-local zone deployment, smoke tests, and sync debugging.

If the zone already exists, read generated/<name>/zone.json first.
For real smoke tests, prefer release for tempo-zone.
Use the Justfile and docs/ZONES.md as the source of truth for user-facing commands.
Read references/commands.md for concrete command patterns and troubleshooting checks.

Build tempo-zone in release before judging sync speed.
Deploy a fresh zone if you need a clean test surface.
Start the zone node and confirm http://localhost:8546 is answering.
For a direct bridge smoke test, run just max-approve-portal, just send-deposit, just max-approve-outbox, then just send-withdrawal.
Deploy the router for that zone.
Run the same-zone swap-and-deposit demo.
If the demo stalls, compare the L1 block of the relevant tx with the latest l1_block= in the zone log before assuming the router flow is broken.

Fresh dev nodes can look broken because they are still compiling and replaying L1; use release for meaningful validation.
Direct deposit/withdraw validation needs both approvals: just max-approve-portal before depositing and just max-approve-outbox before withdrawing.
The demo's first real wait point is token enablement on L2. If the zone is still replaying older L1 blocks, demo-swap-and-deposit can time out before the TokenEnabled event appears.
The current just demo-swap-and-deposit recipe takes optional overrides positionally, not as amount=... tick=....
If a restarted zone crashes while seeding transferPolicyId for a temporary token, check crates/tempo-zone/src/l1_state/tip403/cache.rs and consider retesting with a fresh zone.