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

package/BUILD.json

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

package/README.md

@@ -38,8 +38,8 @@ and an authenticated ACP agent. The default is `codex-acp`; if it is missing,
 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
+and the repository's default branch. New workspaces use a private bare Git
+repository and a separate persistent 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.
 
@@ -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
@@ -177,7 +180,24 @@ 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.
+logs. Retain the managed workspace, issue worktrees and state together across restarts.
+
+New workspaces keep Git storage in `state/repository.git`, a detached management
+worktree in `checkout`, and each issue's worktree in `checkout-issues/<number>`.
+The management and issue worktrees share only this bot's private repository;
+your checkout, release-bot and other bots have independent Git metadata.
+Existing managed clones and their unfinished issue worktrees continue in place.
+A manually configured checkout must be a standalone clone or this bot's private
+worktree; a linked worktree sharing another repository's Git metadata is rejected.
+
+Each attempt fetches the watched branch. The agent merges current remote changes
+into its assigned issue branch, resolves conflicts, and reruns affected checks
+before returning a fix. Retries retain the same branch, staged/unstaged edits,
+and unfinished merges. Other issue worktrees and the local `master`/`main` branch
+are left alone. Overlapping code changes can still need conflict resolution or
+review; worktree isolation prevents local interference. Existing claim comments
+coordinate separate issue-bot instances, and local locks prevent duplicate daemons
+from using the same workspace.
 
 ACP permission requests are automatically approved. Client filesystem callbacks
 are confined by `os.Root`; agents and terminal commands inherit the bot account's
@@ -188,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.2.1",
+  "version": "0.3.1",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",