Skip to content

Citadel v1.4.5

Latest

Choose a tag to compare

@github-actions github-actions released this 04 Nov 18:36
3c317a0

Citadel v1.4.5 packages the reliability and security fixes merged since v1.4.4.

Security and upgrade notes

Repository-configured typechecks and loop trigger/verifier commands require machine-local approval for the exact project and command. Review the displayed approval command and run it interactively; hooks and agents cannot approve their own commands. Session-end cleanup and archive destinations are contained within the project, including paths with symlinked ancestors.

Fixes and improvements

  • Include all shared utilities so installed hooks can load frontmatter dependencies.
  • Preserve bundle activation checks for Citadel-namespaced plugin commands; foreign and unknown namespaces remain unknown.
  • Serialize concurrent scope claims and strengthen recovery identity, checkpoint evidence, uncertain-effect handling, and continuation concurrency.
  • Preserve authored project guidance and show the final dashboard decision from the complete log.
  • Retain the selected intent route when source or shell permission is missing and report blocked activation honestly.
  • Honor proposal-only app requests and the host effort setting before downstream build work.
  • Clarify source-only orchestration commands and local runner confirmations.
  • Scope live skill checks to Citadel, isolate account scheduling tools, and verify authored-file preservation.
  • Use the standard Intel macOS 26 CI pool, retaining Node 22/24 Linux, macOS, and Windows coverage.
  • Batch tagged release reads while preserving deterministic archives.
  • Add guarded delivery continuation and local-effect reconciliation to the source-only Operation Control CLI. The slim archive retains its documented consumer surface.

Thanks to @brandstaetter for the installed-hook dependency fix and security audit fixes.

Install and verify

Use the pinned installation instructions or download the complete archive, manifest, and SHA-256 trio below. Node.js 22 or newer is required.

Verify offline integrity and GitHub's signed provenance for all three assets as described in the release guide.

Full changelog