backeer-opencode 0.2.0 → 0.2.2

package/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 All notable changes to `backeer-opencode` are documented here.
 
+## 0.2.2 - 2026-09-01
+
+- Show user-facing Backeer delivery and decision results in the OpenCode
+  conversation instead of writing them into the TUI input area.
+- Queue conversation feedback until the session is idle and mark it as ignored
+  so it cannot trigger another agent response or enter model context.
+- Send technical diagnostics through OpenCode's structured application log API
+  instead of stdout.
+
+## 0.2.1 - 2026-09-01
+
+- Add `/backeer doctor` for read-only local configuration, protected token,
+  source authentication, gateway capability, and APNs diagnostics.
+- Add `/backeer test` to send a uniquely correlated end-to-end mobile test
+  notification.
+- Keep doctor reports and command output free of bearer token values.
+
 ## 0.2.0 - 2026-09-01
 
 - Notify when an OpenCode assistant run completes successfully.

package/README.md

@@ -150,25 +150,28 @@ Supported options are `origin`, `tokenFile`, `permissions`, `questions`,
 `todos`, `lifecycle`, and `logLevel`. Use `"lifecycle": false` to disable the
 entire lifecycle group. The token itself is deliberately not a plugin option.
 
-## Console feedback
+## Conversation feedback
 
-The plugin writes compact, single-line status messages instead of raw HTTP logs:
+User-facing status messages appear as compact Backeer entries in the OpenCode
+conversation:
 
 ```text
-◆ 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
+Backeer ✓ Permission request sent
+Backeer ✓ Question sent
+Backeer ✓ Todo completion sent
+Backeer ✓ Task completion sent
+Backeer ✓ Decision applied: Always allow
 ```
 
-TTY output uses restrained status colors and respects `NO_COLOR`. Repeated
-connection errors are suppressed for 30 seconds. Normal `info` output omits HTTP
-status codes and internal errors; set `BACKEER_LOG_LEVEL=debug` when technical
-details are needed. Set it to `error` for failures only or `silent` for no output.
+These entries are marked `noReply` and `ignored`, so they are visible without
+starting another agent turn or entering model context. Feedback generated while
+an agent is active is queued until the session becomes idle; it never writes to
+the user's input field.
+
+Technical diagnostics use OpenCode's structured application log API instead of
+stdout. Normal `info` logging omits HTTP details; set
+`BACKEER_LOG_LEVEL=debug` when technical details are needed. Set it to `error`
+for failures only or `silent` to disable structured logs.
 
 ## OpenCode command
 
@@ -177,6 +180,8 @@ The plugin registers a `/backeer` command inside OpenCode:
 ```text
 /backeer
 /backeer status
+/backeer doctor
+/backeer test
 /backeer update-check
 /backeer update
 /backeer token
@@ -188,6 +193,16 @@ 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 doctor` performs a read-only diagnostic pass. It verifies the local
+configuration, protected token-file permissions, source authentication, event
+and command capabilities, and gateway APNs readiness. It does not create an
+event, open a command stream, or display the bearer token.
+
+`/backeer test` publishes one uniquely correlated, non-actionable application
+event and asks the gateway to deliver a real push notification. Use it after
+installation, token rotation, or network changes to verify the complete path
+from OpenCode to the phone.
+
 `/backeer token` displays safe rotation instructions. Never paste a raw token
 into slash-command arguments because OpenCode may retain command text in session
 history. To rotate from inside OpenCode, first place the new token in an absolute
@@ -251,10 +266,11 @@ npm run publish:check
 
 ## Development architecture
 
-The npm plugin runs from the modular source in `src`. Configuration, console
-reporting, HTTP transport, SSE consumption, event publishing, permission command
-handling, and OpenCode event routing are kept in separate modules. The package
-root continues to expose only the default OpenCode plugin entrypoint.
+The npm plugin runs from the modular source in `src`. Configuration, structured
+logging, conversation feedback, HTTP transport, SSE consumption, event
+publishing, permission command handling, and OpenCode event routing are kept in
+separate modules. The package root continues to expose only the default OpenCode
+plugin entrypoint.
 
 The legacy side-loaded installer still deploys one dependency-free file. Build
 that generated artifact before running the installer directly from a source