Scope Quasar UI to browser and standalone capabilities #168

Merged

lost-rob0t merged 5 commits from agent/document-runtime-capability-boundary into main

2026-08-10 04:32:30 +00:00

lost-rob0t commented

2026-08-10 04:25:02 +00:00

(Migrated from github.com)

What changed

rewrites the README to define quasar-ui as the browser UI and standalone web edition, not the complete Quasar/StarIntel runtime
adds docs/CAPABILITY-BOUNDARY.md
scopes docs/ROADMAP.md to standalone web-edition responsibilities instead of globally banning the Common Lisp runtime path
documents connected mode through canonical quasar, starintel-server, and external services such as star-bbpd
updates the roadmap invariant test so CI rejects the old global no deployment path through a Common Lisp backend claim and requires the new connected-runtime boundary

Why

The previous roadmap and its regression test treated the JavaScript-only standalone target as the architecture for all Quasar deployments. That contradicted the canonical Quasar runtime. Standalone browser mode remains first-class, but it is now documented and tested as a bounded subset deployment.

Validation

Documentation plus architecture-regression-test change; no browser runtime behavior changed. CI must pass on the current head before merge.

## What changed - rewrites the README to define `quasar-ui` as the browser UI and standalone web edition, not the complete Quasar/StarIntel runtime - adds `docs/CAPABILITY-BOUNDARY.md` - scopes `docs/ROADMAP.md` to standalone web-edition responsibilities instead of globally banning the Common Lisp runtime path - documents connected mode through canonical `quasar`, `starintel-server`, and external services such as `star-bbpd` - updates the roadmap invariant test so CI rejects the old global `no deployment path through a Common Lisp backend` claim and requires the new connected-runtime boundary ## Why The previous roadmap and its regression test treated the JavaScript-only standalone target as the architecture for all Quasar deployments. That contradicted the canonical Quasar runtime. Standalone browser mode remains first-class, but it is now documented and tested as a bounded subset deployment. ## Validation Documentation plus architecture-regression-test change; no browser runtime behavior changed. CI must pass on the current head before merge.