Add debugging API for the MOLE Grid 2.0 implementations

[Tony-Drummond]

Is your feature request related to a problem? Please describe.
Currently, all the MOLE Error handling system does not stop computation when errors are found, instead errors are stored and flagged for proper handling by the application programmer. There is a need to provide a debugging mode that will force the report of errors after a MOLE operation.

Describe the solution you'd like
A added feature, will provide user support for debugging. In debugging mode, errors will be sent to standard output and the program execution will be halted whenever there are errors after attempting a MOLE Grid operation.
We will overload current functional implementations by adding an extra boolean parameter-flag (debugging_mode) to all callable function in the C++ API.

[github-actions]

This issue has had no activity for 14 days. It will be marked stale in 14 days if there is no further activity.

[Tony-Drummond]

08/13/2026: JR and TD development notes

We will define the following MOLE library debug modes. The MOLE library has been designed in a way that it does not break the execution of a user code, instead it creates and maintains an error logging mechanism that allows users to check for possible errors after a MOLE operation. In addition, the logged errors can be reported to std output or to a file.

1. DEBUG_DEFAULT_MD (default behavior - returns a grid that has errors)
   .hasError (e.g., hasGridErrors())
   Users and application builders are responsible for checking for errors and implementing their error corrections.
   What support does a user get from the MOLE library at this point? A user can call MOLE functions to either:
   A – print the errors to standard output
   B – print errors to a file

2. DEBUG_REPORTS_STDOUT_MD (has to be passed to the MOLE API - returns an object that has errors )
   The MOLE library will report errors to standard output and return control to the users.
   What support does a user get from the MOLE library at this point? A user can call MOLE functions to either:
   A – print the errors to standard output
   B – print errors to a file

3. DEBUG_AND_ABORT_MD (Report, then abort so a debugger stops at that particular failure point, the difference is that this one aborts execution)
   The MOLE library will report errors to standard output and abort the execution (e.g., code exits).

Example: gridBuilder(“dim”,3, “m”,8, n…….”debug”, DEBUG_REPORTS_STDOUT_MD)