@remembrance-ai/opencode-plugin 0.1.53 → 0.1.60

package/README.md

@@ -21,6 +21,17 @@ Restart opencode. Remembrance then appears in its tools list, adds bounded
 matching guidance to eligible model turns, observes completed use, and asks once
 for concise, redacted feedback.
 
+At session creation, the plugin performs a bounded, credential-free release
+check. If a newer verified version exists, opencode shows a notice and gives the
+agent the locally bundled setup command. The agent must ask before running it,
+and the user must restart opencode afterward. Remembrance never updates itself
+silently. Set `REMEMBRANCE_CLIENT_UPDATE_CHECK=0` to disable the advisory check.
+
+Older opencode installations that predate this startup check still learn about
+a verified update on their next successful Remembrance query. The API places a
+command-free notice first in the legacy contribution directive; only this
+installed package supplies the trusted local setup command.
+
 Use `npx -y @remembrance-ai/opencode-plugin setup --dry-run` to preview the merged
 config. `opencode.json` in this package is a reference config for managed
 deployments.
@@ -34,6 +45,25 @@ turn. Empty or unavailable queries never block the task. The plugin also
 observes successful tool calls and prompts once for feedback after meaningful
 use.
 
+## Installation identity and preferences
+
+The bundled local MCP automatically reuses the local TOFU key as one stable
+installation principal and obtains a revocable 24-hour principal session.
+A child runtime profile distinguishes this host surface without sending a
+hostname, username, config path, or repository path. Runtime profiles do not
+consume extra agent slots.
+
+An optional single-use token from **Dashboard > Agents > Instances > Install on
+this device** links the installation to the signed-in member so bounded working
+preferences can follow that engineer. The token expires after ten
+minutes and never belongs in reusable key-distribution instructions. Unlinked
+installs remain fully functional with installation-local preferences. Built-in
+controls cover common presentation choices; extensible preferences can guide
+discretionary workflow and strategy selection. They may reorder only
+already-relevant skills inside one match tier or apply a surgical sidecar, and
+can never weaken safety, authorization, privacy, applicability, required skill
+steps, validation, review, or organization policy.
+
 ## Organization key
 
 The MCP server reads the same Remembrance config as the native plugins, so one
@@ -74,23 +104,28 @@ link-local self-host also requires `REMEMBRANCE_ALLOW_PRIVATE_REGISTRY=true`.
 
 ## What the plugin does
 
-| Event                                | Behavior                                                      |
-| ------------------------------------ | ------------------------------------------------------------- |
+| Event                                | Behavior                                                        |
+| ------------------------------------ | --------------------------------------------------------------- |
 | `session.created`                    | Reports activation health and how to verify organization scope. |
-| `chat.message`                       | Runs the fail-open query helper for the current user turn.     |
-| `experimental.chat.system.transform` | Adds bounded Remembrance guidance before model dispatch.       |
-| `tool.execute.after`                 | Correlates query, invocation, detail, and contribution calls.  |
-| `session.idle`                       | Shows the contribution nudge once per engagement.              |
+| `chat.message`                       | Runs the fail-open query helper for the current user turn.      |
+| `experimental.chat.system.transform` | Adds bounded Remembrance guidance before model dispatch.        |
+| `tool.execute.after`                 | Correlates query, invocation, detail, and contribution calls.   |
+| `session.idle`                       | Shows a compact contribution nudge once per engagement.         |
 
 Set `REMEMBRANCE_AUTO_QUERY=0` to disable the query, or
-`REMEMBRANCE_AUTO_CONTRIBUTE=0` to disable the completion nudge.
+`REMEMBRANCE_AUTO_CONTRIBUTE=0` to disable the completion nudge. OpenCode's
+current idle event exposes this compact instruction as a toast or structured
+log rather than forcing another agent turn.
 
 ## Host policy
 
 A tenant or privacy-policy denial in the host happens before Remembrance is
 called, so it is not a Remembrance misconfiguration — the same boundary as a
 Codex tenant/privacy-policy denial, which occurs before Remembrance is reached
-and must not be reported as a Remembrance setup failure.
+and must not be reported as a Remembrance setup failure. The plugin reports one
+local, content-free alert: **Remembrance was blocked by host policy before
+reaching Remembrance. Nothing was sent. Querying remains available.** It does
+not retry or automatically create a handoff.
 
 ## Generated files
 

package/opencode.json

@@ -3,18 +3,13 @@
   "mcp": {
     "remembrance": {
       "type": "local",
-      "command": [
-        "npx",
-        "-y",
-        "@remembrance-ai/mcp-server@0.1.53"
-      ],
+      "command": ["npx", "-y", "@remembrance-ai/mcp-server@0.1.60"],
       "enabled": true,
       "environment": {
-        "REMEMBRANCE_PLUGIN_HOST": "opencode"
+        "REMEMBRANCE_PLUGIN_HOST": "opencode",
+        "REMEMBRANCE_HOST_SURFACE": "cli"
       }
     }
   },
-  "plugin": [
-    "@remembrance-ai/opencode-plugin@0.1.53"
-  ]
+  "plugin": ["@remembrance-ai/opencode-plugin@0.1.60"]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remembrance-ai/opencode-plugin",
-  "version": "0.1.53",
+  "version": "0.1.60",
   "license": "Apache-2.0",
   "description": "opencode plugin for Remembrance session hooks, tool observation, and contribution nudges.",
   "type": "module",