Installed extensions surface in the shell - #250
Merged
Conversation
The backend already gives every installed extension a full read-side — boards, subject timelines, transcripts, gate answering — but the shell derived its nav, routes, and landing only from the import-time bundle registry, so an extension installed against the published image was invisible to the operator. GET /api/extensions now serves the installed roster (name, icon, description, builtin, subject types, has-frontend). The shell registers every roster entry into the same UI registry the bundled extensions use: a backend-only extension gets generic pages — its subject boards stacked on a home page, and a subject page with summary facts, the run timeline, the newest run's transcript, and the gate controls — while an extension that ships its own dist/ gets an external home at /app/<name>. Bundled registration wins per extension; roster extras follow A→Z. The extension dropdown and the events filter read the roster instead of the settings projection, which is filtered to knob-carrying extensions and was the wrong wire for nav. The in-app review, cancel, and retry controls move from ship's work-item page to shared components so the generic subject page answers gates with the same UI.
czpython
force-pushed
the
installed-extensions-surface
branch
from
August 14, 2026 14:34
c3f6ae8 to
d7b4b08
Compare
czpython
enabled auto-merge (squash)
August 14, 2026 14:35
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.
What
An extension installed against the published image is now visible and usable from the dashboard without shipping any frontend.
GET /api/extensions— the installed roster: name, icon, description, builtin, subject types, has-frontend. The extension dropdown and the events filter read it (the settings projection is filtered to knob-carrying extensions and was the wrong wire for nav).dist/(already served at/app/<name>) gets its app-switcher entry linked there; reaching it is a document load, not an SPA navigation.Why
The backend treats every installed extension uniformly — boards, timelines, transcripts, and gate answering are all platform wire — but the shell derived nav, routes, and landing only from the import-time bundle registry.
uv pip install <app>registered everything except a way for the operator to find it.Acceptance
Stock deploy,
uv pip installa druks-apps extension, restart: the dropdown lists it, its boards render, a parked run's gate is answerable from its subject page. No typed URL, no SPA rebuild.