feat: console improvements

browser/src/functions/mod.rs

@@ -660,7 +660,8 @@ fn register_screenshot(iii: &Arc<IIIClient>, sessions: &Arc<Sessions>) {
                 })
             }
         })
-        .description(SCREENSHOT_DESC),
+        .description(SCREENSHOT_DESC)
+        .metadata(json!({ "display": true })),
     );
 }
 

browser/ui/page.tsx

@@ -5,22 +5,22 @@
  * asset: ../styles.css ships over `console:style` as browser/styles.css —
  * the console mounts and link-swaps it, styles-before-scripts on boot.
  *
- * `setup(host)` registers two contributions:
+ * `setup(host)` registers three contributions:
  * - src/page/ — the `#/ext/browser` page: the session rail, a screencast-fed
  *   live viewport, and the console/network feeds for the selected session;
  *   drill-in flow (list ⇄ session workspace) when the pane is narrow.
  * - src/function-trigger-message/ — how every `browser::*` call renders in
  *   chat and the traces span tab (per-function terminal cards).
- *
- * No config form is registered: the browser worker's configuration is plain
- * scalar fields, so the console's schema-generated form is sufficient.
+ * - src/configuration/ — the full-width, purpose-built browser settings
+ *   editor used by the Console's worker configuration dialog.
  *
  * Registrations go through `host` so the loader disposes them on hot reload /
  * worker disconnect.
  */
 
 import type { Host } from '@iii-dev/console-ui'
-import { createBrowserRenderer } from './src/function-trigger-message'
+import { BrowserConfigForm } from './src/configuration'
+import { createBrowserRenderer, createBrowserScreenshotRenderer } from './src/function-trigger-message'
 import { BrowserPage } from './src/page'
 
 export default function setup(host: Host) {
@@ -30,5 +30,11 @@ export default function setup(host: Host) {
     render: (props) => <BrowserPage host={host} {...props} />,
   })
 
+  host.configForms.register('browser', BrowserConfigForm, { layout: 'full' })
+
+  // A captured page is a first-class chat artifact. Register its focused
+  // renderer first; the general browser renderer still owns errors/running
+  // states and every other browser::* function.
+  host.functionTriggers.register(createBrowserScreenshotRenderer())
   host.functionTriggers.register(createBrowserRenderer(host))
 }