What's in this release

Bind execution contexts to one repository control bundle

Boatstack now fingerprints the runtime pin, project configuration, host skills,
Flow sources, locks, assets, artifacts, and generated entry skills as one
control bundle. Runtime changes and worktree transfers verify the complete
source and target bundles before committing state or lineage.

Workspace creation now resolves its base to one commit and checks out that
exact revision. Generated entry skills also use the repository-pinned release
tag, so changing only the Boatstack build version no longer changes skill
bytes.

Let repository Flows require bounded foreground work

Flows can now declare exact instruction assets, entry inputs, and staged output
contracts for human or agent work. Boatstack suspends and resumes the same run,
validates the result as evidence, and still admits effects only through trusted
operators. Input fingerprints and request-specific staging prevent changed
inputs from reusing stale work. The software-delivery adapter also provides
optional planning-package admission, approval, and promotion operations.

The runtime performs a one-step, transactional schema-4 state upgrade and
verifies every declared planning-package output before approval. Trusted
software-delivery lowering also rejects work inputs that any reachable entry
cannot bind.

Fresh delegated runs now bootstrap verified runtime and configuration state
before deriving repository-policy authority. An exact autonomy delegation may
perform that local initialization, while transitions requiring repository
authority remain unavailable until verified configuration evidence exists.

Published-PR entries now stop until intended delivery changes are committed,
bind the preview and push to that exact commit, and derive short-lived GitHub
provider capability through each trusted transition's declared fingerprint
binding, including correction and recovery. Caller-provided provider receipts
are rejected.

Batch verified changes into nightly releases

Boatstack now checks for verified unreleased changes nightly at 02:00 UTC. Maintainers can request the same stable release check manually, while branch-based release candidates remain available separately.

Publish TypeScript SDK documentation

Flow authors can now browse generated API reference and Product Delivery guides, while required CI validates the documentation before SDK changes merge.

What's in this release

Add read-only control explanations

Boatstack can now explain the exact current controller decision, including rejected predicates and missing authority, without executing an effect. Flow entries may opt generated Codex and Claude skills into this diagnosis when a run suspends.

What's in this release

Keep runtime hydration repository neutral

Exact runtime hydration now works from detached checkouts, requires the pinned version and checksum, and preserves an existing shared launcher.

What's in this release

Report actionable runtime bootstrap failures

Boatstack now reports typed missing-runtime diagnostics with the exact pinned release and a confirmation-gated installation command. Generated Flow skills preserve the blocker and never install automatically.

What's in this release

Continue repository-resolved Flow steps

Repository Flow runs now bind declared repository inputs when the supervisor selects a single parameterized transition. Human questions and ambiguous candidates remain suspended.

What's in this release

Reliable delegated worktree publication

Delivery runs now carry their approved plan into a created worktree and can create pull requests noninteractively with the reviewed preview body.

What's in this release

Repository-owned run delegation

Repository Flows can request one human-approved autonomy grant for an exact run. Boatstack preserves mandatory provider authority and checks revocation, expiry, context, and program identity before each effect.

What's in this release

Make Flow lifecycle policy repository-owned

Flow targets now remain repository-defined runtime identities, and the software-delivery SDK exports trusted mechanisms instead of built-in run or abandonment lifecycle presets.

What's in this release

Replace a bound Flow run safely

Repository Flows can now expose explicit abandonment before starting a replacement delivery. Inbox changes cannot retarget an active run.

What's in this release

Repository-owned Flow entries

Repositories can compile typed Control Programs and expose their own named Flow entries to Codex and Claude without adding delivery modes to Boatstack.