Repository navigation
Phones: instant open for bots, the uberbot, rooms and threads; the person's taps ahead of streaming - #79
Merged
Conversation
…ts page gives up after 3 s; rows without nav open as before Synthesis of ios-snappy inc 1 (B as base): - a background frame with more queued behind it stays quiet until a second since the last screen (as before the 250 ms window), so a cold join or a catch-up builds no more screens than it did - iOS decodes an answer's screen only when it is drawn - iOS awaitedNav / Android opening expire after 3 s: a page that never comes no longer holds the stack (iOS) or every action (Android) - iOS open() with no nav (an older bridge's row) acts as before (from A) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tapping Bub (the uberbot) took about a second while it streamed: the page moved only once Bend answered, the engine thread was one FIFO queue saturated by streaming frames (~100 ms each), and a tap's own screen was dropped whenever frames waited behind it.
What changes (iOS and Android, same behaviour)
nav: the selection its page will have (bots, uberbot card, rooms, remote bots, Status-plane rows;MBots.nav*,Hubs.nav*,Planerows; laws in# ios-snappy: nav,test/mnav_test.bendwith one and two hubs).awaitedNav; expires after 3 s so notifications still move the stack). Thread rows on Android now open at once too.Backplane.flush), so the last state shows within 250 ms. A burst (cold join, catching up) still builds one a second, as before.Backplane tap <nav> first N ms full N ms), ACTS@open=<name>and@times.Measured in an iOS 26.5 simulator with
JSC_useJIT=0, on a sandbox hub with a copy of the real log (push registrations and hooks stripped), with Bub streaming (stand-in agent):Checks:
scripts/check.sh(with PROOF),mnav,mbots,hubs,mplane,plane,onboardtests, the engine/flush harnesses,build-mobile.sh(bridge + release APK), and the Mac Debug build all pass. Synthesis of two independent implementations (Codex GPT-6.1-Sol as base; notes in bp-coord/ios-snappy/synthesis-1.md).🤖 Generated with Claude Code