Browser UI entrypoint, application composition, and client-side modules.
| File | Role |
|---|---|
| App.svelte | Browser application composition: projects/sessions, conversation transcript/composer, commands, recovery controls, and workbench panels. |
| app.css | Keep conversation authority visible at narrow widths and available to assistive tech. |
| main.ts | Browser mount entrypoint and global application setup. |
| Folder | Role / next waypoint |
|---|---|
| lib/ | Browser workspace/session state, API bindings, commands, file drafts, operations, and reusable presentation components. |
Start with the nearest component or state entry point, then trace UI state through the typed API boundary to the Rust gateway and daemon owner before changing behavior. Keep presentation-only state separate from durable run authority, and update the local component or file route when the browser surface moves.
Navigation: Parent waypoint · Repository map.
Keep this waypoint aligned when local files or child responsibilities change. Descriptions are orientation, not a substitute for reading the current implementation.