docs(oss): log the Marketplace hot-reload notification that never reaches the sidecar (UF-038)

This commit is contained in:
shumeiko.it
2026-10-24 17:39:20 +02:00
parent 7dac06706e
commit 2c376f21cf

View File

@@ -66,6 +66,7 @@ Baseline: commit `b20b138` of `git.os-dev.tech/oleg.m/waggle-os`.
| UF-035 | Timeline search and the chat recall toast send the workspace id as the search scope | Fixed | Web UI, memory, privacy |
| UF-036 | The web client reads "important" and "temporary" memories as normal importance | Fixed | Web UI, memory |
| UF-037 | Restore overwrites database files the running sidecar holds open | Open | Sidecar, backup |
| UF-038 | Marketplace installs never notify the running sidecar | Open | Marketplace, sidecar |
## Entries
@@ -374,3 +375,12 @@ Entries UF-010 to UF-019 come from the UI audit `anti-slop/audit-001-2026-10-14.
- Cause: the restore writes every file of the archive in place (only `marketplace.db` is skipped) without closing the open databases first.
- What we did: nothing yet. In the community edition the same applies to `waggle.db` and the mem0 files in `<dataDir>/memory/`.
- Recommendation: stage the restored files and apply them at the next start, before any database opens, as the data-erase marker does; or close the databases, restore, and restart the sidecar.
### UF-038. Marketplace installs never notify the running sidecar
- Status: Open
- Found: 2026-10-24
- Where: at commit `b20b138`, `packages/marketplace/src/installer.ts:94` (`API_BASE = process.env.WAGGLE_API_URL || 'http://localhost:3000'`) and `notifyServer()` at `:960`, called after skill and plugin installs and uninstalls (`:590`, `:667`, `:764`, `:773`)
- Symptom: after a skill or plugin is installed from the Marketplace, the hot-reload the installer asks for does not happen: the sidecar endpoints it calls (`PUT /api/skills/:name` reloads `agentState.skills`, `POST /api/plugins/install` registers and enables the plugin) never receive the request. Not verified end to end whether another path reloads them before a restart.
- Cause: the installer posts to port 3000, while the sidecar listens on 3333 by default and nothing sets `WAGGLE_API_URL`; the request also carries no session token, which the sidecar requires. The error is swallowed (`// Server not running`).
- What we did: nothing yet.
- Recommendation: when the installer runs inside the sidecar (the Marketplace routes), call the reload logic directly instead of over HTTP; for the standalone CLI, take the port and token from the running sidecar.