AstralBeam #168: limit-aware frontend previews

Previews of each PR head. Exposure data (limits, queue, holds) is simulated from the API contract fixtures; a banner on every page says so. Other data is a snapshot of the public testnet API. Nothing here is deployed.

PreviewPRWhatHead SHABuiltScenarios
pr-44#44#168 simplified, PR B (after Beam): the beam carries the transfer status; Activity shows the same words. Same after-Beam and Activity views as the approved simple/ 8ccd284.c8df0b7f729d2026-10-17committed_not_delivered queued_waiting_delay queued_waiting_capacity queued_behind_head queued_ready held held_recipient_refused paused unconfigured recovery_held executed terminal delivery_unknown unknown Activity list (one simulated transfer per status family) Confirming Queued (waiting) Queued (ready, Complete transfer) On hold (Retry) Paused Unknown Delivered
pr-43#43#168 simplified, PR A (pre-sign): one route check line, limits sheet, terms at the confirm step. Same pre-sign views as the approved simple/ 8ccd284.9caac16c962a2026-10-17Route open (just press Beam) May take longer: queued behind other transfers (time tile "Longer than usual") May take longer: would be held (no room for the token) May take longer: transfers into Casper paused May take longer: destination not accepting deliveries Route paused Amount too large for this route right now (tap the line, then Use 3,000) Over the per-transfer maximum Over your balance No wallets connected Couldn't check route limits, stale Couldn't check route limits, unavailable This route isn't supported yet This route isn't available Fills up at signing (Beam, then Fire, then Use the smaller amount) Changes at signing (Beam, then Fire) Limits and transfer status page
simple#168 SIMPLIFIED, round 2 (Michael's 2026-10-16 feedback F2-F21): master's form plus one route check line; details on tap; limits sheet names the route; notices at the confirm step; after Beam the beam itself carries the progress; Activity shows the same words. Compare with master.9d08f5f1a9dc2026-10-16ok queued held destination_paused destination_refused paused insufficient over max per transfer over balance no wallet stale unavailable unsupported route_unknown Fills up at signing (race: Beam, then Fire) Changes at signing (Beam, then Fire) limits page Activity after: committed_not_delivered after: queued_waiting_delay after: queued_waiting_capacity after: queued_behind_head after: queued_ready after: held after: held_recipient_refused after: paused after: unconfigured after: recovery_held after: executed after: terminal after: delivery_unknown after: unknown transaction 9001 transaction 9002 transaction 9003 transaction 9004 transaction 9005 transaction 9006 transaction 9007
mastermaster today (ff36135), for comparison (dev.astralbeam.io is retired, 410)ff36135c16712026-10-08
docs-168Core user guide preview (HonKit build of branch docs/168-limits-and-transfer-status): Transfer Limits and Status4ecd1bc09a652026-10-16Transfer Limits and Status
pr-40#40Part 3: route limits before signinga051945cb7b72026-10-06ok insufficient queued held destination_refused paused stale unavailable unsupported route_unknown
pr-42#42Part 5: limits checked again right before signing; race-time contract refusal1c551054d17b2026-10-07race (press Beam, then Fire) changed (press Beam, then Fire) ok (Fire passes the check) insufficient queued held paused stale unavailable unsupported
part-6Part 6, the final part (combined preview of all of #168; opens as a PR after Michael has looked): transfer status after commitment. Press Beam, then Fire; the status of the simulated commitment follows.28f2c7d631d32026-10-07committed_not_delivered queued_waiting_delay queued_waiting_capacity queued_behind_head queued_ready held held_recipient_refused paused unconfigured recovery_held executed terminal delivery_unknown unknown