Method try_lock_shadow_commit

atomic-repository/src/repository/materialize.rs:55–68

Return the first working-copy file that still contains an unresolved conflict marker, as `(path, 1-based line)`, or `None` if the working copy is clean. This scans the same status entries `record` guards on (Added / Modified / Conflicted) with the same detector (`first_conflict_marker_line`), so `atomic record` and `atomic git push` agree on what counts as a conflicted working copy (SPEC §5.4). I

(&self)

    /// partial staging. It is a distinct lock from the deferred-tree alignment
    /// lock and is meant to be taken **outermost**, before any DB write txn.
    pub fn try_lock_shadow_commit(&self) -> Result<Option<std::fs::File>, RepositoryError> {
        use fs2::FileExt;
        let lock = std::fs::OpenOptions::new()
            .create(true)
            .truncate(false)
            .read(true)
            .write(true)
            .open(self.dot_dir.join("shadow-commit.lock"))?;
        match lock.try_lock_exclusive() {
            Ok(()) => Ok(Some(lock)),
            Err(e) if is_lock_contended(&e) => Ok(None),
            Err(e) => Err(RepositoryError::Io(e)),
        }
    }

    pub fn first_working_copy_conflict_marker(
        &self,