@brokkai/issue-bot-darwin-x64 0.2.1

package/BUILD.json

@@ -0,0 +1 @@
+{"commit": "e375e63f6fc592f6c0f0e35e268a46103027fd5c", "tag": "v0.2.1", "target": "darwin-amd64"}

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/README.md

@@ -0,0 +1,237 @@
+# Brokk Issue Bot
+
+Walk GitHub issues, give a coding agent a focused attempt at each one, and open
+pull requests for review. A Go daemon with the same no-config startup as
+[release-bot](https://github.com/BrokkAi/release-bot). Both use the shared
+[acp-go](https://github.com/BrokkAi/acp-go) protocol client and process runner.
+
+## Install and run
+
+```sh
+npm install -g @brokkai/issue-bot
+cd /path/to/your-repo
+bib
+```
+
+For a single invocation, use `npx --yes @brokkai/issue-bot` from your repository.
+The npm package requires Node.js 18+ and includes the native binary for
+Linux/macOS on x64 or arm64 through optional dependencies. Keep optional
+dependencies enabled; installing and running the package does not require Go.
+
+Or install a prebuilt Linux/macOS binary (amd64 or arm64):
+
+```sh
+curl -fsSL https://raw.githubusercontent.com/BrokkAi/issue-bot/master/install.sh | sh
+```
+
+The installer checks the archive's SHA-256 and installs `bib` to `~/.local/bin`.
+Set `INSTALL_DIR` to use another directory. From source, `make build` produces
+`bin/bib`. Source builds require Go 1.27.1. You can also install from Go:
+
+```sh
+go install github.com/BrokkAi/issue-bot/cmd/bib@latest
+```
+
+Runtime requirements: Git, authenticated `gh` with repository read/push/PR access,
+and an authenticated ACP agent. The default is `codex-acp`; if it is missing,
+`bib` uses `npx --yes @agentclientprotocol/codex-acp` (requires Node.js and may
+download the adapter). Explicit agent commands are used exactly as supplied.
+
+No configuration file is needed. The bot discovers `origin` (or the only remote)
+and the repository's default branch. It creates a managed clone and a separate
+Git worktree for each issue. Your source checkout and uncommitted edits are left
+alone. Starting it authorizes unattended edits, command execution, commits,
+branch pushes, claim/status comments and PR creation for the configured repository.
+
+```sh
+bib /path/to/repo
+bib https://github.com/OWNER/REPO.git
+bib --label bug --label ready
+bib once --issue 123
+bib --model YOUR_MODEL_ID --effort low
+bib --agent your-acp-agent --agent-arg=--stdio
+bib --claim-timeout 15m
+bib --draft=false
+bib status
+bib retry --issue 123 --once
+```
+
+Flags may appear before or after the repository argument. `--once` attempts at
+most one eligible issue (or reconciles one completed job), then exits. `status`
+prints saved JSON without starting an agent. `retry` resets pending/blocked
+attempt budgets and resumes work; `--issue` restricts it to that issue. Run
+`bib --help` for all flags.
+
+## How it works
+
+1. Walk all open, unlocked issues, oldest first, with pagination. No label
+   filter is required. Optional repeated `--label` flags require all labels;
+   `exclude_labels` can opt out particular labels.
+2. Skip issues that already have a linked or cross-referenced PR, including PRs
+   created by people or other bots, on other branches or forks. Open, draft,
+   merged and closed PRs all count. GitHub's issue links and timeline are checked;
+   a PR with no reference to the issue cannot be associated automatically.
+3. Post an **“I'm starting work on this issue”** comment with a unique claim and
+   expiry time. Other instances skip issues with an active claim and continue
+   walking the queue. Recheck competing claims before launching the agent.
+4. Create a persistent `issue-bot/<base-branch-hash>/<issue-number>` branch and
+   isolated worktree. The agent reads repository instructions, inspects the issue
+   and discussion, implements a focused fix, runs checks, and commits locally.
+5. Require a completion receipt with the explanation and validation evidence.
+   Independently check the branch, clean worktree, starting commit and real diff.
+   An optional operator `verify` command must also pass. Recheck claim ownership
+   and existing PRs before pushing and again before creating the PR.
+6. Push without force and create a draft PR with the explanation, check results
+   and `Fixes #N`. Confirm its repository, branches, issue marker and head commit.
+   Update the starting comment to **“Done — pull request: URL”**, then continue
+   to the next available issue. `--draft=false` creates regular PRs. The bot
+   does not merge PRs or close issues itself.
+
+A PR is recorded as **submitted**, not as proof that the issue is solved. Agent
+validation evidence is a report; the bot does not infer test correctness from
+prose or wait for remote CI. Use repository branch protections and review, and
+configure `verify` when you need an independent local gate.
+
+Ambiguous, already-fixed, unsupported or oversized issues can be marked blocked
+with an explanation on the issue. They do not prevent attempts on later issues.
+Failed or interrupted attempts mark the claim released; detailed diagnostics stay
+in local logs. Transient work failures retry after 15 minutes, up to
+three attempts; exhausted jobs require `retry`. Failed work and the previous
+failure are preserved. Agent setup failures (login, executable, model or effort)
+stop the daemon without consuming an issue attempt.
+
+The daemon polls every five minutes when no issue is ready; while work is
+available it proceeds sequentially. Each attempt has a two-hour budget. Saved
+pending jobs are checked for an existing PR before further agent work, including
+at the attempt limit or after the issue closes. A lost PR-creation response is
+reconciled by the persistent branch and issue marker. A closed, unmerged bot PR
+blocks the job for inspection. Work is not automatically deleted or reset.
+
+## Coordination between instances
+
+The claim timeout defaults to **15 minutes**, configurable with
+`--claim-timeout 30m` or `"claim_timeout": "30m"` (minimum 30 seconds).
+While working, the bot renews the same comment every third of that duration.
+The per-attempt `timeout` is separate and still defaults to two hours. A crashed
+instance stops renewing; another instance can take over after its claim expires.
+A renewal error cancels the active agent, and publication requires a fresh
+ownership check. Keep participating machines' clocks synchronized.
+
+Claims cover the repository and issue number across base branches and machines.
+Each installation keeps its own managed workspace; local locks still protect
+against two processes sharing the same checkout/state. Simultaneous claimants
+wait two seconds after posting and elect the lowest active GitHub comment ID;
+losers release their comment and move on. GitHub comments provide **advisory
+coordination, not an atomic distributed lock**: delayed visibility can briefly
+allow duplicate local effort. Rechecking ownership and PR links before publication
+reduces duplicate PRs, but GitHub offers no atomic comment-claim/PR transaction.
+All participating instances need this version's claim protocol; older versions
+do not honor it.
+
+Starting comments and completion updates are idempotent across retries: the
+random token is saved before the initial POST, and a failed completion update
+is retried without running the agent or creating a PR again. The same comment
+is updated throughout the attempt so heartbeats do not produce comment spam.
+If an attempt cannot continue, its comment is marked released. An uneditable or
+deleted comment stops renewal; a previously saved completion can be posted again
+if its comment was deleted. Issues/PR read access, issue-comment write access,
+and the existing push/PR-creation rights are required.
+
+## Optional configuration
+
+`bib --config issue-bot.json` reads a strict JSON object. There is no implicitly
+loaded or generated config. Paths are relative to that file. See
+[issue-bot.example.json](issue-bot.example.json).
+
+```json
+{
+  "remote": "https://github.com/OWNER/REPO.git",
+  "branch": "main",
+  "directory": "var/checkout",
+  "state_directory": "var/state",
+  "labels": ["bug"],
+  "exclude_labels": ["wontfix", "duplicate", "invalid"],
+  "draft": true,
+  "poll": "5m",
+  "claim_timeout": "15m",
+  "timeout": "2h",
+  "retry_delay": "15m",
+  "attempts": 3,
+  "agent": {"command": ["codex-acp"], "model": "YOUR_MODEL_ID", "effort": "low"},
+  "verify": ["/opt/checks/verify-issue"]
+}
+```
+
+`agent` also accepts `environment`, `auth_method` and `mode`. Model and effort
+choices are selected and confirmed before work; unavailable choices fail
+explicitly. `github.host` supports Enterprise; `github.repo` (`OWNER/REPO`)
+identifies a repository when using a local mirror. `instruction_files` defaults
+to `AGENTS.md`, `CONTRIBUTING.md`, and `README.md`. `issue` can pin one issue number.
+
+The verifier runs as an argument array, without shell expansion, in the issue
+worktree with `ISSUE_NUMBER` set. Keep it outside the agent's writable worktree.
+
+## State and diagnostics
+
+Default state lives below `$XDG_STATE_HOME/issue-bot` or
+`~/.local/state/issue-bot`, keyed by remote and base branch. Startup logs the paths.
+State writes use atomic replacement and fsync. Private JSONL transcripts live in
+`state/sessions`; readable live output goes to stderr. Use `--json` for structured
+logs. Retain the managed clone, issue worktrees and state together across restarts.
+
+ACP permission requests are automatically approved. Client filesystem callbacks
+are confined by `os.Root`; agents and terminal commands inherit the bot account's
+OS rights. This is not a sandbox. Use an account/container appropriate for the
+repository and its credentials. Transcripts may include code and command output;
+manage their retention externally. Issue text is treated as untrusted problem
+data in the agent instructions, not as permission to broaden the task.
+
+## Publishing npm packages
+
+Tag releases build four native archives with checksums and commit metadata.
+After the GitHub release finishes, run the **Publish packages** workflow from
+that same tag, supplying the tag as input. The default `publish=false` builds
+and tests the npm tarballs and saves them as a workflow artifact. Set
+`publish=true` to publish the four native packages followed by the launcher.
+Retries verify existing versions against the staged bytes and skip identical
+uploads; conflicting versions stop publication.
+
+The workflow uses the `packages-publish` environment. Configure npm trusted
+publishing for each of the five `@brokkai/issue-bot*` packages with repository
+`BrokkAi/issue-bot`, workflow `publish-packages.yml`, and environment
+`packages-publish`. An environment secret named `NPM_TOKEN` can be used for
+bootstrap publication. Only npm is packaged; uv support is pending.
+
+For a local installer check from a clean commit (requires Go, Node.js 24 and npm):
+
+```sh
+node --test --test-isolation=none npm/bib.test.cjs
+python3 -m unittest discover -s scripts -p '*_test.py'
+python3 scripts/smoke_installers.py
+```
+
+The smoke check builds native archives and all five npm tarballs, then installs
+and launches the local platform package offline with lifecycle scripts disabled.
+
+## Development
+
+```sh
+make check build
+./bin/bib --help
+```
+
+Tests use temporary Git remotes and simulated GitHub responses. They cover
+walking multiple issues, existing human/fork PR detection, competing claims,
+claim expiry and renewal failure, idempotent starting/completion comments,
+PR reconciliation after a lost response, blocked-job
+fairness, retries preserving edits, setup failures, independent verification,
+configuration, discovery and locks. They do not run a paid agent or create PRs
+in live repositories. The shared ACP library and release-bot additionally test
+protocol and subprocess interoperability, model/effort selection and cancellation.
+
+Protocol/API references: [ACP v1](https://agentclientprotocol.com/protocol/v1/overview),
+[GitHub issues](https://docs.github.com/en/rest/issues/issues),
+[GitHub pull requests](https://docs.github.com/en/rest/pulls/pulls).
+
+Licensed under [Apache-2.0](LICENSE). Repository discovery and CLI/runner patterns
+originate in BrokkAi/release-bot; common ACP code is maintained in BrokkAi/acp-go.

package/package.json

@@ -0,0 +1,19 @@
+{
+  "version": "0.2.1",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/BrokkAi/issue-bot.git"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "name": "@brokkai/issue-bot-darwin-x64",
+  "os": [
+    "darwin"
+  ],
+  "cpu": [
+    "x64"
+  ],
+  "description": "Brokk Issue Bot native binary for darwin/x64"
+}