@volter-ai-dev/supercode-ui 0.1.29 → 0.1.31

package/README.md

@@ -60,15 +60,17 @@ import {
   SessionList,
 } from '@volter-ai-dev/supercode-ui/preact';
 import { HarnessLogo, harnessLogoDataUrl } from '@volter-ai-dev/supercode-ui/preact/logo';
+import { HarnessAdvisory, HarnessSettingsPanel } from '@volter-ai-dev/supercode-ui/preact/settings';
 import { groupConversation } from '@volter-ai-dev/supercode-ui/core';
 ```
 
 The public components are `SupercodeMessenger`, `Conversation`, `TranscriptEntry`,
 `ActivityGroup`, `RequestCard`, `SessionList`, `SessionRow`, `Composer`, `ContinuationBar`,
-`LoadingStatus`, `TaskPlan`, `SessionDetails`, and `HarnessLogo`. Pure state readers, selectors,
+`LoadingStatus`, `TaskPlan`, `SessionDetails`, `HarnessLogo`, `HarnessAdvisory`, and
+`HarnessSettingsPanel`. Pure state readers, selectors,
 formatters, and intent constructors live at `supercode-ui/core` and have no DOM or Preact imports.
 For genuine partial delivery, the `preact/logo`, `preact/icon`, `preact/conversation`, `preact/sessions`,
-`preact/composer`, and `preact/messenger` subpaths are independently tree-shaken artifacts; taking
+`preact/composer`, `preact/settings`, and `preact/messenger` subpaths are independently tree-shaken artifacts; taking
 the logo does not pull in Markdown, the messenger, or session-list code.
 `harnessLogoDataUrl(id)` gives non-Preact launchers the same self-contained canonical SVG; it
 returns `null` for an unknown harness rather than inventing a fallback identity.
@@ -126,6 +128,12 @@ errors, and owned/attached identities without reimplementing transcript or capab
 `SupercodeController` snapshots and persisted inventory into it, then handles `SupercodeUiIntent`.
 The browser cannot supply locators, credentials, policy, environment variables, or arbitrary
 materialization paths. Session keys and target harnesses must be revalidated by the host.
+Harness configuration is similarly narrow: the UI can only submit a choice from the revisioned
+interoperability-control report it received. The headless controller rejects configuration unless
+the trusted embedding host explicitly opts into `allowHarnessConfiguration`, revalidates the
+active harness, control key, declared choice, reset capability, and revision, then asks the local
+service to update the native file atomically. The UI shows the scope, precedence uncertainty, and
+security consequence before it emits that intent; it is not a generic preferences editor.
 `pickContext` is optional and host-owned: the default composer shows one attachment control when
 this callback exists and accepts either typed text context (`detail`) or native image inputs
 (`url`). Images can also be pasted or dropped directly, and an image-only turn is sent without