2026-09-27 - 2026-09-28
Overview
30 Pull requests merged by 2 users
Merged
#111 The controller follows the subject it decodes
Merged
#110 A merge on the forge builds what it moved, bases first
Merged
#109 rollout hand: a machine's membership, minted afresh and handed to an operator once
Merged
#108 A store row keeps its seat's protocol, and a holder may take work from its queue
Merged
#107 The build machine takes work on the bus its credential names, and the work queue has a taker
Merged
#106 A principal may hear what its consumer delivers
Merged
#105 The bus account has JetStream, and the control plane's client has its own inbox
Merged
#104 The control plane pins the bus's certificate, and keeps its password out of errors
Merged
#103 The control plane serves and pushes on the bus it is told to
Merged
#102 A machine may bind its consumer
Merged
#101 The mint leaves the control plane's old-bus secret alone
Merged
#100 The control plane mounts the bus secret it reads
Merged
#99 The network map resolves each machine with the seat holders on record
Merged
#98 The control plane speaks the new bus
Merged
#97 The mint names the bus by bare host, and can mint again
Merged
#96 The mint finds the bus on the hub
Merged
#95 The move mints every credential and tells each machine its membership
Merged
#93 The first handover records the standing holder without re-judging it
Merged
#92 AMQP is not a provision: the bus seat delivers the bus, and the word is refused
Merged
#91 A seat is handed over as one act, and the holder is on record
Merged
#90 The move ends with the old broker going, not staying
Merged
#89 The store owns the seat set, so only the control plane may judge a claim
Merged
#88 The Go base has to be 1.26: the NATS client requires it
Merged
#87 The bus on NATS: both transports behind seams, and the rollout switch
Merged
#86 The mesh owns the operator's ~/.ssh: account fact + home-scoped resources (to-be 29)
Merged
#85 A module declares its fail2ban jail; mesh composes per node (to-be 31 mechanism)
Merged
#84 A module can name the mesh's range: ${machine:mesh-range}
Merged
#83 Seats keep their former names — a rename is one DB op (ADR 0122, phase 2)
Merged
#82 Seats are data the controller owns, loaded from its store (ADR 0122, phase 1)
Merged
#81 Name system seats by scope; let a module define its own (ADR 0121)
1 Pull request proposed by 1 user
Proposed
#94 The two seat commands appear in the usage text