@tealbrick/kit 0.1.2 → 0.1.3

package/BOOTSTRAP.md

@@ -1,11 +1,13 @@
+> Eve 0.58.1 is the approved pinned baseline. Suite 0.1.3 is prepared but not yet published.
+
 # Deployment guide: Eve agent + Teal Brick kit
 
 This guide installs the seven implemented packages through one kit and activates
-only the capabilities you select. The supported harness line is **Eve 0.56.x**;
-**0.56.0** and **AI SDK 7.0.93** are the current tested versions. Use Node **24**.
+only the capabilities you select. The supported harness line is **Eve 0.58.x**;
+**0.58.1** and **AI SDK 7.0.105** are the current tested versions. Use Node **24**.
 
-**Release status:** `@tealbrick/kit@0.1.2` is the Eve 0.56 compatibility release of the
-complete suite. Use the npm installation in step 3. Do not substitute an unrelated unscoped `tealbrick` package.
+**Release status:** `@tealbrick/kit@0.1.3` is an unpublished Eve 0.58 compatibility candidate for the
+complete suite. The npm installation in step 3 applies after publication. Do not substitute an unrelated unscoped `tealbrick` package.
 
 ## What installs what
 
@@ -17,12 +19,12 @@ Eve runs the agent and needs its own working primary-model authentication.
 For a fresh machine, the sequence is:
 
 1. Install Node 24 and npm.
-2. Create an Eve 0.56.0 project and configure its primary model credentials.
-3. Install `@tealbrick/kit@0.1.2` inside that project.
+2. Create an Eve 0.58.1 project and configure its primary model credentials.
+3. Install `@tealbrick/kit@0.1.3` inside that project.
 4. Run `tealbrick setup` to sign in, select capabilities and register the card.
 5. Build and start Eve, then check a real chat from desktop.
 
-For an **existing Eve 0.56.0 project**, start at step 3 from its project directory.
+For an **existing Eve 0.58.1 project**, start at step 3 from its project directory.
 Do not run `eve init` over an existing agent. Preserve its model configuration and
 review any existing Eve channel before setup, as explained under Portal below.
 
@@ -45,7 +47,7 @@ Nucbox/Fedora N150. This package guide does not provision a VM or install AVMM.
 Choose an unused project directory, outside any existing live agent:
 
 ```bash
-npx --yes eve@0.56.0 init tealbrick-agent --model openai/gpt-5.6-terra
+npx --yes eve@0.58.1 init tealbrick-agent --model openai/gpt-5.6-terra
 ```
 
 Finish scaffolding and return to the terminal before continuing. If Eve starts
@@ -53,12 +55,12 @@ Finish scaffolding and return to the terminal before continuing. If Eve starts
 
 ```bash
 cd tealbrick-agent
-npm install --save-exact eve@0.56.0 ai@7.0.93
+npm install --save-exact eve@0.58.1 ai@7.0.105
 ```
 
 Keep `package-lock.json` under version control.
 The exact Eve pin is intentional: the compatibility workflow validates patches
-before advancing it and will not cross into 0.57 automatically.
+before advancing it and will not cross into 0.59 automatically.
 
 The example model uses the Vercel AI Gateway. To supply its key for this terminal
 without putting the key in shell history, in Bash run:
@@ -80,7 +82,7 @@ Run this inside the Eve project created in step 2 (or your existing compatible
 project), not in an empty directory or as a global install:
 
 ```bash
-npm install --save-exact @tealbrick/kit@0.1.2
+npm install --save-exact @tealbrick/kit@0.1.3
 ```
 
 This installs Portal, AVM, Voice, Vision, Deliver and the shared provider transport

package/README.md

@@ -1,19 +1,21 @@
+> Eve 0.58.1 is the approved pinned baseline. Suite 0.1.3 is prepared but not yet published.
+
 # @tealbrick/kit
 
 One installation, explicitly selected capabilities. The kit includes the currently
 implemented Portal, Voice, Vision, Deliver and AVM packages. Dependencies are code
 availability, not agent permissions. Nothing is mounted by installing the kit.
 
-Install inside an existing Eve 0.56.0 project:
+Install inside an existing Eve 0.58.1 project:
 
 ```sh
-npm install --save-exact @tealbrick/kit@0.1.2
+npm install --save-exact @tealbrick/kit@0.1.3
 npx --no-install tealbrick setup
 ```
 
 The suite is published on npm. The kit does not install, create or start Eve.
 Create the Eve project first and configure its primary-model authentication.
-Eve 0.56.0 and Node 24 are the validated host versions; VM provisioning remains
+Eve 0.58.1 and Node 24 are the validated host versions; VM provisioning remains
 host setup. After Teal Brick setup, build and start Eve to make the agent usable.
 
 See [BOOTSTRAP.md](BOOTSTRAP.md) for the complete deployment guide, including fresh-machine and existing-agent paths, provider prompts and verification.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tealbrick/kit",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "type": "module",
   "license": "MIT",
   "description": "Complete Teal Brick package kit with explicit Eve capability activation",
@@ -32,16 +32,16 @@
     "test": "node --test test/*.test.mjs"
   },
   "dependencies": {
-    "@tealbrick/portal": "0.1.2",
-    "@tealbrick/avm": "0.1.2",
-    "@tealbrick/voice": "0.1.2",
-    "@tealbrick/vision": "0.1.2",
-    "@tealbrick/deliver": "0.1.2",
+    "@tealbrick/portal": "0.1.3",
+    "@tealbrick/avm": "0.1.3",
+    "@tealbrick/voice": "0.1.3",
+    "@tealbrick/vision": "0.1.3",
+    "@tealbrick/deliver": "0.1.3",
     "@inquirer/prompts": "8.7.2",
     "zod": "^4.0.0"
   },
   "peerDependencies": {
-    "eve": ">=0.56.0 <0.57.0"
+    "eve": ">=0.58.1 <0.59.0"
   },
   "peerDependenciesMeta": {
     "eve": {