@pellux/goodvibes-tui 0.19.20 → 0.19.22

package/CHANGELOG.md

@@ -4,6 +4,36 @@ All notable changes to GoodVibes TUI.
 
 ---
 
+## [0.19.22] — 2026-04-21
+
+Hotfix release: regenerates foundation artifacts against SDK 0.22.0 after 0.19.21's release pipeline failed the `foundation artifacts gate` test. No consumer-facing feature changes beyond what 0.19.21 carried.
+
+### Fixed
+- **`docs/foundation-artifacts/operator-contract.json` regenerated against SDK 0.22.0.** The 0.19.21 tag shipped with an artifact stamped `"version": "0.21.36"` while consuming SDK 0.22.0 — the `foundation artifacts gate` release-gates test detected this drift and failed the release workflow on the `Tests` step, blocking the npm publish. 0.19.22 contains the regenerated artifact (one-line version-stamp update) and ships cleanly.
+- **CI: composite `./.github/actions/setup` action** shared across every `ci.yml` and `release.yml` job: pins Bun 1.3.10, restores `~/.bun/install/cache` via `actions/cache@v4`, runs `bun install`. Eliminates ~60 lines of duplicated setup boilerplate and gives every job a warm dep cache.
+
+### Internal
+- Reconciliation sweep against SDK 0.22.0 confirmed no other TUI drift: typecheck clean, architecture check clean, 456/456 test files pass.
+
+---
+
+## [0.19.21] — 2026-04-21
+
+Maintenance release: SDK 0.22.0 bump + README/gitignore hygiene + test-timeout polish. **Did not publish** — the release workflow's foundation-artifacts gate detected stale artifact drift against SDK 0.22.0; see 0.19.22 for the shipped fix. No consumer-facing feature or behavior changes.
+
+### Changed
+- **SDK dep bumped to `@pellux/goodvibes-sdk@0.22.0`.** Picks up the SDK's contract-artifact refresh pipeline, documentation audit, and test-suite cleanup. No TUI code paths change; the bump is source-compatible.
+- **Active-early-development banner** added near the top of `README.md`. Signals that CLI flags, config keys, slash commands, key bindings, daemon routes, and on-disk layouts can change across patch releases pre-1.0; no legacy/compat shims; docs describe current behavior only. 1.0.0 is the stability freeze.
+
+### Fixed
+- Raised timeouts on three flaky edit-tool tests from the default 5 s to 7.5 s (`edit tool > fuzzy matching > matches despite extra whitespace`, `edit tool > batch edits on different files > applies edits to multiple files`, `edit tool > ast_pattern mode > respects occurrence number selector`). These were intermittently tripping on heavily-loaded CI runners despite the underlying operation completing well under 5 s on fast hardware.
+
+### Internal
+- `docs/uat/` added to `.gitignore` and existing UAT reports untracked (kept on disk locally). UAT validation reports are live-daemon smoke results, not canonical documentation.
+- `:memory:` filename added to `.gitignore` — prevents regression of an SQLite-sentinel-as-path test leak.
+
+---
+
 ## [0.19.20] — 2026-04-21
 
 ### Changes

package/README.md

@@ -2,10 +2,12 @@
 
 [![CI](https://github.com/mgd34msu/goodvibes-tui/actions/workflows/ci.yml/badge.svg)](https://github.com/mgd34msu/goodvibes-tui/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-[![Version](https://img.shields.io/badge/version-0.19.20-blue.svg)](https://github.com/mgd34msu/goodvibes-tui)
+[![Version](https://img.shields.io/badge/version-0.19.22-blue.svg)](https://github.com/mgd34msu/goodvibes-tui)
 
 A terminal-native AI coding, operations, automation, knowledge, and integration console with a typed runtime, omnichannel surfaces, structured memory/knowledge, and a raw ANSI renderer.
 
+> ⚠️ **Active early development — pre-1.0.** This project is under active early development. CLI flags, config keys, slash commands, key bindings, daemon routes, and on-disk layouts can and do change quickly — sometimes across patch releases. There are no legacy/compat shims. Documentation always describes the **current** behavior, not historical behavior. When 1.0.0 ships the project freezes to enterprise-grade stability guarantees (semver, deprecation windows, migration guides). Until then: pin exact versions and read `CHANGELOG.md` before upgrading.
+
 <!-- screenshot -->
 
 ---

package/docs/foundation-artifacts/operator-contract.json

@@ -3,7 +3,7 @@
   "product": {
     "id": "goodvibes",
     "surface": "operator",
-    "version": "0.21.36"
+    "version": "0.22.0"
   },
   "auth": {
     "modes": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pellux/goodvibes-tui",
-  "version": "0.19.20",
+  "version": "0.19.22",
   "description": "Terminal-native GoodVibes product for coding, operations, automation, knowledge, channels, and daemon-backed control-plane workflows.",
   "type": "module",
   "main": "src/main.ts",
@@ -90,7 +90,7 @@
     "@anthropic-ai/vertex-sdk": "^0.16.0",
     "@ast-grep/napi": "^0.42.0",
     "@aws/bedrock-token-generator": "^1.1.0",
-    "@pellux/goodvibes-sdk": "0.21.36",
+    "@pellux/goodvibes-sdk": "0.22.0",
     "bash-language-server": "^5.6.0",
     "fuse.js": "^7.1.0",
     "graphql": "^16.13.2",

package/src/version.ts

@@ -6,7 +6,7 @@ import { join } from 'node:path';
 // The prebuild script updates the fallback value before compilation.
 // Uses import.meta.dir (Bun) to locate package.json relative to this file,
 // which is correct regardless of the process working directory.
-let _version = '0.19.20';
+let _version = '0.19.22';
 try {
   const pkg = JSON.parse(readFileSync(join(import.meta.dir, '..', 'package.json'), 'utf-8'));
   _version = pkg.version ?? _version;