Klever

We found out that the best way to develop specifications is to install Bridge in the development mode, edit those specifications directly within the repository using some IDE/editory and then create and decide new verification jobs that automatically catch all the local changes. One issue with that is Bridge always use the default decision configuration unlike for new job versions for which it suggests decision configurations of previous versions automatically. The latter may be very convenient for powerful machines where users can use, say, more parallel workers to get verification results much faster. We couldn't follow the same logic for verification jobs since they can differ much and it is not safe to implicitly select the latest decision configuration, but we can reduce user's effort by providing an ability to use current job decision configuration by default. I suggest to relate this choice with a user profile since different users can have different preferences.