backeer-opencode 0.1.4 → 0.2.0

package/CHANGELOG.md

@@ -2,6 +2,25 @@
 
 All notable changes to `backeer-opencode` are documented here.
 
+## 0.2.0 - 2026-09-01
+
+- Notify when an OpenCode assistant run completes successfully.
+- Notify terminal session errors with redacted diagnostic summaries.
+- Warn once when a session reaches its third retry attempt.
+- Notify once per version when an OpenCode update is available.
+- Add granular lifecycle configuration and lifecycle state to `/backeer status`.
+- Use stable lifecycle event IDs and the completion sound for successful runs.
+
+## 0.1.5 - 2026-09-01
+
+- Check the NPM registry for a newer Backeer plugin version once per day.
+- Notify the OpenCode agent once per session when an update is available.
+- Add `/backeer update-check` for an explicit registry check.
+- Add `/backeer update` to delegate an exact-version installation and
+  verification workflow to the OpenCode agent.
+- Require the agent workflow to preserve the token and avoid `@latest` cache
+  ambiguity.
+
 ## 0.1.4 - 2026-09-01
 
 - Add `/backeer` and `/backeer status` for an in-session integration report.

package/README.md

@@ -1,10 +1,11 @@
 # Backeer for OpenCode
 
 `backeer-opencode` connects OpenCode to Backeer. It sends mobile notifications
-for permission requests, questions, and completed todo lists. While a permission
-is pending, it also consumes an authenticated Backeer command stream so an
-authorized user can answer **Allow once**, **Always allow**, or **Reject** from
-the Backeer iOS application.
+for permission requests, questions, completed todo lists, completed assistant
+runs, session failures, prolonged retries, and OpenCode updates. While a
+permission is pending, it also consumes an authenticated Backeer command stream
+so an authorized user can answer **Allow once**, **Always allow**, or **Reject**
+from the Backeer iOS application.
 
 The plugin uses outbound HTTPS only. It does not start a server or require an
 inbound firewall rule.
@@ -109,6 +110,13 @@ environment variables are supported:
 | `BACKEER_NOTIFY_PERMISSIONS` | Set to `false` to disable permission notifications and remote replies |
 | `BACKEER_NOTIFY_QUESTIONS` | Set to `false` to disable question notifications |
 | `BACKEER_NOTIFY_TODOS` | Set to `false` to disable todo-completion notifications |
+| `BACKEER_NOTIFY_LIFECYCLE` | Set to `false` to disable every lifecycle notification |
+| `BACKEER_NOTIFY_SESSION_COMPLETED` | Set to `false` to disable successful-run notifications |
+| `BACKEER_NOTIFY_SESSION_ERRORS` | Set to `false` to disable session-error notifications |
+| `BACKEER_NOTIFY_SESSION_RETRIES` | Set to `false` to disable retry warnings |
+| `BACKEER_NOTIFY_OPENCODE_UPDATES` | Set to `false` to disable OpenCode update notifications |
+| `BACKEER_SESSION_COMPLETION_MIN_SECONDS` | Minimum run duration; defaults to `0` (every completion) |
+| `BACKEER_RETRY_ATTEMPT_THRESHOLD` | First retry attempt that triggers a warning; defaults to `3` |
 | `BACKEER_LOG_LEVEL` | `info` (default), `error`, `debug`, or `silent` |
 
 For npm installations, non-secret options can also be supplied through the
@@ -122,7 +130,16 @@ OpenCode plugin tuple syntax:
       {
         "permissions": true,
         "questions": true,
-        "todos": true
+        "todos": true,
+        "lifecycle": {
+          "enabled": true,
+          "completed": true,
+          "errors": true,
+          "retries": true,
+          "updates": true,
+          "completionMinSeconds": 0,
+          "retryAttemptThreshold": 3
+        }
       }
     ]
   ]
@@ -130,7 +147,8 @@ OpenCode plugin tuple syntax:
 ```
 
 Supported options are `origin`, `tokenFile`, `permissions`, `questions`,
-`todos`, and `logLevel`. The token itself is deliberately not a plugin option.
+`todos`, `lifecycle`, and `logLevel`. Use `"lifecycle": false` to disable the
+entire lifecycle group. The token itself is deliberately not a plugin option.
 
 ## Console feedback
 
@@ -140,6 +158,9 @@ The plugin writes compact, single-line status messages instead of raw HTTP logs:
 ◆ Backeer  Permission request sent
 ◆ Backeer  Question sent
 ◆ Backeer  Todo completion sent
+◆ Backeer  Task completion sent
+◆ Backeer  Retry warning sent
+◆ Backeer  Task failure sent
 ✓ Backeer  Decision applied: Always allow
 ! Backeer  Connection interrupted — retrying
 ```
@@ -156,14 +177,16 @@ The plugin registers a `/backeer` command inside OpenCode:
 ```text
 /backeer
 /backeer status
+/backeer update-check
+/backeer update
 /backeer token
 /backeer token-file /absolute/path/to/a/protected-token-file
 ```
 
 The status report shows the plugin version, gateway reachability, token source,
-notification switches, command-stream state, pending permissions, and log level.
-It never displays the token. Gateway reachability does not validate the source
-credential.
+notification switches and lifecycle thresholds, command-stream state, pending
+permissions, and log level. It never displays the token. Gateway reachability
+does not validate the source credential.
 
 `/backeer token` displays safe rotation instructions. Never paste a raw token
 into slash-command arguments because OpenCode may retain command text in session
@@ -173,6 +196,19 @@ atomically copies it to the configured token location, applies mode `0600`, and
 activates it immediately without restarting OpenCode. The source file is not
 removed.
 
+The plugin checks the NPM registry at most once every 24 hours. When a newer
+version exists, it adds one synthetic update notice to each OpenCode session so
+the agent can inform the user. The notice never authorizes installation by
+itself.
+
+`/backeer update-check` performs an explicit check. `/backeer update` is the
+user authorization point: it gives the OpenCode agent an exact-version install
+command, requires verification of both the global version pin and package
+cache, and forbids reading or changing the Backeer token. The agent does not
+terminate the active OpenCode process; restart OpenCode after a successful
+update. Exact versions are used instead of `@latest` to avoid stale OpenCode
+package caches.
+
 ## Events and decisions
 
 The plugin publishes:
@@ -183,6 +219,21 @@ The plugin publishes:
 | `question.asked` | Notification-only question card |
 | `question.v2.asked` | Notification-only question card, including plan-mode questions |
 | `todo.updated` | One notification when a non-empty list transitions to fully completed |
+| `message.updated` + `session.status`/`session.idle` | One notification for each successfully completed assistant run |
+| `session.error` | Critical failure notification with a redacted error summary |
+| `session.status` (`retry`) | One warning when the configured retry threshold is reached |
+| `installation.update-available` | One notification per available OpenCode version |
+
+Completion requires a completed, error-free assistant message in the current
+busy cycle. An idle event caused by a pending permission or question is not
+reported as successful. Repeated idle callbacks, retry callbacks, error events,
+and update events use stable correlation IDs so they do not create duplicate
+push notifications.
+
+Lifecycle payloads intentionally omit command arguments, model output, file
+paths and diffs, stack traces, HTTP response bodies, and response headers. Error
+messages are length-limited and redact common credentials, URL queries, and
+filesystem paths before leaving the OpenCode host.
 
 Permission commands are delivered at least once. The plugin caches terminal
 acknowledgements and resends the same acknowledgement on redelivery without