feat: add interactive VT and workspace command plane

README.md

@@ -19,9 +19,10 @@ as installable binaries; building from source will remain supported.
 This repository is in architecture and vertical-slice phase. The installable
 binary is still a scaffold, while the isolated native UI spikes now exercise an
 interactive six-surface workspace and the root workspace contains the first
-bounded local PTY and runtime-actor boundaries. The GPUI slice renders one real
-actor-owned PTY beside five deterministic surfaces. We are still validating
-terminal emulation, standalone runtime IPC/durability, ACP integration,
+bounded local PTY, runtime-actor, VT engine, and capability-gated workspace
+command boundaries. The GPUI slice renders one real actor-owned VT session beside
+five deterministic surfaces. We are still validating the dedicated styled
+terminal renderer, standalone runtime IPC/durability, ACP integration,
 packaging, and usage-data contracts before a large implementation.
 
 ## Product shape
@@ -39,6 +40,9 @@ packaging, and usage-data contracts before a large implementation.
   provenance instead of invented precision.
 - Optional first-class Buzz channels, messages, agents, and confirmed redacted
   pane sharing without making Buzz a requirement.
+- An optional Lumbridge Harness that can suggest, coordinate, and—with explicit
+  execution capability—manage agents through the same audited command plane as
+  the human UI. Lumbridge remains useful without it.
 
 Start with [the product spec](docs/PRODUCT_SPEC.md),
 [architecture](docs/ARCHITECTURE.md), [research map](docs/RESEARCH.md), and
@@ -63,3 +67,5 @@ native shell candidates live in [`spikes/`](spikes/), with results tracked in
 [the UI scorecard](docs/UI_SPIKE_SCORECARD.md).
 The signed-protocol and pane-sharing boundary is in
 [the Buzz integration design](docs/BUZZ_INTEGRATION.md).
+Brand masters, platform-ready raster exports, and usage rules are in
+[`assets/brand/`](assets/brand/) and [the brand guide](docs/BRAND.md).