Referenced by2
Labels2

Referencing ideas

IdeaStatusTagsSummaryKatz
scopeTypeScript package standards for `packages/extension` ( npm `reqlan-extension` ), especially UI state. Complements [development_core.rust_mindset] and [extension_architecture.state_machine_mindset]. Webview inventory: [webview_doc.webview]. Package role: [core_architecture.extension_package].0.040
webview_app_statedoneComplex webviews ( activity bar, Ideas Summary ) own a single `AppState` class in `state/app.svelte.ts`. Fields that drive UI are Svelte 5 `$state` properties on that class; side effects and host I / O are methods. Export one module singleton ( `export const app = new AppState()` ) and inject it via [svelte_app_context]. Do not use `svelte/store` writable / readable stores for new UI, and do not put zustand inside webview code ( [zustand_boundary] ). Simple panels ( export form, onboarding, index diagnostics ) may keep `$state` on the root `App.svelte` instead of a separate AppState module when the surface is a single form / flow. Related: ["../extension/workspace-summary/ideas_summary/webview.rq".table_column_filters] `$derived` binding rule; ["../extension/workspace-summary/ideas_summary/graphical_graph.rq".graph_ui_persistence].0.070

Reference labels

"../../packages/extension/webviews/onboarding/App.svelte", ../../packages/extension/webviews/onboarding/App.svelte