@tealbrick/kit 0.1.0 → 0.1.2

package/BOOTSTRAP.md

@@ -1,12 +1,30 @@
-# Bootstrap an Eve agent with Teal Brick
+# 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.55.x**;
-**0.55.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.56.x**;
+**0.56.0** and **AI SDK 7.0.93** are the current tested versions. Use Node **24**.
 
-**Release status:** the npm installation in step 3 becomes available once
-`@tealbrick/kit@0.1.0` is published. Until then, use the local-tarball alternative
-below. Do not substitute an unrelated unscoped `tealbrick` npm package.
+**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.
+
+## What installs what
+
+**The Teal Brick kit does not create, install or start an Eve agent.** Create the
+Eve project first, then install the kit inside it. The kit supplies Teal Brick
+capabilities; setup signs you into Portal and registers the agent's workspace card.
+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.
+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.
+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.
 
 ## 1. Install Node and npm
 
@@ -27,7 +45,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.55.0 init tealbrick-agent --model openai/gpt-5.6-terra
+npx --yes eve@0.56.0 init tealbrick-agent --model openai/gpt-5.6-terra
 ```
 
 Finish scaffolding and return to the terminal before continuing. If Eve starts
@@ -35,12 +53,12 @@ Finish scaffolding and return to the terminal before continuing. If Eve starts
 
 ```bash
 cd tealbrick-agent
-npm install --save-exact eve@0.55.0 ai@7.0.93
+npm install --save-exact eve@0.56.0 ai@7.0.93
 ```
 
 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.56 automatically.
+before advancing it and will not cross into 0.57 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:
@@ -58,18 +76,21 @@ Never copy a host's provider login files into a worker to make this step work.
 
 ## 3. Install the complete kit
 
-**After npm publication:**
+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.0
+npm install --save-exact @tealbrick/kit@0.1.2
 ```
 
 This installs Portal, AVM, Voice, Vision, Deliver and the shared provider transport
 as dependencies. You do not install or select provider transport separately.
 Installation alone exposes no Teal Brick tools or routes.
 
-If the package is not yet available, perform the tarball installation below, then
-continue with step 4. An npm 404 is not a reason to install a different package.
+This command does not scaffold Eve, configure its primary model or start a server.
+
+If npm reports a 404 immediately after release, wait for registry propagation
+and retry. Do not install a similarly named unscoped package.
 
 ## 4. Run Teal Brick setup
 
@@ -172,6 +193,8 @@ AVM package README; workspace labels do not replace authenticated identities.
 
 ## 5. Check and run
 
+Setup registration does not start Eve. From the same project directory, run:
+
 ```bash
 npx --no-install tealbrick status
 npx --no-install eve info --json
@@ -220,33 +243,3 @@ Restart the running Eve process after the rebuild. Deselecting a capability remo
 its kit-owned mounts. Setup refuses to overwrite hand-edited mounts. Saved settings
 and optional local secrets live under ignored `.tealbrick/`; secrets are not embedded
 in generated source. Disabling a capability does not revoke or delete its credentials.
-
-## Local-tarball installation before publication
-
-You need read access to the private package repository. On a development/build
-machine with Node 24:
-
-```bash
-git clone https://github.com/Doppelabs/tealbrick-packages.git
-cd tealbrick-packages
-npm ci --ignore-scripts
-npm run compatibility:validate
-```
-
-This produces verified `.tgz` files under `artifacts/packages/`. Copy all seven
-files together to the deployment account on Nucbox. From the fresh Eve project
-created in step 2, use the **absolute path** to that tarball directory:
-
-```bash
-TEALBRICK_TARBALLS=/absolute/path/to/tarballs
-for package in provider-transport portal avm voice vision deliver; do
-  npm pkg set "overrides.@tealbrick/$package=file:$TEALBRICK_TARBALLS/tealbrick-$package-0.1.0.tgz"
-done
-npm install --save-exact "$TEALBRICK_TARBALLS/tealbrick-kit-0.1.0.tgz"
-npx --no-install tealbrick setup
-```
-
-The overrides prevent npm from looking up unpublished internal dependencies.
-Keep the tarballs available while using these local overrides. When migrating to
-the public npm release, remove only these six Teal Brick override entries and
-replace the kit's file dependency with `@tealbrick/kit@0.1.0`, then run `npm install`.

package/README.md

@@ -4,18 +4,19 @@ One installation, explicitly selected capabilities. The kit includes the current
 implemented Portal, Voice, Vision, Deliver and AVM packages. Dependencies are code
 availability, not agent permissions. Nothing is mounted by installing the kit.
 
-Once published, the consumer workflow is:
+Install inside an existing Eve 0.56.0 project:
 
 ```sh
-npm install @tealbrick/kit
+npm install --save-exact @tealbrick/kit@0.1.2
 npx --no-install tealbrick setup
 ```
 
-The package is currently local/unpublished. Install the locally packed suite
-artifacts together until the npm scope is published. Eve 0.55.0 and Node 24 are the
-validated host versions; VM provisioning and Eve installation remain host 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
+host setup. After Teal Brick setup, build and start Eve to make the agent usable.
 
-See [BOOTSTRAP.md](BOOTSTRAP.md) for the complete first-run guide, provider prompts, verification and pre-publication tarball installation.
+See [BOOTSTRAP.md](BOOTSTRAP.md) for the complete deployment guide, including fresh-machine and existing-agent paths, provider prompts and verification.
 
 ## Activation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tealbrick/kit",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "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.0",
-    "@tealbrick/avm": "0.1.0",
-    "@tealbrick/voice": "0.1.0",
-    "@tealbrick/vision": "0.1.0",
-    "@tealbrick/deliver": "0.1.0",
+    "@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",
     "@inquirer/prompts": "8.7.2",
     "zod": "^4.0.0"
   },
   "peerDependencies": {
-    "eve": ">=0.55.0 <0.56.0"
+    "eve": ">=0.56.0 <0.57.0"
   },
   "peerDependenciesMeta": {
     "eve": {
@@ -55,10 +55,5 @@
   "publishConfig": {
     "access": "public",
     "registry": "https://registry.npmjs.org"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/Doppelabs/tealbrick-packages.git",
-    "directory": "packages/kit"
   }
 }