feat: add interactive VT and workspace command plane

2026-08-31 17:05:49 -07:00
parent 32d190c6c6
commit b838d000db
54 changed files with 3004 additions and 113 deletions
@@ -0,0 +1,27 @@
+# 0007: Lumbridge Harness is optional, separate, and capability-scoped
+
+Status: accepted for architecture; implementation and fork policy pending.
+
+Lumbridge may distribute a separately versioned Lumbridge Harness for prompt
+refinement, trace analysis, recommendations, and agent coordination. The native
+Rust terminal workspace remains complete without it, and the Harness does not
+run inside the UI process.
+
+The captured DeepSeek Harness is an MIT-licensed and architecturally useful
+reference, but it is also an unaudited Node/TypeScript developer preview with a
+web client and broad native dependency closure. A maintained fork, if selected,
+lives in its own repository/process, preserves required notices, and exposes a
+small versioned protocol. Its React UI is not embedded in Lumbridge. We can later
+replace the implementation with a first-party Rust service without changing the
+desktop contract.
+
+Model access is provider-neutral and begins with OpenAI-compatible endpoints so
+development can use a self-hosted Spark/Qwen model or a user-selected service
+such as Cerebras. Endpoint credentials are opaque secret-store handles.
+
+Trace analysis is opt-in per workspace. The user chooses the trace projection
+and destination; local processing stays local, while hosted processing requires
+an explicit preview and consent. Suggestions and decision-shelf choices carry no
+authority. Any setup, launch, mutation, or autopilot action becomes a typed
+workspace plan and can use only the Observe, Configure, or Execute capability
+granted to that run.