@tealbrick/kit 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/BOOTSTRAP.md CHANGED
@@ -1,12 +1,31 @@
1
- # Bootstrap an Eve agent with Teal Brick
1
+ # Deployment guide: Eve agent + Teal Brick kit
2
2
 
3
3
  This guide installs the seven implemented packages through one kit and activates
4
- only the capabilities you select. The supported harness line is **Eve 0.55.x**;
5
- **0.55.0** and **AI SDK 7.0.93** are the current tested versions. Use Node **24**.
4
+ only the capabilities you select. The supported harness line is **Eve 0.56.x**;
5
+ **0.56.0** and **AI SDK 7.0.93** are the current tested versions. Use Node **24**.
6
6
 
7
- **Release status:** `@tealbrick/kit@0.1.1` is the metadata-correction release of the
7
+ **Release status:** `@tealbrick/kit@0.1.2` is the Eve 0.56 compatibility release of the
8
8
  complete suite. Use the npm installation in step 3. Do not substitute an unrelated unscoped `tealbrick` package.
9
9
 
10
+ ## What installs what
11
+
12
+ **The Teal Brick kit does not create, install or start an Eve agent.** Create the
13
+ Eve project first, then install the kit inside it. The kit supplies Teal Brick
14
+ capabilities; setup signs you into Portal and registers the agent's workspace card.
15
+ Eve runs the agent and needs its own working primary-model authentication.
16
+
17
+ For a fresh machine, the sequence is:
18
+
19
+ 1. Install Node 24 and npm.
20
+ 2. Create an Eve 0.56.0 project and configure its primary model credentials.
21
+ 3. Install `@tealbrick/kit@0.1.2` inside that project.
22
+ 4. Run `tealbrick setup` to sign in, select capabilities and register the card.
23
+ 5. Build and start Eve, then check a real chat from desktop.
24
+
25
+ For an **existing Eve 0.56.0 project**, start at step 3 from its project directory.
26
+ Do not run `eve init` over an existing agent. Preserve its model configuration and
27
+ review any existing Eve channel before setup, as explained under Portal below.
28
+
10
29
  ## 1. Install Node and npm
11
30
 
12
31
  Install Node 24 using the [official Node.js installer or installation instructions](https://nodejs.org/en/download).
@@ -26,7 +45,7 @@ Nucbox/Fedora N150. This package guide does not provision a VM or install AVMM.
26
45
  Choose an unused project directory, outside any existing live agent:
27
46
 
28
47
  ```bash
29
- npx --yes eve@0.55.0 init tealbrick-agent --model openai/gpt-5.6-terra
48
+ npx --yes eve@0.56.0 init tealbrick-agent --model openai/gpt-5.6-terra
30
49
  ```
31
50
 
32
51
  Finish scaffolding and return to the terminal before continuing. If Eve starts
@@ -34,12 +53,12 @@ Finish scaffolding and return to the terminal before continuing. If Eve starts
34
53
 
35
54
  ```bash
36
55
  cd tealbrick-agent
37
- npm install --save-exact eve@0.55.0 ai@7.0.93
56
+ npm install --save-exact eve@0.56.0 ai@7.0.93
38
57
  ```
39
58
 
40
59
  Keep `package-lock.json` under version control.
41
60
  The exact Eve pin is intentional: the compatibility workflow validates patches
42
- before advancing it and will not cross into 0.56 automatically.
61
+ before advancing it and will not cross into 0.57 automatically.
43
62
 
44
63
  The example model uses the Vercel AI Gateway. To supply its key for this terminal
45
64
  without putting the key in shell history, in Bash run:
@@ -57,16 +76,19 @@ Never copy a host's provider login files into a worker to make this step work.
57
76
 
58
77
  ## 3. Install the complete kit
59
78
 
60
- **Published installation:**
79
+ Run this inside the Eve project created in step 2 (or your existing compatible
80
+ project), not in an empty directory or as a global install:
61
81
 
62
82
  ```bash
63
- npm install --save-exact @tealbrick/kit@0.1.1
83
+ npm install --save-exact @tealbrick/kit@0.1.2
64
84
  ```
65
85
 
66
86
  This installs Portal, AVM, Voice, Vision, Deliver and the shared provider transport
67
87
  as dependencies. You do not install or select provider transport separately.
68
88
  Installation alone exposes no Teal Brick tools or routes.
69
89
 
90
+ This command does not scaffold Eve, configure its primary model or start a server.
91
+
70
92
  If npm reports a 404 immediately after release, wait for registry propagation
71
93
  and retry. Do not install a similarly named unscoped package.
72
94
 
@@ -171,6 +193,8 @@ AVM package README; workspace labels do not replace authenticated identities.
171
193
 
172
194
  ## 5. Check and run
173
195
 
196
+ Setup registration does not start Eve. From the same project directory, run:
197
+
174
198
  ```bash
175
199
  npx --no-install tealbrick status
176
200
  npx --no-install eve info --json
@@ -219,4 +243,3 @@ Restart the running Eve process after the rebuild. Deselecting a capability remo
219
243
  its kit-owned mounts. Setup refuses to overwrite hand-edited mounts. Saved settings
220
244
  and optional local secrets live under ignored `.tealbrick/`; secrets are not embedded
221
245
  in generated source. Disabling a capability does not revoke or delete its credentials.
222
-
package/README.md CHANGED
@@ -4,18 +4,19 @@ One installation, explicitly selected capabilities. The kit includes the current
4
4
  implemented Portal, Voice, Vision, Deliver and AVM packages. Dependencies are code
5
5
  availability, not agent permissions. Nothing is mounted by installing the kit.
6
6
 
7
- Once published, the consumer workflow is:
7
+ Install inside an existing Eve 0.56.0 project:
8
8
 
9
9
  ```sh
10
- npm install @tealbrick/kit
10
+ npm install --save-exact @tealbrick/kit@0.1.2
11
11
  npx --no-install tealbrick setup
12
12
  ```
13
13
 
14
- The package is currently local/unpublished. Install the locally packed suite
15
- artifacts together until the npm scope is published. Eve 0.55.0 and Node 24 are the
16
- validated host versions; VM provisioning and Eve installation remain host setup.
14
+ The suite is published on npm. The kit does not install, create or start Eve.
15
+ Create the Eve project first and configure its primary-model authentication.
16
+ Eve 0.56.0 and Node 24 are the validated host versions; VM provisioning remains
17
+ host setup. After Teal Brick setup, build and start Eve to make the agent usable.
17
18
 
18
- See [BOOTSTRAP.md](BOOTSTRAP.md) for the complete first-run guide, provider prompts, verification and pre-publication tarball installation.
19
+ See [BOOTSTRAP.md](BOOTSTRAP.md) for the complete deployment guide, including fresh-machine and existing-agent paths, provider prompts and verification.
19
20
 
20
21
  ## Activation
21
22
 
package/dist/cli.js CHANGED
File without changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tealbrick/kit",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "type": "module",
5
5
  "license": "MIT",
6
6
  "description": "Complete Teal Brick package kit with explicit Eve capability activation",
@@ -32,16 +32,16 @@
32
32
  "test": "node --test test/*.test.mjs"
33
33
  },
34
34
  "dependencies": {
35
- "@tealbrick/portal": "0.1.1",
36
- "@tealbrick/avm": "0.1.1",
37
- "@tealbrick/voice": "0.1.1",
38
- "@tealbrick/vision": "0.1.1",
39
- "@tealbrick/deliver": "0.1.1",
35
+ "@tealbrick/portal": "0.1.2",
36
+ "@tealbrick/avm": "0.1.2",
37
+ "@tealbrick/voice": "0.1.2",
38
+ "@tealbrick/vision": "0.1.2",
39
+ "@tealbrick/deliver": "0.1.2",
40
40
  "@inquirer/prompts": "8.7.2",
41
41
  "zod": "^4.0.0"
42
42
  },
43
43
  "peerDependencies": {
44
- "eve": ">=0.55.0 <0.56.0"
44
+ "eve": ">=0.56.0 <0.57.0"
45
45
  },
46
46
  "peerDependenciesMeta": {
47
47
  "eve": {