@zackbart/connecta 0.19.0 → 0.20.0

package/documentation/upgrading.md

@@ -57,7 +57,7 @@ exist so far:
 | --- | --- | --- |
 | **pre-template** | before 0.10.2 | no `connecta init` existed; hand-written, or copied from the retired `examples/node` |
 | **A** | 0.10.2 – 0.15.1 | `.env.example`, `.gitignore`, `AGENTS.md`, `CLAUDE.md`, `README.md`, `package.json`, `src/index.ts`, `tsconfig.json` |
-| **B** | 0.16.0 – 0.19.0 | adds `.dockerignore`, `Dockerfile`, `docker-compose.yml`, and `src/file-activity.ts`; `src/index.ts` grows the four commented operator blocks; `.env.example` ships `CONNECTA_TOKEN=` empty |
+| **B** | 0.16.0 – 0.20.0 | adds `.dockerignore`, `Dockerfile`, `docker-compose.yml`, and `src/file-activity.ts`; `src/index.ts` grows the four commented operator blocks; `.env.example` ships `CONNECTA_TOKEN=` empty |
 
 Generation A is a decade in template years and identifying it precisely does
 not matter, because you are about to reconstruct it exactly rather than guess
@@ -106,7 +106,7 @@ know what to preserve, once to know what to re-verify at the end.
 ### Bump the pin and install
 
 ```sh
-npm pkg set dependencies.@zackbart/connecta=0.19.0
+npm pkg set dependencies.@zackbart/connecta=0.20.0
 npm install
 ```
 
@@ -130,7 +130,7 @@ Generate the *current* template beside the base you already made, into the same
 `$SCRATCH`:
 
 ```sh
-(cd "$SCRATCH" && npx @zackbart/connecta@0.19.0 init current)
+(cd "$SCRATCH" && npx @zackbart/connecta@0.20.0 init current)
 ```
 
 You now have a three-way merge with a real base: `$SCRATCH/base` is what this
@@ -186,7 +186,7 @@ A deployment older than 0.10.2 has no base to diff against. Do not try to
 manufacture one. Instead:
 
 1. `SCRATCH=$(mktemp -d)`, then
-   `(cd "$SCRATCH" && npx @zackbart/connecta@0.19.0 init current)` — there is no
+   `(cd "$SCRATCH" && npx @zackbart/connecta@0.20.0 init current)` — there is no
    `base` leg here, only the current template to read from.
 2. Copy `$SCRATCH/current` into the deployment file by file, **skipping
    `src/index.ts`**.
@@ -207,6 +207,30 @@ first, so cross them bottom-up: start at the oldest one still above this
 deployment's pin and work back up the page, because each boundary assumes the
 older ones are already done.
 
+### 0.19.0 → 0.20.0
+
+Three intake paths become deliberately strict. None changes storage, the two
+deployment shapes, or the exact seven-tool MCP surface.
+
+- `createConnecta` now rejects every unknown own configuration property by its
+  complete path. Remove typos and options retired before 0.19, including the
+  top-level `toolkits`, `credentialHealth`, `surface`, and `maxResultBytes`,
+  plus `credentials.health` and `calls.maxBatchResultBytes`. Connector, auth,
+  storage, activity-store, logger, deployment-metadata, and executor
+  implementations remain open objects; their implementation-specific fields
+  are not configuration typos.
+- `call_tool` and `call_destructive_tool` no longer accept `fields`. Put
+  projection in one `execute_code` program. For a legitimate oversized direct
+  read, call without `fields` and follow the returned `get_result` action; that
+  paging path remains part of the seven-tool surface.
+- `connecta.ui` accepts one HTML string and is display-only. Remove its second
+  read-binding argument and any page calls to `connecta.read`. Fetch and shape
+  data in the program before rendering, then return the same compact summary
+  the view initially displays. Views cannot call any Connecta tool.
+
+The Node template layout remains generation B. Reconcile it as usual after the
+version bump; no new deployment file or environment variable is required.
+
 ### 0.18.3 → 0.19.0
 
 Nothing changes for a deployment. Bump the version and reconcile the template
@@ -451,9 +475,11 @@ built-in routes miss, so it can add a route and never shadow one
 
 ### Removed options that throw
 
-These fail at construction with their migration named rather than falling back
-to a default, because silently ignoring a removed option is how a deployment
-ends up running a policy its config file says it has:
+These fail at construction rather than falling back to a default, because
+silently ignoring a removed option is how a deployment runs a policy its config
+file says it has. Releases through 0.19 name the migration in the error. Version
+0.20's strict configuration boundary names the unknown path; this table remains
+the migration map:
 
 | Option | Removed in | Do |
 | --- | --- | --- |
@@ -461,7 +487,7 @@ ends up running a policy its config file says it has:
 | `credentials.health`, `credentialHealth` | 0.8.1 (#179) | delete; credentials fail at use |
 | `surface` | 0.11.0 (#273) | delete; there is one seven-tool surface |
 | `calls.maxBatchResultBytes` | 0.11.0 (#273) | delete; program batching is bounded by `execute_code`'s own limits |
-| flat v0.6 config paths | 0.7.0 | move into their groups — one complete migration error lists them ([operations](./operations.md#configuration)) |
+| flat v0.6 config paths | 0.7.0 | move into their groups ([operations](./operations.md#configuration)) |
 
 ## Verify
 

package/ethos.md

@@ -78,7 +78,7 @@ CHANGELOG, not here.
 | MRTR / `input_required` passthrough | gated | relayable statelessly; no host or downstream emits it yet ([#176](https://github.com/zackbart/connecta/issues/176)) |
 | Downstream `ttlMs` cache hints | gated | needs refresh-churn evidence ([#206](https://github.com/zackbart/connecta/issues/206)) |
 | Downstream MCP Apps template passthrough | gated | needs a downstream that ships one ([#266](https://github.com/zackbart/connecta/issues/266)) |
-| View-initiated mutation calls from program UI | gated | a click is not approval ([#287](https://github.com/zackbart/connecta/issues/287)) |
+| Program UI tool calls | removed | the read bridge added a second contract without improving agent data retrieval; views are display-only again ([#287](https://github.com/zackbart/connecta/issues/287), [#484](https://github.com/zackbart/connecta/issues/484)) |
 
 ## Invariants
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zackbart/connecta",
-  "version": "0.19.0",
+  "version": "0.20.0",
   "type": "module",
   "sideEffects": false,
   "description": "One MCP to rule them all — a single MCP endpoint aggregating many downstream connectors behind a code-first surface of seven meta-tools.",

package/templates/node/package.json

@@ -15,7 +15,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@zackbart/connecta": "0.19.0",
+    "@zackbart/connecta": "0.20.0",
     "quickjs-emscripten": "0.32.0"
   },
   "devDependencies": {