a plugin's frontend, generated and rebuilt without a restart

the last piece. installing a plugin now brings its UI with it.

a bundler cannot follow import(runtimeString), so which plugins have a frontend
cannot be answered from the database at render time — it has to be written into
source first. Plugins.gen.tsx is that file: concrete imports, generated from
what is installed, gitignored because it describes THIS machine.

App.tsx keeps its core routes and gains one map. the wildcard hands the whole
subtree to the plugin's own router, which react-router nests natively.

serving moved to build/ in production. the html import is bundled once when the
module graph loads and can never change after, which is precisely why a plugin's
frontend needed a restart; Bun.build measures ~900ms for a 25MB bundle, so an
install can just rebuild. development keeps the html import, because that is
what gives HMR and bun --watch restarts on every source change anyway.

verified end to end against a running server, no restart at any point: install
regenerated the module, rebuilt the bundle (chunk hash changed), and the
plugin's own markup was in it; /example and /example/deeper both served; disable
took it back out of both the module and the bundle and 404'd the api; enable put
it back.

three things worth recording because they were found rather than reasoned:

the shell output is named after the ENTRYPOINT — index.gen.html, not index.html
— and naming: { entry: '[name].[ext]' } does not change it because [name] is
'index.gen'. found as a 503 on the first boot after the switch.

App.tsx already destructured a `plugins`, from useServerSettings — the DEAD
plugin system that scans a directory which does not exist and always returns [].
it silently shadowed the import. the new one is `installedPlugins` and says why.

seedAppRegistry takes plugin panels as an argument rather than importing them:
officerdev is a dependency of the shell, so importing upward would invert that.

756 pass, same 10 pre-existing failures.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/apps/officer-web/App.tsx

@@ -5,6 +5,10 @@ import { useAuth } from 'hooks/useAuth';
 import { useServerSettings } from 'state/useServerSettings';
 import { useServerEnvironment } from 'state/useServerEnvironment';
 import { useInitialData } from '@/state/useInitialData';
+// `installedPlugins`, not `plugins`: App.tsx already destructures a `plugins` from useServerSettings(),
+// which is the DEAD plugin system — /server-settings/plugins scans src/workspaces/plugins/, a directory
+// that does not exist, so it is always []. Different thing entirely; see docs/offscale-plugin.md.
+import { plugins as installedPlugins } from './Plugins.gen';
 
 export function App() {
   const { isLoading, isAuthenticated } = useAuth();
@@ -65,6 +69,12 @@ export function App() {
             <Route path="/photos/:section" element={<Dashboard.PhotosScreen />} />
             <Route path="/app-store" element={<Dashboard.AppStoreScreen />} />
             <Route path="/plugins" element={<Dashboard.PluginsScreen />} />
+            {/* Installed plugins. Core routes above stay hand-written; everything below is generated from
+                what is installed, because a bundler cannot follow a runtime import specifier. The wildcard
+                hands the whole subtree to the plugin's own router, which react-router nests natively. */}
+            {installedPlugins.map((plugin) => (
+              <Route key={plugin.appName} path={`${plugin.route}/*`} element={<plugin.Router />} />
+            ))}
             <Route path="/jellyfin" element={<Dashboard.JellyfinScreen />} />
             <Route path="/jellyfin/:section" element={<Dashboard.JellyfinScreen />} />
             <Route path="/transmission" element={<Dashboard.TransmissionScreen />} />