Align Auto-Dig Quasar with canonical runtime capability boundary #17
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/auto-dig-quasar!17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "agent/document-runtime-capability-boundary"
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
auto-dig-quasaras the Auto-Dig specialization of the browser UI, not a second Quasar runtimedocs/CAPABILITY-BOUNDARY.mdquasar -> starintel-server -> external servicespathno deployment path through a Common Lisp backendclaim cannot returnWhy
The Auto-Dig fork still carried the old JavaScript-only architecture wording after canonical Quasar moved to a Common Lisp control-plane/runtime model. This keeps the fork aligned with
quasar-ui, canonicalquasar, StarIntel Server, and BBPD.Validation
Documentation plus architecture-regression-test change; no product runtime behavior changed. CI must pass on the current head before merge.