@brokkai/brokk-town-linux-x64 0.1.1 → 0.2.0

package/BUILD.json

@@ -1 +1 @@
-{"commit": "f75803f0b79af78c32e55de064f1ee589714b9e3", "tag": "v0.1.1", "target": "linux-amd64"}
+{"commit": "5ded0114ffbfb578c085594166d62b6a4158eed3", "tag": "v0.2.0", "target": "linux-amd64"}

package/README.md

@@ -25,13 +25,15 @@ Build with the Go version in `go.mod`:
 
 ```sh
 make build
-./bin/bt serve --demo
+./bin/bt tui --demo
 ```
 
-Open the browser address printed by the service. In another terminal:
+Any `bt` command starts the town service in the background when it is not
+running. Press `q` to leave the terminal panel; the town keeps going. Print the
+browser address with:
 
 ```sh
-./bin/bt tui --demo
+./bin/bt web --demo
 ```
 
 Demo mode uses an isolated state directory and simulated activity in two towns.
@@ -42,9 +44,42 @@ fixtures, with active worker profiles available to inspect. Paper-trail illustra
 a neighboring repository with a failed watchtower. Pause a house to hold its next step.
 
 The browser and TUI attach to the same service. Closing either leaves workers
-running. Stop the foreground service with Ctrl+C; it cancels and waits for workers
-before releasing the state lock. `bt` without a command opens the TUI of an
-already-running service. Use `bt web` to print its browser address again.
+running. `bt` without a command opens the TUI. Use `bt web` to print the browser
+address again; the local access key is persistent, so bookmarks and open tabs
+survive restarts.
+
+### The service keeps itself running
+
+There is nothing to install or remember. The first `bt` command that starts a
+real town also registers the service with your login session: a launchd agent
+on macOS (`~/Library/LaunchAgents/ai.brokk.town.plist`) or a systemd user unit
+on Linux (`~/.config/systemd/user/brokk-town.service`). From then on the town
+restarts after a crash and returns after a reboot without any command, and the
+browser page reloads itself when a new version comes up. The demo town is never
+registered; it starts on demand and stays until stopped.
+
+- `bt service status` shows the service, its registration, and log locations
+  (`logs/serve.log` and `logs/serve.err.log` under the state directory).
+- `bt service stop` stops it until the next `bt` command. `bt service restart`
+  restarts it in place.
+- `bt service off` keeps the service out of your login session; `bt` still
+  starts it on demand, but it will not return by itself after logout or reboot.
+  `bt service on` registers it again.
+- `bt serve` still runs the service in the foreground for development. It
+  refuses to start while another service holds the state directory and names
+  that process.
+
+The registration captures the `PATH` of the shell that created it, so `gh`,
+`git`, `npx`, and your chosen agent are found without a login shell. A
+`--listen` address given to any command is remembered for that town, so a later
+command's default never moves a registered service to another port. On Linux,
+`bt` enables lingering for your user so the town survives logout; if that needs
+administrator approval, it says so. Over SSH on a Mac without a logged-in
+session there is no launchd user domain, so the service runs unregistered.
+
+When you rebuild or upgrade `bt`, the next `bt` command notices that the running
+service is older and restarts it on the new binary. An older `bt` never
+downgrades a running service.
 
 The browser header switches among **Town**, **Board**, and **Compact** without
 restarting. Town keeps the animated houses first-class; Board groups durable work
@@ -70,13 +105,22 @@ 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 stable release is available from [GitHub](https://github.com/BrokkAi/brokk-town/releases/tag/v0.1.0)
+The stable release is available from [GitHub](https://github.com/BrokkAi/brokk-town/releases/tag/v0.1.1)
 and npm:
 
 ```sh
 npm install -g @brokkai/brokk-town
 ```
 
+While the service is running, Town checks npm outside its input and render loops.
+When a newer stable release is available, the browser offers an **Upgrade Town**
+button and the TUI offers `u`. After confirmation, the service installs that exact
+version through the channel it was installed from (npm for the npm package,
+otherwise the checksum-verified release archive over the current binary) and
+restarts itself in place; the browser page reloads when the new version is up.
+Bots that were mid-run keep working through the restart and are reconnected.
+A failed or offline check never interrupts local operation.
+
 You can also build from source as above or install the current branch:
 
 ```sh
@@ -106,11 +150,27 @@ 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.
+Each bot's Settings panel shows its current pin. **Check for bot update** reads
+npm's stable tag, and **Use VERSION** stages that exact version for the Mayor to
+save. The pin changes only for that town and takes effect on the bot's next run;
+capability and reported-version checks still run before any repository work.
+
+Town also checks npm's stable tags on its own, at start and every six hours.
+When a bot has a newer stable release than a town's pin, the town receives a
+Mayoral decision at Town Hall: **Upgrade now** pins the new version for the
+bot's next run, **Delay a day** asks again after 24 hours, and **Decline** keeps
+the current pin until an even newer release is published. The **Update bots
+automatically** town setting (off by default) pins new stable releases as they
+appear instead, including any offer already waiting. A registry outage never
+changes a pin or stops a town.
 
 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
+requires Town to parse bot-private state. Until the worker protocol carries job
+outcomes, Town uses the same pinned issue-bot release's validated public state
+API to import blocked/submitted scheduling metadata and perform explicit retries.
+See
 [docs/WORKER_PROTOCOL.md](docs/WORKER_PROTOCOL.md) for the contract.
 
 Town defaults to the official ACP registry’s `codex-acp` npm distribution, which
@@ -131,8 +191,10 @@ GitHub reconciliation.
 ```
 
 New towns start with the five automation workers **paused**. Repo-bot starts its
-read-only inventory. Inspect the town, then start individual workers or choose
-**Wake the town**. Starting workers authorizes their real work: filing issues,
+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**.
+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
 permissions. Use an isolated account or machine for repositories you don't trust.
@@ -151,6 +213,15 @@ Pause finishes active work and stops scheduling more. Stop also cancels active
 work. Enabled/paused settings survive restarts. A restart resumes enabled workers;
 uncertain external writes retain their saved intent and are reconciled first.
 
+Stopping or restarting the service (Ctrl+C, SIGTERM, `bt service restart`, or
+an in-app upgrade) does not stop the external bots. Each bot process runs detached, and Town commits its handle (PID,
+socket, and exact task) before requesting work. The next `bt serve` reconnects to
+those processes before scheduling anything new. Bots that advertise the `detach`
+capability replay the events Town missed and their results are applied normally.
+Older bots finish on their own, and Town records that attempt as uncertain rather
+than guessing; repo-bot then reconciles whatever landed on GitHub. Only an explicit
+Stop, a town deletion, or the two-hour dispatch deadline ends a bot process.
+
 Capacity is a persisted service setting shared by every town. It reserves only
 non-reporter bot runs; repo-bot, issue publishing, and prompt-free model choice
 discovery stay outside the pool. Lowering the limit lets current work finish and
@@ -284,6 +355,15 @@ Animation never initiates a GitHub write. Reconnecting does not replay previousl
 seen deliveries. External PRs receive reviews but their branches are left to their
 authors; only locally recorded Town-created branches enter automatic repair.
 
+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
+`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.
+
 A review is bound to the exact base, head, PR description, and discussion snapshot. A suppressed
 duplicate comment is still a finding to check. Complete coverage, explicit
 resolution of every concern, and validation evidence are required for a clean
@@ -293,6 +373,7 @@ 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
 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
 merges for now. GitHub is the final authority at write time.
 
@@ -307,7 +388,8 @@ bot profiles, verification command, and policy, then run:
 
 Configuration is a JSON array for town-only files. Each entry supplies `repo`, optional `branch` and
 `harness`, `agent`, optional `bot_agents`, optional `verify` argument vector,
-`merge_policy`, `poll_seconds`, `report_seconds`, and `max_cycles`. The example
+`merge_policy`, `mayoral_feature_review`, `poll_seconds`, `report_seconds`, and
+`max_cycles`. The example
 lists all required values. To persist global capacity alongside the town list,
 use the object form `{"max_workers": 2, "towns": [...]}`; the legacy array form
 remains accepted. When `serve --config` includes `max_workers`, that value
@@ -351,6 +433,45 @@ 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;
 each bot's effective harness, model, and effort are visible.
+
+### Source funnels
+
+Optional `funnels` make issue intake source-neutral. Each named funnel declares a
+provider, validated location/filter, a local credential reference, explicit
+priority policy, overlap policy, and allowlisted lifecycle mappings. Credential
+references are resolved by adapters at request time; secret values never enter
+Town state, model prompts, events, logs, or public snapshots. Public state shows
+the safe funnel configuration and each normalized item's source identity, URL,
+revision, external state, eligibility, capabilities, priority policy, last sync,
+and typed outcome.
+
+GitHub funnels support query, `selected_issues`, and comma-separated
+`include_labels`/`exclude_labels`. Focused selections are read by issue identity
+instead of relying on search indexing. `working` and `blocked` mappings translate
+the normalized lifecycle into confirmed label changes. Slack is the second real
+adapter: it reads a configured channel through paginated Web API calls and maps
+configured lifecycle actions to reactions plus bounded thread replies. Slack
+tokens are obtained from a private resolver immediately before each request.
+Read-only funnels and empty per-transition mappings stay visibly unsupported.
+
+Funnels also recognize provider-native done signals on inbound reads. A Slack
+message with a present `:white_check_mark:` or `:heavy_check_mark:` reaction is
+normalized as **Done**; a GitHub issue whose state is `closed` is normalized as
+**Closed**. Both remain in the durable inventory with their source provenance,
+but become ineligible and leave the worker queue. A GitHub selector must include
+closed issues (for example `is:issue`, not `is:issue is:open`) if Town is to
+observe that transition. Done is based only on an explicit item state or reaction;
+an incomplete or empty inventory never closes missing work by implication.
+
+Lifecycle mutations use a durable intent before the provider call. A lost
+response remains `uncertain`; reconciliation is read-only and absence of a
+receipt never permits a duplicate label, reaction, comment, or thread reply.
+Incomplete reads, partial discovery, authentication failures, rate limits,
+unsupported actions, and uncertain writes remain distinct outcomes. Funnel
+declaration order is never scheduling priority. Overlapping source identities
+are retained, deduplicated, or rejected only according to the explicit overlap
+policy. Demo and tests use synthetic or fake providers and perform no live source
+or agent automation. See the complete JSON example for GitHub and Slack shapes.
 Local logs and worktrees can contain repository content; keep this directory private.
 
 If a push or merge response is lost, Town checks GitHub rather than assuming
@@ -364,6 +485,18 @@ Retry explicitly permits another attempt after fresh checks. For an uncertain
 repair push, it reuses and verifies the saved commit; it does not rerun the agent.
 If the PR moved, the saved worktree is retained for inspection. A retry also resets
 an exhausted repair budget. Never delete an uncertain intent to force progress.
+
+When the release house reports that Release Bot's retry budget is exhausted, fix
+the reported failure and ask Town to lift the budget:
+
+```sh
+./bin/bt retry --repo BrokkAi/my-project --role release
+```
+
+The next release run first calls the bot's `POST /v1/retry` worker API, which
+resets the pending release's attempt budget in its own workspace, then resumes
+the same release. Town never edits the bot's private state. The pinned Release
+Bot must advertise the `retry` capability; older pins report that plainly.
 Use `bt status` to inspect saved details and GitHub to resolve conflicts.
 
 The HTTP listener accepts loopback IPs only (default `127.0.0.1:8099`). Host,

package/licenses/THIRD_PARTY_NOTICES.txt

@@ -221,6 +221,230 @@ Source: https://github.com/BrokkAi/acp-go/tree/v0.1.0
 
 ==============================================================================
 
+github.com/BrokkAi/issue-bot v0.5.2
+License: Apache-2.0
+Source: https://github.com/BrokkAi/issue-bot/tree/v0.5.2
+
+==============================================================================
+
+--- github.com/BrokkAi/issue-bot/LICENSE ---
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+==============================================================================
+
+--- github.com/BrokkAi/issue-bot/NOTICE ---
+
+Brokk Issue Bot
+Copyright 2026 Brokk.ai and contributors
+
+This project is licensed under the Apache License, Version 2.0.
+See LICENSE for the full terms. Third-party terms and attribution are
+provided in licenses/THIRD_PARTY_NOTICES.txt.
+
+==============================================================================
+
 github.com/rivo/uniseg v0.4.7
 License: MIT AND Unicode-3.0
 Source: https://github.com/rivo/uniseg/tree/v0.4.7

package/package.json

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