best-peer 0.0.23

best-peer 0.0.23

A card its owner is using takes no new work, and the owner holds and releases the machine by hand; a key taken back takes its work with it; a peer that cannot mount makes no disk for a job and never takes the last of its file system. An agent driving a workspace on a GPU host from the manifest alone is recorded in acceptance.

Commits since v0.0.22

• Review: a credential taken back is checked before a hold that ended a starting workload, and a hold that could not stop one leaves it to come ready, so neither depends on timing nor leaves a deployment starting for ever (29a7c58)
• A peer that cannot mount makes no disk for a job and reserves no room for one, and a disk never takes the last of its file system, so a job asking for a disk cannot fill the peer's volume (3271f4e)
• A key the operator takes back takes its work with it: its waiting orders end before they start, its jobs stop and its deployments end, unless revoke is told --keep-running, so a key taken back for misuse leaves nothing to start later in its name (5023f68)
• A card its owner is using takes no new work, found from the driver and never logged, and the owner holds and releases the machine by hand, so a personal GPU can be lent without competing with its owner (55ad893)
• Review: an issue filed for an epic's work is made its sub-issue and carries its label, and enhancement is never used since an issue that is not a bug is one by default (9975a5a)
• The board's labels say which one epic an issue belongs to: an epic carries epic and a label of its own, the product's name with a number, and every issue of it carries that label and no other epic's (f8f58c0)
• Review: the release script's usage example is the next patch, not a minor, as SDLC.md now says (3fc2391)
• A release is a patch, and the minor or the major goes up only when the owner asks for it, so SDLC.md no longer has a capability raise the minor on its own (e8587b2)
• Review: the run's record gives the joining read as two thirds of a second before the door's poll and the engine image's pull as 1 minute 17 seconds, as the logs have them (8b5fc95)
• Review: the run's record says the agent's code was approved six seconds after the client showed it and only the member's before it asked, scopes the cloud on every fact to those from CloudConfiguredV1 on, counts the client's two questions among the 31 calls, gives 6:02 from the person's sentence, and the README's definition of done names the new record (92e9430)
• Review: the run's record says when each approval was made and that the agent's joining read came half a second before the door's poll, names the peer on the facts a member told and not on the job's order, gives the client's time as 6:20 with 2:37 waiting and the model ready 13 s after the pull, and says how the member was seen empty; the run's credential file is deleted as the record says (7091df2)
• An agent drives a workspace on a GPU host from the manifest alone, recorded in acceptance: Copilot through best-mcp 2.6.0 signs in to best-peer 0.0.22's door, creates a workspace, configures a cloud with a V100 member, deploys, prompts as a command and reads PromptAnswered with the cloud and peer, runs a job whose end carries its output, and undeploys; the README's step 5 links it (behavioralstate/spec#62, behavioralstate/spec#73) (80c7f53)

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.23. 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.23-x86_64-unknown-linux-gnu.tar.gz	best-peer-x86_64-unknown-linux-gnu.tar.gz
Windows x86_64	best-peer-0.0.23-x86_64-pc-windows-msvc.zip	best-peer-x86_64-pc-windows-msvc.zip
macOS Apple silicon	best-peer-0.0.23-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.