Repository navigation
v0.10.0 — named execution boundaries and release preparation
v0.10.0 — named execution boundaries and release preparation
This release adds explicit execution boundaries, named closure of residual
findings, and reusable release preparation. It includes the changes merged
since v0.9.1.
What changed
- Named execution boundaries. A realm selects its boundary, the run manifest
pins it, and effects, seat records, CLI, TUI and web readouts report it.
Admission checks cover run, resume, rerun and doctor. Runs underharnessor
openare visibly marked unboxed.
#230 - Explicit finding closure.
brokkr operator --action supersedecloses
residuals by name and records who closed them, optionally citing the run that
addressed them. Past judgments remain intact.
#212 - Release manager. A portable library agent prepares versions, writes notes
from commits, reconciles README, architecture and configured documentation,
and prepares organization-profile updates. The realm's pinned house file
supplies extensible project configuration. Thereleaserecipe verifies and
reviews the candidate; publication remains a separate, explicit action. - Standby and landing recipes. Standby supplies an alternative provider crew
when the default account is exhausted. Landing classifies an existing branch,
verifies code changes, reviews it and returns findings for remediation before
shipping.
#228,
#241 - Adapter and prompt fixes. Add the DeepSeek
flash-experimentalias, pin
research-dsh effort toxhigh, and spell out the result contract's three keys.
#238,
#239,
#215 - Reproducible coverage setup. CI, local coverage and the release workflow
use the dated nightly inrust-nightly-version.txt.
#236
Upgrade and compatibility
The default boundary remains namespace, requiring Linux or WSL2 and
bubblewrap 0.10 or newer. Realm maps declaring a boundary use forge.realms/v4.
harness and open do not build a Brokkr namespace box; model gates under
harness require an adapter fragment that has been measured for that provider.
Some shipped recipes therefore still refuse under harness.
seatbelt and container are named but not implemented and refuse at start.
The old driver.confine declaration is retired and refused. There is no working
container migration in this release; choose an available boundary only if it
meets the deployment's requirements. See the
boundary guide.
New realms v4, run-manifest v9, seat-record v4 and effect-boundary v1 files sit
beside their earlier contracts. The earlier frozen bytes remain unchanged.
The version bump changes compiled manifest identities; use the engine's normal
resume comparison and refusals when bringing a run across versions.
The binary remains brokkr, with Rust 1.88 as the minimum build version. Install
or upgrade through the existing package channels, or download the platform
archive, check it against SHA256SUMS, and verify build provenance with
gh attestation verify <asset> -R feedback-loop-ai/brokkr.