@pellux/goodvibes-agent 1.5.6 → 1.5.8

package/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 Product-facing release notes for GoodVibes Agent.
 
+## 1.5.8 - 2026-07-06
+
+- The `memory` CLI command (`goodvibes-agent memory ...`) now writes to the same shared cross-surface memory store that the runtime, the terminal UI, and the SDK already read and write. Previously the CLI opened its own private database, so a memory added from the CLI was invisible everywhere else; a memory added from the CLI is now visible in the Agent runtime, the TUI, and the SDK, and vice versa.
+- Memory records written by older CLI versions are not lost: the runtime's existing startup memory merge already reads from the exact path the old CLI wrote to, so those older records are folded into the shared store automatically the next time the runtime starts. No manual migration step is needed.
+- Documentation and code-comment hygiene: internal planning shorthand was replaced with plain language in comments, test names, and past changelog entries. No behavior change.
+
+## 1.5.7 - 2026-07-06
+
+- v1.5.7 is a patch on the 1.5 line that completes the platform-SDK adoption started in 1.5.6. The fullscreen Agent workspace, Agent-local behavior, isolated Agent Knowledge, connected-host operator integration, and explicit side-effect boundaries all stay in force; the bundled 1.0.0 GoodVibes platform SDK is unchanged.
+- Adopted the platform's shared credential-status read. When the Agent acts as a client of a connected GoodVibes host, it now reads credential *status* — whether each shared-store credential is configured and usable — over the daemon's `credentials.get` route, and renders it honestly: a host with no shared credential store, an older host that does not serve the route yet, or an unreachable host all report a plain "status unavailable" reason. It never shows a fabricated "configured" and never carries a secret value over the wire. Secret *resolution* for provider auth is unchanged and stays local; API keys remain environment-only and are never persisted.
+- Completed the memory-unification boot follow-ups. At startup the Agent now folds any legacy per-surface memory into the single cross-surface store and shows the fold report (nothing is silently dropped), migrates existing VIBE.md personality files into durable persona records exactly once — guarded by a persisted marker so the same file is never re-imported into near-duplicate records — and builds the VIBE prompt as a projection of those persona records. The projection preserves the precedence rule verbatim: these vibe instructions are followed only when they do not conflict with explicit user instructions, safety policy, tool contracts, confirmation requirements, or secret-handling rules.
+- No change to your conversations, skills, routines, or operator confirmation gates beyond the visibility and memory adoption above.
+
 ## 1.5.6 - 2026-07-06
 
 - v1.5.6 is a patch on the 1.5 line. The fullscreen Agent workspace, Agent-local behavior, isolated Agent Knowledge, connected-host operator integration, and explicit side-effect boundaries all stay in force; this release picks up the 1.0.0 GoodVibes platform SDK.

package/README.md

@@ -1,7 +1,7 @@
 # GoodVibes Agent
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
-[![Version: 1.5.3](https://img.shields.io/badge/version-1.5.6-blue.svg)](#install)
+[![Version: 1.5.3](https://img.shields.io/badge/version-1.5.8-blue.svg)](#install)
 
 GoodVibes Agent is the installable autonomous operator assistant for GoodVibes. It keeps the existing terminal renderer and workspace bones, but the product goal is different from a vibecoding harness: the user should experience one assistant that can chat, plan, remember, research, schedule, send, generate, run visible agents, and operate the GoodVibes daemon contract with clear confirmation gates.