Replace Boatstack with the V2 delivery kernel

[bigboateng]

Summary

• replace the distributed V1 control paths with one authoritative 17-facet, 61-transition delivery kernel
• route CLI, hooks, SDK, MCP, shell, and host projections through the same observe → resolve → admit → effect → verify → receipt/recovery law
• remove V1 coexistence, migration, fallback, shadow-controller, and unmanaged-writer code in one flag-day cutover
• preserve failure knowledge as 22 typed historical fixtures and generate the readable catalog plus Locus safety/liveness models from the runtime registry
• canonicalize configuration authority across JSON formatting and checkout line endings while retaining native path identity and LF-stable generated artifacts

Why

Boatstack previously reconstructed lifecycle, identity, authority, recovery, and completion across multiple projections. Those partial views caused recurring deadlocks, ambiguous ownership, stale admission, self-invalidating success, and unsafe cleanup. V2 makes the executable kernel the single source of delivery truth.

Boundary conformance

• Boundary: every managed lifecycle transition and local or external effect
• Control law: an exact canonical snapshot, invocation identity, goal, parameters, current authority, and source revision must admit the registered transition before mutation; fresh observation must prove its target before a receipt can establish success
• Affected paths: runtime kernel, plant observer, effect transaction/recovery layer, public surfaces, installers, and release workflow
• Failure behavior: stale, ambiguous, conflicting, unauthorized, interrupted, or unknown outcomes fail closed into refusal, bounded recovery, reconciliation, frontier, or safe abandonment
• Evidence: completeness source inventory, reducer coverage, consumer parity, fault injection, integration tests, repository contracts, historical scenarios, and generated-model drift checks
• Residual risk: real provider behavior and platform crash semantics remain bounded by adapters, restart tests, and CI rather than claimed as exhaustively model-checked

Validation

• go test ./...
• go test -race ./...
• go vet ./... and go build ./...
• 89 Go tests across 10 isolated shards
• 22 repository/install/document contract tests
• darwin, linux, and windows builds for amd64 and arm64
• Bash installer syntax and base-aware release-note preflight
• Locus safety, guard-essentiality, nonblockingness/coreachability, and event-completeness checks over the generated 61-event model

Windows CI supplies the PowerShell parser check because pwsh is not installed locally.

Prerelease testing

The release workflow can publish explicit exact-source release candidates from an open branch. It rejects stable-looking manual tags, existing tags, tag refs, and moved branch heads.

Release note

Added release-notes/2026-08-10-v2-delivery-kernel.md.