World Lab's subtitle promises "Simulate, forecast, and intervene on the current world," and ScreensController already had a fully working forecastWorld() method plus a "world:forecast" case in its onAction dispatch table (calling the real worlds.forecast API) since the P6 wave — but no screen ever rendered a button with that action id, so a real user could never trigger it. The button, its handler, and its result were three separately built pieces that were never connected. Add the "Request live forecast" button to World Lab's actions, track a `forecasting` in-flight flag, and surface the live forecast result as a metric so clicking it has a visible effect instead of silently doing nothing. Covered by a new end-to-end test (worldLabForecastTests) that drives the real action id through a live api-client transport and asserts the model updates. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
LawSynth Studio
Studio is the browser orchestration layer for project workspaces, dataset inspection, law discovery, simulation, model structure, uncertainty, regimes, and provenance. It composes the typed API client and state store; numerical execution remains on the LawSynth service/runtime boundary.
The application controller is framework-neutral and can mount its accessible shell into an owned DOM element. Providers are explicit so authentication, persistence, logging, notification delivery, clocks, and identifiers remain replaceable at the application boundary.
const app = createStudioApp({ providers: scope, route: parseRoute(location.href) });
app.mount(document.querySelector("#app")!);
await app.start();
Call stop() during permanent teardown. It flushes pending settings,
unsubscribes state listeners, detaches keyboard shortcuts, cancels the active
workspace, and disposes providers in reverse registration order.