@brokkai/brokk-town-linux-arm64 0.2.0 → 0.3.1

package/BUILD.json

@@ -1 +1 @@
-{"commit": "5ded0114ffbfb578c085594166d62b6a4158eed3", "tag": "v0.2.0", "target": "linux-arm64"}
+{"commit": "95bf612db25f0eed0c3954cf8a89238213eea030", "tag": "v0.3.1", "target": "linux-arm64"}

package/README.md

@@ -190,10 +190,13 @@ GitHub reconciliation.
 ./bin/bt tui
 ```
 
-New towns start with the five automation workers **paused**. Repo-bot starts its
-read-only inventory. The town header shows whether the town is paused, awake,
+Town starts and manages the bot libraries internally; the standalone bot CLIs are
+not companion processes. New towns start with Bug Bot, Feature Bot, Issue Bot,
+Review Bot, and Release Bot **paused**. Repo Bot starts its read-only inventory.
+The town header shows whether the town is paused, awake,
 or partly awake, and its button offers the action that changes that state.
-Inspect the town, then start individual workers or choose **Wake the town**.
+Inspect the town, then start individual workers or choose **Wake the town**, which
+enables all five automation workers (except Release Bot under manual merge policy).
 Starting workers authorizes their real work: filing issues,
 creating and repairing PRs, posting reviews, merging under the configured policy,
 and publishing releases. Agents and verification commands run with your local
@@ -359,7 +362,8 @@ New external issues and PRs first wait at Town Hall for a durable Mayoral
 decision. **Admit** sends the work to Issue Bot or Review Bot; **Decline** keeps
 Town from acting on it without changing GitHub. Feature Bot proposals follow the
 same route by default and can be exempted in **Town Settings → External
-contributions**. The browser provides the primary decision UX; scripts may use
+contributions**. A proposal is the town's own work, so declining one also closes
+its issue as not planned; outside issues and PRs are only ignored. The browser provides the primary decision UX; scripts may use
 `bt admit --repo OWNER/REPO --task issue:123` or `bt decline ...`. Offered bot
 upgrades use the same commands with `--task upgrade:feature` (or another bot
 role), plus `bt delay ...` to be asked again in a day.
@@ -371,7 +375,10 @@ result. New commits invalidate review readiness. Uncertain reviews and exhausted
 repair cycles become visible tasks needing attention.
 
 The default merge policy is `bot`: auto-merge eligible Town-created PRs. `manual`
-leaves merging to the operator; `all` also permits eligible external PRs. Town-managed merges require current clean Town evidence, GitHub mergeability, required checks
+leaves every merge to the operator; because the current Release Bot protocol cannot
+limit its authority to publish while forbidding its release-preparation PR merges,
+Town pauses Release Bot and rejects attempts to start or retry it under this policy.
+`all` also permits eligible external PRs. Town-managed merges require current clean Town evidence, GitHub mergeability, required checks
 and approvals. Town uses an expected-head squash merge, without admin bypass.
 Change this at any time under **Town Settings → External contributions**.
 Repositories that require a merge queue or prohibit squash merging need manual
@@ -424,11 +431,22 @@ uncertain proposals before filing. Its verifier receives `FEATURE_COMMIT` and
 `FEATURE_FINDING`; shared verification commands must support the selected bot's
 environment. New and upgraded towns keep feature discovery paused until started.
 
+Town Hall's **Automation outcomes** report separates worker attempts, filed
+findings, submitted implementation PRs, repository-confirmed merges, repair
+rounds, blocked or abandoned work, and verified releases for a selectable
+period. A submitted PR is an artifact rather than an accepted fix. Operators
+can mark each filed finding useful or a false positive only by adding an
+explanation. Records retain task and revision provenance and show elapsed time,
+token usage, and cost as unknown when the worker does not provide them. The CSV
+export includes the repository on every row for comparisons across runs and
+towns.
+
 Private state defaults to `$XDG_STATE_HOME/brokk-town` or
 `~/.local/state/brokk-town`. `--state-dir` selects another directory; `--demo`
 appends `demo`. A single writer lock, atomic snapshots, per-role bot state, and
-private worktrees keep towns separate. Events, logs, and reports have bounded
-recent histories; task/intent history persists. Browser access uses a per-service
+private worktrees keep towns separate. Events, logs, and repo-bot reports have
+bounded recent histories; task, intent, and automation outcome history persists.
+Browser access uses a per-service
 local key in a URL fragment. `connection.json` and state snapshots are mode 0600.
 Private agent commands, environment, and authentication configuration are omitted
 from public configuration snapshots for both town defaults and bot profiles;

package/package.json

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