Repository navigation
v3.5.3
What's new
Bug Fixes
The operation observer used to discover a single Git directory and reuse it for both command execution and filesystem reads. In repositories with a separate Git directory (core.worktree), that conflation meant commands resolved paths relative to .git while file hashing used repository-subpath semantics — snapshots could go stale or be reported unavailable, breaking readback and closure checks. This release (#735) splits command execution context from filesystem context: commands now use the discovered Git command directory, while file reads use the resolved worktree root. Tracked, staged, and untracked paths are now read with repository-root pathspec semantics (--full-name and :/) so snapshots stay repo-wide even when the command directory points at a subdirectory, submodule revision reads use absolute paths to avoid resolution drift, and remote readback operations share the same Git invocation root as local snapshot collection.
Continuous Integration
Renovate PR builds previously ran a separate artifact-generation step outside the normal build pipeline. That path is now consolidated into the standard build so Renovate PRs produce artifacts the same way any other PR does, and a postupgrade script/task was added now that bfra-me/renovate-action 10.1.0 supports allowed post-upgrade commands (#725). The Renovate and update-repo-settings workflows were also bumped to v4.16.44 (#734).
Documentation
Delegated receipt recovery is now documented under docs/solutions, capturing the recovery flow and aligning the worked example with the current source implementation (#723).