@brokkai/issue-bot-darwin-x64 0.3.0 → 0.3.1

package/BUILD.json

@@ -1 +1 @@
-{"commit": "6179a134ef36597a101368c4b11b30960157eba3", "tag": "v0.3.0", "target": "darwin-amd64"}
+{"commit": "77aa637c93df32b4af99f497e167c4b759c40196", "tag": "v0.3.1", "target": "darwin-amd64"}

package/README.md

@@ -53,6 +53,7 @@ bib --agent your-acp-agent --agent-arg=--stdio
 bib --claim-timeout 15m
 bib --draft=false
 bib status
+bib version
 bib retry --issue 123 --once
 ```
 
@@ -62,6 +63,8 @@ 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.
 
+`bib version` prints the embedded release tag. Local builds report `dev`; binaries installed with `go install ...@version` report the module version.
+
 ## How it works
 
 1. Walk all open, unlocked issues, oldest first, with pagination. No label
@@ -205,13 +208,16 @@ 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.
+Pushing a `v*` version tag automatically runs CI, publishes the native GitHub
+release, and uploads the four npm platform packages followed by the launcher.
+Follow the **Publish packages** workflow for the complete pipeline; it keeps all
+artifacts tied to the same tag and commit. No separate manual dispatch is needed.
+
+The manual workflow remains available for recovery: dispatch from the existing
+tag with its tag input and `publish=true`, or use `publish=false` for validation
+only. Existing package bytes are checked for conflicts before uploading.
+Successful uploads do not wait for npm's public version index or run immediate
+public-install checks. Use the explicit registry `verify` command later if needed.
 
 The workflow uses the `packages-publish` environment. Configure npm trusted
 publishing for each of the five `@brokkai/issue-bot*` packages with repository

package/package.json

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