Add Common Lisp control plane and CLOG WebSocket bridge #1
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
priority:P1
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/quasar!1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "agent/common-lisp-control-plane"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What changed
quasar-uiapplication asfrontend/at commit83dc45fsrc/app/main.tsxbootstrap without deleting componentspostMessagefrontend client exposed aswindow.QuasarControlPlaneClientArchitecture
React, Cytoscape, mobile navigation, routes, themes, agents, documents, datasets, imports, settings, statistics, and PWA behavior stay in the browser UI. High-frequency rendering and interaction remain local. Durable or privileged operations cross the CLOG WebSocket bridge to the Common Lisp control plane.
Current vertical slice
The control plane exposes:
system.capabilitiesworkspace.snapshotworkspace.applystarlang.statusstarlang.loadThe migration ledger maps the remaining current UI surfaces to their Common Lisp commands without deleting features.
Validation
Follow-on boundary
This PR establishes the runnable control-plane/transport foundation. It does not claim that every existing browser persistence and integration call has already been replaced; that migration is enumerated in
docs/UI-MIGRATION.mdwith non-regression gates.