[starintel-ide] Compose Lem SDL2, Quasar, A2A, STAR-KB/spec IDE, Git and LLM UX

Parent: #1 Blocked by the control-plane decision in #2. This issue is an integration epic; it does not authorize implementation while the repository control mode is `unselected`. ## Goal Turn Lem into the native desktop StarIntel IDE ("StarIntel Emacs"): use the SDL2 graphical frontend, port Quasar capabilities into native Common Lisp/Lem commands and views, expose Actor2Actor workflows, and provide first-class STAR-KB/spec/StarLang development UX. ## Ownership / dependencies - #5 owns editor core, graphical UI behavior, windows/workspaces, completion/navigation. - #8 owns Prolog and StarLang language-mode/LSP/parser integration. - #9 owns Magit/Forge-like Git/project/file/session workflows. - #11 owns LLM assistants, MCP/tool UX, streaming/cancellation/authorization. - #12 owns StarIntel dashboards and service clients. - This issue owns the integration contracts between those slices plus Quasar/A2A/spec/KB composition. ## Frontend - Primary desktop frontend: Lem SDL2. - Keep editor-core behavior frontend-independent. - Use Lem graphics primitives for images/shapes/panels; any immediate-mode UI layer must sit behind a narrow graphical interface and must not become a hard dependency of editor core. - Preserve ncurses/headless testability for non-visual behavior. ## Quasar port Port behavior and service contracts, not React components. Native Lem surfaces: - actor registry/browser - actor inspector and manifests - config/secrets metadata browser (never reveal plaintext secrets) - target submission and status - dataset/workflow explorer - graph/relationship views - event/log stream - approvals - StarIntel server connection/session status Quasar remains a reference client and compatibility target; Lem talks to the same StarIntel APIs/protocols. ## Actor2Actor Provide: - actor registry discovery - A2A endpoint/capability inspection - request composer - structured message/result buffers - streaming progress/events - cancellation - capability/permission display - per-request correlation IDs - transcript/provenance links - test doubles so the IDE starts and tests without live actors ## STAR-KB / Prolog - first-class Prolog major mode - STAR-KB browser and query REPL - jump fact -> source/provenance - predicate/reference search - query history - explanation/proof buffer - JSON-LD -> Prolog fact inspection - validation commands - graph visualization adapters ## Spec IDE - first-class spec buffers - requirements/acceptance/test linkage - jump spec <-> code <-> issue <-> test - validation and stale-evidence warnings - structured diagnostics - generated implementation/test skeleton commands without auto-execution ## StarLang - native major mode - syntax/highlighting/indentation - tree-sitter/parser integration where available - compile/check commands - diagnostics - REPL/runtime interaction - schema/config/actor definitions - jump-to-definition/references - format command - snippets/templates ## Git / Magit-style UX Implemented under #9 but integrated here: - status buffer - hunk staging/unstaging - diff/log/blame - branch/worktree - commit - pull/push - issue/PR/Forge views - StarIntel-aware repo/worktree shortcuts - destructive operations remain explicitly confirmed ## Document editor - Org remains a primary human-editable document format - Markdown/plain text - specs/reports/ADRs - links among issues, commits, actors, datasets, star:// resources and KB facts - project/session restore ## LLM assistants Implemented under #11 but integrated into code/spec/KB buffers: - chat/rewrite/explain commands - selected-region actions - code/spec review - Prolog/KB reasoning tools - StarIntel actor/MCP/A2A tools - streaming and cancellation - provider/tool selection - no provider initialization during startup - missing credentials/providers never break Lem ## Reports / evidence Durable implementation evidence belongs under: `reports/starintel-ide/YYYY-MM-DD-<slice>.org` Each report records: - start SHA / final SHA - upstream Lem SHA - Quasar and Quasar UI reference SHAs - exact commands - red/green test evidence - SDL2 launch evidence - screenshots where the slice has visual behavior - CI status - known gaps - rollback instructions Do not commit secrets, private Org contents, tokens, or raw sensitive StarIntel data. ## Desktop acceptance On the user's desktop: - SDL2 build launches under the active Wayland/XWayland environment - cold/warm launch - file/project open - Git status/stage/commit - Prolog query - STAR-KB browse/query - StarLang edit/check - spec validation - Quasar actor registry view - A2A mock request and live smoke where configured - LLM disabled startup - LLM mock stream/cancel - crash/restart/session restore - screenshots for graphical flows ## Acceptance - [ ] SDL2 is the tested primary GUI frontend. - [ ] Quasar's required StarIntel workflows have native Lem owners. - [ ] Actor2Actor is inspectable and usable from the editor. - [ ] Prolog/STAR-KB and StarLang have first-class editor modes. - [ ] Spec/code/test/issue navigation works. - [ ] Git workflow is usable without leaving Lem for normal daily work. - [ ] LLM features are optional, lazy, cancellable and permission-aware. - [ ] Evidence is recorded under `reports/starintel-ide/`. - [ ] Desktop graphical behavior has screenshot evidence. - [ ] Exact-head CI and local gates are green. ## Stop conditions - #2 still has no explicit ADADR/Auto-RAGE selection. - Frontend code leaks into editor-core abstractions. - Plaintext secrets enter buffers/logs/events. - A destructive Git/StarIntel action lacks explicit target/confirmation. - A live service is required for deterministic tests.

nsaspy commented

2026-09-19 02:57:04 +00:00

Owner

Parent: #1

Blocked by the control-plane decision in #2. This issue is an integration epic; it does not authorize implementation while the repository control mode is unselected.

Goal

Turn Lem into the native desktop StarIntel IDE ("StarIntel Emacs"): use the SDL2 graphical frontend, port Quasar capabilities into native Common Lisp/Lem commands and views, expose Actor2Actor workflows, and provide first-class STAR-KB/spec/StarLang development UX.

Ownership / dependencies

#5 owns editor core, graphical UI behavior, windows/workspaces, completion/navigation.
#8 owns Prolog and StarLang language-mode/LSP/parser integration.
#9 owns Magit/Forge-like Git/project/file/session workflows.
#11 owns LLM assistants, MCP/tool UX, streaming/cancellation/authorization.
#12 owns StarIntel dashboards and service clients.
This issue owns the integration contracts between those slices plus Quasar/A2A/spec/KB composition.

Frontend

Primary desktop frontend: Lem SDL2.
Keep editor-core behavior frontend-independent.
Use Lem graphics primitives for images/shapes/panels; any immediate-mode UI layer must sit behind a narrow graphical interface and must not become a hard dependency of editor core.
Preserve ncurses/headless testability for non-visual behavior.

Quasar port

Port behavior and service contracts, not React components.

Native Lem surfaces:

actor registry/browser
actor inspector and manifests
config/secrets metadata browser (never reveal plaintext secrets)
target submission and status
dataset/workflow explorer
graph/relationship views
event/log stream
approvals
StarIntel server connection/session status

Quasar remains a reference client and compatibility target; Lem talks to the same StarIntel APIs/protocols.

Actor2Actor

Provide:

actor registry discovery
A2A endpoint/capability inspection
request composer
structured message/result buffers
streaming progress/events
cancellation
capability/permission display
per-request correlation IDs
transcript/provenance links
test doubles so the IDE starts and tests without live actors

Spec IDE

first-class spec buffers
requirements/acceptance/test linkage
jump spec <-> code <-> issue <-> test
validation and stale-evidence warnings
structured diagnostics
generated implementation/test skeleton commands without auto-execution

StarLang

native major mode
syntax/highlighting/indentation
tree-sitter/parser integration where available
compile/check commands
diagnostics
REPL/runtime interaction
schema/config/actor definitions
jump-to-definition/references
format command
snippets/templates

Git / Magit-style UX

Implemented under #9 but integrated here:

status buffer
hunk staging/unstaging
diff/log/blame
branch/worktree
commit
pull/push
issue/PR/Forge views
StarIntel-aware repo/worktree shortcuts
destructive operations remain explicitly confirmed

Document editor

Org remains a primary human-editable document format
Markdown/plain text
specs/reports/ADRs
links among issues, commits, actors, datasets, star:// resources and KB facts
project/session restore

LLM assistants

Implemented under #11 but integrated into code/spec/KB buffers:

chat/rewrite/explain commands
selected-region actions
code/spec review
Prolog/KB reasoning tools
StarIntel actor/MCP/A2A tools
streaming and cancellation
provider/tool selection
no provider initialization during startup
missing credentials/providers never break Lem

Reports / evidence

Durable implementation evidence belongs under:

reports/starintel-ide/YYYY-MM-DD-<slice>.org

Each report records:

start SHA / final SHA
upstream Lem SHA
Quasar and Quasar UI reference SHAs
exact commands
red/green test evidence
SDL2 launch evidence
screenshots where the slice has visual behavior
CI status
known gaps
rollback instructions

Do not commit secrets, private Org contents, tokens, or raw sensitive StarIntel data.

Desktop acceptance

On the user's desktop:

SDL2 build launches under the active Wayland/XWayland environment
cold/warm launch
file/project open
Git status/stage/commit
Prolog query
STAR-KB browse/query
StarLang edit/check
spec validation
Quasar actor registry view
A2A mock request and live smoke where configured
LLM disabled startup
LLM mock stream/cancel
crash/restart/session restore
screenshots for graphical flows

Acceptance

SDL2 is the tested primary GUI frontend.
Quasar's required StarIntel workflows have native Lem owners.
Actor2Actor is inspectable and usable from the editor.
Prolog/STAR-KB and StarLang have first-class editor modes.
Spec/code/test/issue navigation works.
Git workflow is usable without leaving Lem for normal daily work.
LLM features are optional, lazy, cancellable and permission-aware.
Evidence is recorded under reports/starintel-ide/.
Desktop graphical behavior has screenshot evidence.
Exact-head CI and local gates are green.

Stop conditions

#2 still has no explicit ADADR/Auto-RAGE selection.
Frontend code leaks into editor-core abstractions.
Plaintext secrets enter buffers/logs/events.
A destructive Git/StarIntel action lacks explicit target/confirmation.
A live service is required for deterministic tests.

Rows
Columns

[starintel-ide] Compose Lem SDL2, Quasar, A2A, STAR-KB/spec IDE, Git and LLM UX #17