@cabane/companion 0.5.0 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -76,7 +76,7 @@ Lifecycle — **register / deactivate / remove** a device, and **assign agents**
76
76
  cabane-companion start --daemon
77
77
  # Cabane Companion started in the background (pid 51234).
78
78
  # → Dashboard: http://127.0.0.1:7474
79
- # Logs: ~/.cabane/bridge.log
79
+ # Logs: ~/.cabane/companion.log
80
80
  # Status: cabane-companion status
81
81
  # Stop: cabane-companion stop
82
82
  ```
@@ -191,7 +191,7 @@ Everything else about a Companion-run agent is unchanged — same assignment, sa
191
191
  ├── outbox/<workspace_id>/ # durable per-agent commit queue — a reply survives a transient API outage
192
192
  ├── runtime.json # written while `start` runs: dashboard url + pid (swept on exit)
193
193
  ├── transcripts/ # one JSONL file per dispatch — the full agent turn (see below)
194
- └── bridge.log # rolling JSON-lines log
194
+ └── companion.log # rolling JSON-lines log
195
195
  ```
196
196
 
197
197
  No SQLite, no embedded DB. Cabane is the source of truth for which agents to run and how they're configured.