StackKits v0.24.27

Release notes for v0.24.27 are rendered from the current Unreleased changelog section.

Added

• stackkit service start|stop|restart|logs persists owner-signed desired state,
  redacts bounded logs, protects critical control-plane services, and exposes
  the same closed operations through StackAction for enrolled agents.

Changed

• Application rollout now completes independent components as
  completed_degraded, uses declared adapter fallbacks only before an external
  identity is committed, and verifies standalone Compose runtime state.
• Access manifests project desired state, allowed actions, and protected
  evidence references so orchestration UIs consume StackKits authority without
  a Coolify-specific mapping.
• Planner use-case tiles now materialize CUE-declared defaults and explicit
  alternatives; capacity controls use integer CPU/storage steps and 0.5-GiB RAM
  steps without coercing undeclared or off-grid input.

Fixed

• Keep the shared renderer transaction fixture aligned with the required host, maintenance, and redaction contracts so foundation changes exercise generation authorization instead of failing during compiler construction.
• Published GitHub Release notes now retain the exact private source SHA across
  draft creation, retry, and final changelog-note application, so first-party
  consumers can verify release provenance after publication.
• Public release publication now requires the exact numeric version to exist in
  this changelog. Fast pre-1.0 deliveries can no longer replace user-facing
  notes with a source-SHA placeholder.
• The missing public history for every existing v0.14.x and v0.15.x tag is
  restored, including patch releases that previously existed only as tags or
  GitHub Release objects.
• Coolify, Komodo, and Dokploy now retain an external deployment identity when
  a post-upsert deploy/readiness step fails, preventing a duplicate Compose
  fallback deployment.

Full Changelog: v0.16.8...v0.24.27

Built from 7f802289d057cbedb60e291bff8dd25083f180c9.