feat(ui): read-only model registry view in Settings (RIG-3124) - #1332
Open
rigel-mintaka wants to merge 2 commits into
Open
rigel-mintaka wants to merge 2 commits into
rigel-mintaka wants to merge 2 commits into
Conversation
Adds a read-only display of the fleet model registry to the Settings screen. The data comes from `CompassService.GetModelRegistry`, which is open to any authenticated account. This is the first production caller of the `createConnectQuery` glue. - **Store:** `createAppStore` takes an optional `transport`. When set, it runs a `GetModelRegistry` query and exposes `modelRegistry()` as `offline | pending | error | ready`. Rows are sorted by stable name, and each candidate chain keeps its order, since that order is the fallback order. With no transport the store is offline and creates no query. - **Boot:** `index.tsx` passes `clients.transport` to the store. - **View:** a new Model registry section under the tracker editor shows the version, each stable name with its display name, and the ordered `provider/modelId` chain. It also shows loading, error, and empty states. The section is hidden on an offline store, so the fixture boot and the committed `settings.png` baseline do not change. - **Client:** `@compass/client` now re-exports `GetModelRegistryResponse` and its schema. Out of scope, as the record says: a write surface (edits go through the operator `PutModelRegistry` RPC) and the effective backend per caller. Record: `docs/designs/platform/compass-stable-name-routing/design.md` §P4. Spec-impact: none. Refs RIG-3124 Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
|
Compass engineering docs preview: https://compass-obs-rig-3124-model-r.compass-eng-docs.pages.dev Deployed from |
The registry state checked the query error before its cached data. A background refetch failure (focus or reconnect) then replaced a loaded registry with the error state. Data now wins over error, and the state is a memo, so rows are mapped once per fetch instead of on every read. Adds a regression test: load the registry, fail the refetch, and the rows remain. Refs RIG-3124 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
marked this pull request as ready for review
September 25, 2026 18:26
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
1 participant
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.
Adds a read-only display of the fleet model registry to the Settings screen. The data comes from
CompassService.GetModelRegistry, which is open to any authenticated account. This is the first production caller of thecreateConnectQueryglue.createAppStoretakes an optionaltransport. When set, it runs aGetModelRegistryquery and exposesmodelRegistry()asoffline | pending | error | ready. Rows are sorted by stable name, and each candidate chain keeps its order, since that order is the fallback order. With no transport the store is offline and creates no query.index.tsxpassesclients.transportto the store.provider/modelIdchain. It also shows loading, error, and empty states. The section is hidden on an offline store, so the fixture boot and the committedsettings.pngbaseline do not change.@compass/clientnow re-exportsGetModelRegistryResponseand its schema.Out of scope, as the record says: a write surface (edits go through the operator
PutModelRegistryRPC) and the effective backend per caller.Record:
docs/designs/platform/compass-stable-name-routing/design.md§P4.Spec-impact: none. Refs RIG-3124
Co-authored-by: Matt Wilkinson matt@rigel.build