backeer-opencode 0.1.1 → 0.1.3

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to `backeer-opencode` are documented here.
 
+## 0.1.3 - 2026-09-01
+
+- Split configuration, logging, HTTP, SSE, event publishing, and permission
+  command handling into focused source modules.
+- Keep the npm plugin entrypoint backward-compatible with a default export only.
+- Add an esbuild-generated, dependency-free bundle for legacy side-loaded
+  installations.
+
+## 0.1.2 - 2026-09-01
+
+- Replace raw HTTP log lines with compact Backeer console status messages.
+- Add restrained TTY colors with `NO_COLOR` support.
+- Suppress repeated connection errors for 30 seconds.
+- Add `BACKEER_LOG_LEVEL` and the `logLevel` plugin option.
+- Keep technical HTTP and error details in debug mode only.
+
 ## 0.1.1 - 2026-09-01
 
 - Add `backeer-opencode configure` for hidden interactive token entry.

package/README.md

@@ -109,6 +109,7 @@ 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_LOG_LEVEL` | `info` (default), `error`, `debug`, or `silent` |
 
 For npm installations, non-secret options can also be supplied through the
 OpenCode plugin tuple syntax:
@@ -128,8 +129,25 @@ OpenCode plugin tuple syntax:
 }
 ```
 
-Supported options are `origin`, `tokenFile`, `permissions`, `questions`, and
-`todos`. The token itself is deliberately not a plugin option.
+Supported options are `origin`, `tokenFile`, `permissions`, `questions`,
+`todos`, and `logLevel`. The token itself is deliberately not a plugin option.
+
+## Console feedback
+
+The plugin writes compact, single-line status messages instead of raw HTTP logs:
+
+```text
+◆ Backeer  Permission request sent
+◆ Backeer  Question sent
+◆ Backeer  Todo completion sent
+✓ Backeer  Decision applied: Always allow
+! Backeer  Connection interrupted — retrying
+```
+
+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.
 
 ## Events and decisions
 
@@ -156,6 +174,26 @@ npm run pack:check
 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 legacy side-loaded installer still deploys one dependency-free file. Build
+that generated artifact before running the installer directly from a source
+checkout:
+
+```sh
+npm install
+npm run build
+node bin/backeer-opencode.js
+```
+
+`npm test`, `npm pack`, and `npm publish` build the side-loaded artifact
+automatically. Do not edit `dist/backeer-permission.js` by hand.
+
 ## Publishing
 
 Maintainers can publish a release after authenticating the `Backeer` npm

package/bin/backeer-opencode.js

@@ -173,7 +173,7 @@ const configDirectory = resolve(arguments_.configDir ?? defaultConfigDirectory()
 const pluginDirectory = join(configDirectory, "plugins")
 const secretPath = join(configDirectory, "secrets", "backeer-ingest-token")
 const packageDirectory = resolve(dirname(fileURLToPath(import.meta.url)), "..")
-const sourcePath = join(packageDirectory, "src", "index.js")
+const sourcePath = join(packageDirectory, "dist", "backeer-permission.js")
 // Keep the legacy filename so upgrading an existing Backeer installation
 // replaces it instead of loading two copies of the same plugin.
 const installedPath = join(pluginDirectory, "backeer-permission.js")