@brokkai/brokk-town-linux-arm64 0.1.0 → 0.1.1

package/BUILD.json

@@ -1 +1 @@
-{"commit": "8006469e2b861513f469c4b481b551cc22ce1594", "tag": "v0.1.0", "target": "linux-arm64"}
+{"commit": "f75803f0b79af78c32e55de064f1ee589714b9e3", "tag": "v0.1.1", "target": "linux-arm64"}

package/README.md

@@ -70,10 +70,11 @@ a commit shipped. Columns, prompts and transitions are not programmable.
 ## Installation and releases
 
 Source is published at [BrokkAi/brokk-town](https://github.com/BrokkAi/brokk-town).
-The bootstrap prerelease is available on npm:
+The stable release is available from [GitHub](https://github.com/BrokkAi/brokk-town/releases/tag/v0.1.0)
+and npm:
 
 ```sh
-npm install -g @brokkai/brokk-town@next
+npm install -g @brokkai/brokk-town
 ```
 
 You can also build from source as above or install the current branch:
@@ -84,8 +85,8 @@ go install github.com/BrokkAi/brokk-town/cmd/bt@master
 
 The release pipeline builds checksum-verified Linux/macOS archives for amd64 and
 arm64, plus `@brokkai/brokk-town` and four native npm packages. All packages carry
-the project license, attribution, and complete third-party notices. The initial `0.1.0-rc.1` npm bootstrap is published. After the first stable GitHub
-release, the supported installer commands are:
+the project license, attribution, and complete third-party notices. The supported
+installer commands are:
 
 ```sh
 sh install.sh                       # From a checkout; defaults to ~/.local/bin
@@ -100,24 +101,13 @@ for first-release setup, access checks, publishing, and recovery.
 
 ## Connect real repositories
 
-Install and authenticate `git`, GitHub CLI (`gh`), your chosen coding agent, and
-Brokk bot releases that advertise **Town Worker Protocol v1**. Town no longer
-compiles the bots into `bt`; each dispatch starts the installed `bbb`, `bfb`,
-`bib`, `brv`, or `brb` executable from the service PATH and communicates over a
-private Unix socket. Run `<command> version` and `<command> worker --help` to
-confirm a compatible release.
+Install and authenticate `git`, GitHub CLI (`gh`), Node.js/npm, and your chosen
+coding agent. Town does not require a separate bot installation: each dispatch
+uses `npx --yes` with an exact compatible release of bug-bot, feature-bot,
+issue-bot, review-bot, or release-bot, then communicates with it over a private
+Unix socket. Town never selects an ambient or floating bot version.
 
-Install the released Worker Protocol v1 npm distributions:
-
-```sh
-npm install -g @brokkai/bug-bot@0.3.1 \
-  @brokkai/feature-bot@0.1.1 \
-  @brokkai/issue-bot@0.5.1 \
-  @brokkai/review-bot@0.2.1 \
-  @brokkai/release-bot@0.5.1
-```
-
-Checksum-verified native bot releases are equally supported. The worker uses
+The worker uses
 standard-library HTTP/JSON, negotiates protocol and capabilities before work,
 streams contiguous progress events, and returns explicit typed results. It never
 requires Town to parse bot-private state. See
@@ -128,11 +118,10 @@ requires Node.js and `npx`. Choose another harness in Settings as described belo
 Git must already be able to clone and push your GitHub repositories; Town uses
 the current Git/gh credentials.
 
-Bot executables can be replaced while the Town service remains running. The next
-dispatch resolves PATH again and negotiates with the new service. An active
-dispatch pins its resolved path, executable hash, and reported version, then
-rechecks all three; a mid-dispatch replacement fails uncertainly and is resolved
-through durable bot state and GitHub reconciliation.
+Town resolves and hashes the `npx` executable for every dispatch and rechecks it
+and the pinned bot's reported version afterward. A mid-dispatch executable or
+version change fails uncertainly and is resolved through durable bot state and
+GitHub reconciliation.
 
 ```sh
 ./bin/bt serve --repo BrokkAi/my-project

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.1.0",
+  "version": "0.1.1",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",