Spike native shells and define local-first integrations

README.md

@@ -34,6 +34,8 @@ contracts before committing to a large implementation.
   profiles for OpenAI, Anthropic, Gemini, Groq, Cerebras, DeepSeek, and more.
 - Usage history, burn rate, reset windows, and forecasts with visible data
   provenance instead of invented precision.
+- Optional first-class Buzz channels, messages, agents, and confirmed redacted
+  pane sharing without making Buzz a requirement.
 
 Start with [the product spec](docs/PRODUCT_SPEC.md),
 [architecture](docs/ARCHITECTURE.md), [research map](docs/RESEARCH.md), and
@@ -51,3 +53,10 @@ cargo run -p lumbridge
 
 See [the testing strategy](docs/TESTING.md) for fake harnesses, ACP replay,
 terminal conformance, UI driving, recovery, performance, and packaging tests.
+
+The accepted local/remote boundary is recorded in
+[decision 0003](docs/decisions/0003-local-data-and-remote-sessions.md). The two
+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).