@brokkai/brokk-town-linux-arm64 0.1.0-rc.1

package/BUILD.json

@@ -0,0 +1 @@
+{"commit": "cfa1a68754e565b61894bb5de33558ee05b169f7", "tag": "v0.1.0-rc.1", "target": "linux-arm64"}

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

package/NOTICE

@@ -0,0 +1,12 @@
+Brokk Town
+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.
+
+Process execution, terminal key decoding, and license checking foundations
+are adapted from BrokkAi/review-bot, BrokkAi/bug-bot, and BrokkAi/issue-bot,
+also licensed under Apache-2.0. Modified for the local multi-repository service.
+
+Town artwork was generated for this project; see docs/ARTWORK.md.

package/README.md

@@ -0,0 +1,203 @@
+# Brokk Town
+
+One repository, one little town. Brokk Town runs several repository towns from a
+local Go service, with an animated browser village and a compact terminal control
+panel. Each town owns its houses, queues, review loops, releases, and history.
+Branches and private worktrees belong to their repository's town. Your machine
+hosts the towns and shares four agent worker slots between them.
+
+The browser shows worker houses, wheelbarrows carrying completed handoffs, trucks
+bringing external issues and PRs, and shipments leaving the release depot. Visit
+a house to inspect its queue, activity, errors, and controls. Town hall holds
+repo-bot's reports. The all-towns overview shows activity and attention counts
+without visiting each repository.
+
+[![CI](https://github.com/BrokkAi/brokk-town/actions/workflows/ci.yml/badge.svg)](https://github.com/BrokkAi/brokk-town/actions/workflows/ci.yml)
+
+This is the first local implementation. The browser UI is embedded in the Go
+binary; Node.js is only needed for UI development checks and agents that use it.
+Linux and macOS are supported. No hosted service is required.
+
+## Try the town
+
+Build with the Go version in `go.mod`:
+
+```sh
+make build
+./bin/bt serve --demo
+```
+
+Open the browser address printed by the service. In another terminal:
+
+```sh
+./bin/bt tui --demo
+```
+
+Demo mode uses an isolated state directory and simulated activity in two towns.
+It never calls GitHub or launches agents. Orchard cycles through bug discovery,
+implementation, review, repair, merge, release, and external arrivals. Paper-trail
+illustrates a quiet neighboring repository. 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.
+
+## Installation and releases
+
+Source is published at [BrokkAi/brokk-town](https://github.com/BrokkAi/brokk-town).
+Until the first release, build from source as above, or install the current branch:
+
+```sh
+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. No release
+has been cut yet. After the first release, the supported installer commands are:
+
+```sh
+sh install.sh                       # From a checkout; defaults to ~/.local/bin
+npm install -g @brokkai/brokk-town   # Installs the bt launcher and native package
+```
+
+The GitHub release workflow and npm OIDC workflow follow the bot repositories.
+The `packages-publish` environment accepts `v*` tags only. npm trust must be
+configured for all five package names after their initial bootstrap publication;
+a workflow file alone does not establish npm trust. See [RELEASING.md](RELEASING.md)
+for first-release setup, access checks, publishing, and recovery.
+
+## Connect real repositories
+
+Install and authenticate `git`, GitHub CLI (`gh`), and an ACP coding agent. The
+agent defaults to `codex-acp` on PATH, with `npx --yes
+@agentclientprotocol/codex-acp` as its fallback. Git must already be able to clone
+and push your GitHub repositories; Town uses the current Git/gh credentials.
+
+```sh
+./bin/bt serve --repo BrokkAi/my-project
+# In another terminal:
+./bin/bt add --repo BrokkAi/another-project
+./bin/bt tui
+```
+
+New towns start with the four 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,
+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.
+
+```sh
+./bin/bt start --repo BrokkAi/my-project --role bug
+./bin/bt pause --repo BrokkAi/my-project --role all
+./bin/bt stop --repo BrokkAi/my-project --role issue
+./bin/bt status
+```
+
+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.
+
+## How work moves
+
+| House | Work and handoff |
+| --- | --- |
+| Bug greenhouse | Runs bug-bot's investigation and verification; observed filed issues travel to issue-bot. |
+| Issue workshop | Runs issue-bot on eligible issues, opens implementation-ready PRs, and repairs Town-owned PR branches from review feedback. |
+| Review observatory | Runs review-bot, independently checks the full change and every retained finding, then returns fixes or waits for merge requirements. |
+| Release depot | Runs release-bot's batching and publishing policy. Confirmed merged/direct commits accumulate here; a published stable release ships only commits proven to be its ancestors. |
+| Repo watchtower | Polls GitHub, reconciles arrivals and revisions, summarizes new commit titles, reports queue growth and blocked work. |
+| Town hall | Stores periodic and event-triggered repo-bot reports. |
+
+The first complete inventory establishes existing work without a burst of arrival
+animations. Subsequent deliveries follow durable, sequenced state changes.
+Animation never initiates a GitHub write. Reconnecting does not replay previously
+seen deliveries. External PRs receive reviews but their branches are left to their
+authors; only locally recorded Town-created branches enter automatic repair.
+
+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
+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
+and approvals. Town uses an expected-head squash merge, without admin bypass.
+Repositories that require a merge queue or prohibit squash merging need manual
+merges for now. GitHub is the final authority at write time.
+
+## Configuration and recovery
+
+Copy [docs/config.example.json](docs/config.example.json), edit the repository,
+agent command, verification command, and policy, then run:
+
+```sh
+./bin/bt serve --config /path/to/towns.json
+```
+
+Configuration is a JSON array. Each entry supplies `repo`, optional `branch`,
+`agent`, optional `verify` argument vector, `merge_policy`, `poll_seconds`,
+`report_seconds`, and `max_cycles`. The example lists all required values. Town
+uses the repository's default branch when omitted; an initialized town's branch
+cannot be changed in place. Omitted towns are retained when loading a config.
+Agent configuration uses acp-go's `command`, `environment`, `auth_method`, `mode`, `model`, and `effort` fields.
+
+Repo-bot and issue/review scheduling use `poll_seconds` (default 60). Quiet reports
+use `report_seconds` (1800). Bug-bot runs at most every 30 minutes; release-bot
+checks every five minutes and retains its own quiet window, minimum gap, and
+batching decisions. Each worker attempt has a two-hour deadline. Repair cycles
+default to five; failed PR attempts back off and block after three failures.
+
+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
+local key in a URL fragment. `connection.json` and state snapshots are mode 0600.
+Agent commands/environment values are omitted from public configuration snapshots.
+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
+success. Inspect the task and its saved intent, then use **Reconcile and retry** or:
+
+```sh
+./bin/bt retry --repo BrokkAi/my-project --task pr:123
+```
+
+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.
+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,
+origin, and bearer key checks protect the local API. A browser supporting WebMCP
+can list towns and navigate to a house through optional page tools. Unsupported
+browsers use the ordinary interface.
+
+## Keyboard and development
+
+Browser: `0` overview, `1`–`5` agent houses, `6` town hall, `?` help, Escape closes
+the inspector. Motion follows reduced-motion preferences and can be switched off.
+Terminal: `0` overview, Tab next town, `1`–`5` or `j`/`k` select a house, `s` start,
+`p` pause, `x` stop, `a` wake the selected town, `q` detach. Bracketed paste is
+ignored as commands. Network and agent work stay off the input/render loops.
+
+```sh
+make check
+make smoke
+```
+
+Tests use fake GitHub and agents, temporary local Git remotes, authenticated HTTP
+fixtures, and the isolated simulation. Do not use live repository automation as a
+development test. See [CONTRIBUTING.md](CONTRIBUTING.md),
+[docs/ARCHITECTURE.md](docs/ARCHITECTURE.md), and
+[licenses/README.md](licenses/README.md).
+
+Licensed under [Apache-2.0](LICENSE). Attribution is in [NOTICE](NOTICE) and
+[third-party notices](licenses/THIRD_PARTY_NOTICES.txt). Artwork provenance is in
+[docs/ARTWORK.md](docs/ARTWORK.md). Native and npm packaging is configured; the first publication still requires
+the documented package bootstrap and trusted-publisher setup.