Retain axioms in background knowledge beyond the debugging session life cycle

Once the user has moved some axioms from the knowledge base (set of possibly faulty axiom) to the background (correct axioms) and causes a reset of the debugging session state (by either stopping/finishin a debugging session or restarting a session, reloading the ontology, changing preference settings, changing the reasoner, etc), the axioms that have been manually defined as correct axioms (background) are again automatically declared as possibly faulty.

This requires the user to move them again once she desires to restart a debugging session with the same precondition from the previous debugging session.

Find a way to keep this information (which axioms are supposed to be correct) such that the user does not have to do this again from scratch.