Update docs for the helper script refactor

Update the build and developer docs to match the new helper scripts:
- Replace lncfg/lnbuild with the consolidated bin/lnbld and use
  --install-dir; drop the removed --update-shell flag.
- Update lnrun usage to the new flag/key=value syntax (--test, --debug,
  --docs program=, --help <command>).
- Replace the black/isort/flake8 instructions with the ruff-based
  bin/lnchk --fmt / --chk-fmt flow, which also covers clang-format.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: thilinarmtb

docs/build.rst

@@ -40,9 +40,9 @@ Similarly, you can install the dev dependencies with mamba as well:
    mamba env create -f environment-dev.yml
    mamba activate libnomp-dev
 
-Use `lncfg` to configure CMake build and `lnbuild` to build/install `libnomp`. To
-see the available options, check out `lncfg --help`. `libnomp` currently supports
-the following backends:
+Use `lnbld` to configure the CMake build and build/install `libnomp` in a single
+step. To see the available options, check out `lnbld --help`. `libnomp`
+currently supports the following backends:
 
 #. OpenCL
 #. CUDA
@@ -54,8 +54,7 @@ commands:
 .. code-block:: bash
 
    cd libnomp
-   ./lncfg --enable-opencl --install-prefix ${HOME}/.nomp
-   ./lnbuild
+   ./bin/lnbld --enable-opencl --install-dir ${HOME}/.nomp
 
 `NOMP_INSTALL_DIR` environment variable must be set to `libnomp` install directory
 or it should be passed as a command line argument using `--nomp-install-dir` during
@@ -69,45 +68,38 @@ variable with `NOMP_INSTALL_DIR/bin`.
    export PATH=${NOMP_INSTALL_DIR}/bin:${PATH}
 
 Setting the environment variable and adding `NOMP_INSTALL_DIR/bin` to `PATH` will
-enable you to use `lnrun` script without using its full path to open documentation,
-run tests, debug tests, etc. You can update the shell configuration file automatically
-by passing `--update-shell` to `lnbuild` script. You have to open a new shell in
-order for changes to take affect in case you update the shell configuration file.
+enable you to use the `lnrun` script without using its full path to open
+documentation, run tests, debug tests, etc.
 
-.. code-block:: bash
-
-   cd libnomp
-   ./lncfg --enable-opencl --install-prefix ${HOME}/.nomp
-   ./lnbuild --update-shell
-
-Use `lnbuild --help` to see all the available options supported by `lnbuild` script.
+Use `lnbld --help` to see all the available options supported by the `lnbld`
+script.
 
 You might additionally want to specify OpenCL library path as below if CMake
 can't find OpenCL:
 
 .. code-block:: bash
 
-   ./lncfg --enable-opencl --opencl-lib /lib/x86_64-linux-gnu/libOpenCL.so
+   ./bin/lnbld --enable-opencl --opencl-lib /lib/x86_64-linux-gnu/libOpenCL.so
 
 If you used `conda` to install OpenCL (for example `pocl`_), do the following:
 
 .. code-block:: bash
 
-   ./lncfg --enable-opencl --opencl-lib ${CONDA_PREFIX}/lib/libOpenCL.so --opencl-headers ${CONDA_PREFIX}/include
+   ./bin/lnbld --enable-opencl --opencl-lib ${CONDA_PREFIX}/lib/libOpenCL.so --opencl-headers ${CONDA_PREFIX}/include
 
 
 Run `libnomp` tests
 -------------------
 
-You can run `libnomp` tests by executing `lnrun test` command. See below for
-a few examples on how to use the script:
+You can run `libnomp` tests by executing the `lnrun --test` command. See below
+for a few examples on how to use the script:
 
 .. code-block:: bash
 
-   lnrun test
-   lnrun test --backend opencl
+   lnrun --test
+   lnrun --test backend=opencl
 
-Use `lnrun help` to see all supported options.
+Use `lnrun --help test` to see all supported options.
 
 nompcc
 ------
@@ -166,22 +158,22 @@ Documentation
 
 We use `Doxygen` for in source documentations and render those with `Sphinx`
 and `Breathe`. These packages must be available if you install the dev
-dependencies using `conda`. You can enable docs by passing either `-docs` or
-`--enable-docs` option to `lncfg` script.
+dependencies using `conda`. You can enable docs by passing the `--enable-docs`
+option to the `lnbld` script.
 
 .. code-block:: bash
 
-    ./lncfg --enable-docs
-    ./lnbuild
+    ./bin/lnbld --enable-docs
 
-Use `lnrun` to open the user documentation locally. You can specify the browser
-with option `--browser`. For example, to open the documentation in firefox:
+Use `lnrun --docs` to open the user documentation locally. You can specify the
+program used to open the documentation with the `program` option. For example,
+to open the documentation in firefox:
 
 .. code-block:: bash
 
-    lnrun docs --browser firefox
+    lnrun --docs program=firefox
 
-If you do not specify the browser, it opens the documentation in chrome by
+If you do not specify the program, it opens the documentation with `open` by
 default.
 
 

docs/developer-docs.rst

@@ -52,24 +52,21 @@ instead of:
 Formatting files before committing
 ----------------------------------
 
-Run `clang-format` before committing any changes you make on the source files.
-`clang-format` will be available if you install the dev dependencies with conda.
-Run `clang-format` as follows:
+Run `lnchk --fmt` before committing any changes you make to the source files.
+This formats all C source files with `clang-format` and all python files with
+`ruff`. Both tools will be available if you install the dev dependencies with
+conda.
 
 .. code-block:: bash
 
-    clang-format -i **/*.[ch]
+    ./bin/lnchk --fmt
 
-If you change any python files, please use `black` and `isort` to format the
-python code and then check with `flake8` before committing. `black`, `isort`
-and `flake8`  will be available if you install the dev dependencies with
-conda.
+To only check the formatting (and run the `ruff` linter) without modifying any
+files, use `lnchk --chk-fmt`. This is the same check that is run in CI.
 
 .. code-block:: bash
 
-    black .
-    isort .
-    flake8
+    ./bin/lnchk --chk-fmt
 
 Debugging github actions
 ------------------------
@@ -105,15 +102,15 @@ As a prerequisite you have to install the `gdbserver` which you can install with
 
     sudo apt install gdbserver
 
-Use :code:`lnrun debug` command to host the debugging session. If you want to debug the
-test case `nomp-api-200`:
+Use the :code:`lnrun --debug` command to host the debugging session. If you want
+to debug the test case `nomp-api-200`:
 
 .. code-block:: bash
 
-    lnrun debug api-200
+    lnrun --debug api-200
 
 Additionally, you can set the port and the target device for the specific session.
-You can view the available options by :code:`lnrun help debug`.
+You can view the available options by :code:`lnrun --help debug`.
 
 By default the test starts on `localhost:5005`, and a debug viewer should be connected
 to this target address. For example, the following figure shows how clion connects to