integration.lssm-os-state-git

@lssm-tech/integration.lssm-os-state-git

Atomic, Git-trackable persistence for LSSM OS desired/observed state, plans, and append-only receipts. The adapter writes canonical JSON, keeps revision history immutable, rejects revision equivocation, and uses scoped filesystem locks and atomic renames for current pointers.

Lock ownership uses an atomically created directory with a unique owner token. Claims do not expire or depend on wall-clock age: a contender cannot overlap an active owner after a clock jump or stale heartbeat, and a claimant only removes its own token. Crash residue fails closed and must be pruned during explicit offline maintenance. Data files are synced before publication and containing directories are synced after link, rename, or unlink. Directory fsync is best-effort only on filesystems that explicitly report it unsupported; file-level durability and atomic publication remain enforced there.

The adapter rejects symlink roots and symlink ancestors for all state and lock paths. Deploy it on a filesystem whose state root is writable only by the Runtime Node process; filesystem permission boundaries remain part of the operator threat model.

The configured root is data, not a credential location. Consumers decide when and how the resulting files are committed or synchronized with Git.