[ark] Multi segment journeys#8138
Merged
paullewis merged 2 commits intobreadboard-ai:mainfrom Mar 11, 2026
Merged
Conversation
📊 Coverage Report
|
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.
What
Fixes multi-step journey bugs and adds missing lifecycle states: themed processing indicator, step navigation between segments, a completion view for finished journeys, and graceful error handling with retry for Gemini 503s.
Why
Journeys were broken in several ways: steps didn't advance visually, the step counter went past total ("4 of 3"), the processing spinner was invisible, the last step's emit locked users out, and API errors silently killed the journey.
Changes
Backend (
journey_router.py,world_model.py,main.py)error_messagefield toJourneywith human-friendly 503/429 messagesmin(current_step_index, len(steps))retry_journey()— resets a failed journey to planning and re-triggers generationPOST /journeys/{id}/retryendpointon_progresscallback into_call_agentfor real-time agent progress.jsx/.cssonlyFrontend (
ark-app.ts,journey-store.ts,backend.ts)#viewManagerwhen viewport DOM is removed, fixing step 1→2 transition--cg-*tokens, theme CSS injected into shadow DOM via:root→:hostremapsource: "journey"toViewBundle, inspector skips reuse check for journeysTypes (
types.ts)source?: "run" | "journey"toViewBundleTesting