best-peer 0.0.22

best-peer 0.0.22

An agent reaches the workspace it made through the published connector (best-mcp 2.6.0): the root's sign-in names no tenant, and a stranger is told to act with the credential that made or joined the workspace. A job's end carries the last lines it printed, and its outputs are its files, directories and links, streamed to the store, cut by a stop or the order's deadline.

Commits since v0.0.21

• Review: a stranger to a workspace is told to act with the credential that made or joined it, the README names the best-mcp that reaches a workspace, and the departure is entries 2 and 23 of spec#37 (ab18754)
• The root's token answer names no tenant_id, and a stranger's NO_SUCH_WORKSPACE says that a sign-in is a new identity, so an agent reaches the workspace it made with the credential that made it (behavioralstate/spec#73) (b371ef7)
• Review: the peer bounds a job's output itself, the Docker read keeps only its end, and the outputs paths and the size rule say where output is (e46684b)
• A job's end carries the last lines it printed, so an agent that ran a job reads what it said from the manifest alone (091ba39)
• A job's outputs are its files, directories and links, streamed to the store as they are packed, and a stop or the order's deadline ends their sending (#53) (a05db7f)
• Review: the main a pull request is squashed onto is noted from the worktree, after the fetch (267d366)
• Review: a pull request's reviewed head is recorded and compared in full, and a merge waits for the gate again when main moved since it (a47680b)
• Review: a pull request's head is compared at seven characters, and its merge is pinned to the head that was gated (30129bb)
• Review: every rule says the pull request's gate runs on what would land, a push since its review sends it back to the review, and the scratch worktree is removed by force (1b4d430)
• Review: a contributor's pull request is gated on what would land, its head squashed onto the current main (7521f59)
• Review: the review skill's opening, CLAUDE.md and SDLC.md section 6 say the whole merge and rebase rule (1d21212)
• Review: a rebase that brings commits in sends the gate back to the new head, a fork's code runs only after its diff is read, and a red gate is reported as not ready (0ca7164)
• Review: a set-aside finding is recorded in an empty Review: commit, the gate runs last on the head pushed, and a contributor's pull request is read and gated at its own head (14ddb69)
• Every change is made on main and pushed there, after the local gate and the mandatory review, so work no longer waits in pull requests (62aa106)
• An epic is In progress as soon as any of its issues is In progress, In review or Done, and Backlog before that, so the board's columns say which goals have work under way (#52) (fd3e72a)

Run it

One binary. Download the archive for the machine, check it against SHA256SUMS, unpack it and run best-peer with the environment the README's Run section names; best-peer --version says best-peer 0.0.22. Each archive is here twice, byte for byte the same: under the name with the version, for pinning, and under the name without it, which releases/latest/download/<name> resolves to the newest release, as the README's commands use.

Machine	Archive	Same file, unversioned
Linux x86_64 (glibc 2.35 or newer)	best-peer-0.0.22-x86_64-unknown-linux-gnu.tar.gz	best-peer-x86_64-unknown-linux-gnu.tar.gz
Windows x86_64	best-peer-0.0.22-x86_64-pc-windows-msvc.zip	best-peer-x86_64-pc-windows-msvc.zip
macOS Apple silicon	best-peer-0.0.22-aarch64-apple-darwin.tar.gz	best-peer-aarch64-apple-darwin.tar.gz

Every archive carries a build provenance attestation: gh attestation verify <archive> --repo behavioralstate/best-peer.