Function insert_sql_outcome_with_cursor 

pub fn insert_sql_outcome_with_cursor(
    conn: &Connection,
    key: &str,
    result: &str,
    run_id: Option<&str>,
    request: Option<&str>,
    cursor: Option<&str>,
    created_at: i64,
) -> Result<(), BookkeepingError>

insert_sql_outcome with an exact cursor written atomically. Standalone WAL2 commits use this form because their next TxId is known inside the open transaction; the HCTree master continues to insert a run id and backfill its engine-assigned cursor after commit.