@brokkai/issue-bot-darwin-x64 0.5.1 → 0.5.3

package/BUILD.json

@@ -1 +1 @@
-{"commit": "b6fd95e7a21396a422907e3ba356966f02830944", "tag": "v0.5.1", "target": "darwin-amd64"}
+{"commit": "fd48c698b2793a979d167f6a273f04aa8c4d0072", "tag": "v0.5.3", "target": "darwin-amd64"}

package/README.md

@@ -186,6 +186,10 @@ private to the local service, and the process exits after Town requests shutdown
 
 Worker protocol v1 uses standard-library HTTP with JSON messages:
 
+Town may include an `issue` number in a run request to constrain the operation to
+one explicitly admitted issue. The worker advertises the `exact-issue` capability;
+an omitted issue retains repository-wide behavior for existing clients.
+
 - `GET /v1/initialize` returns the protocol range, bot identity, release version,
   and capabilities. Town requires `issue-result` as well as common `run` and
   `progress` capabilities.
@@ -233,6 +237,10 @@ to `AGENTS.md`, `CONTRIBUTING.md`, and `README.md`. `issue` can pin one issue nu
 
 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.
+It must leave HEAD, the assigned branch, and the clean worktree unchanged. The
+bot repeats its publication checks after verification and pushes the exact
+validated commit. Failed verification leaves local work intact for inspection
+and retry.
 
 ## State and diagnostics
 

package/package.json

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