Repository navigation
feat(ui): find a flow in the model browser and see its steps - #448
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- model browser: a Flow badge on a flow, and a Models / Flows filter
- model page: a Steps section for a flow, with its steps drawn as a graph and
listed with each step's piece, owner, settings and links in words
- thread picker: a flow this user cannot run is greyed out with the reason
- adapter: GET /flows/{id}/availability says, for the caller, whether each
step's piece can be run. A piece the caller cannot see is reported only as
missing
The flow queries are hand-written and separate from the page's own, so a
deployment where they fail loses the badge, not the page.
wmobley
force-pushed
the
feat/ui-find-a-flow
branch
from
November 20, 2026 02:53
d6fc04a to
019ba8d
Compare
This branch was successfully deployed
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.
C2 of the plan in #441.
GET /flows/{id}/availabilitysays, for the caller, whether each step's piece can be run. A piece the caller cannot see is reported only as missing.The flow queries are hand-written and separate from the page's own, so a deployment where they fail loses the badge, not the page. The plan had the availability route on the Ensemble Manager; the web app calls the adapter directly, as it already does for other things.
Tests: web app 1344 passing, type check clean; adapter 806 passing with the four failures that predate this work.