doc(vector_test_description): rm all references

Author: rouson

README.md

@@ -251,12 +251,10 @@ GCC `gfortran`   | 13, 14, 15               | see 1 below
 Intel `ifx`      | 2025.1.1 Build 20250418  | see 2 below
 
 1. `gfortran` issues:
-   - With GCC 14 or earlier, the `test_description_t` constructor's
+   - With GCC 14.2.0 or earlier, the `test_description_t` constructor's
      `diagnosis_function` actual argument must be a procedure pointer conforming
      conforming with the `diagnosis_function_i` abstract interface.
-   - The `string_t` `bracket` type-bound function crashes for GCC 14 or earlier.
-   - _Deprecated feature_: Each element of a [`vector_test_description_t`] array
-     must be defined in a separate statement.
+   - The `string_t` `bracket` type-bound function crashes for GCC 14.2.0 or earlier.
 2. `ifx` issue:
    - Two `string_t` tests fail as described in issue [#51].
 
@@ -317,5 +315,4 @@ See our online [documentation] or build the documentation locally by installing
 [Garden]: https://gitlab.com/everythingfunctional/garden
 [handy-dandy]: https://github.com/rouson/handy-dandy/blob/7caaa4dc3d6e5331914a3025f0cb1db5ac1a886f/src/fresh-llvm-build.sh
 [Sourcery]: https://github.com/sourceryinstitute/sourcery
-[`vector_test_diagnosis_i`]: https://github.com/BerkeleyLab/julienne/blob/37bcc959efa8f9e27ae50fecfd37a6bf52ef0a43/src/julienne/julienne_vector_test_description_m.F90#L18
 [Veggies]: https://gitlab.com/everythingfunctional/veggies

demo/README.md

@@ -115,7 +115,7 @@ Skipping Tests
 --------------
 When a test is known to cause a compile-time or runtime crash in a specific scenario, e.g., with a specific compiler or compiler version, including that test will prevent the test suite from building or running to completion.
 It can be useful to skip a test with the problematic compiler but to report the test as skipped and account for the skipped tests in the tally of test results.
-For this purpose, the `test_description_t` and `vector_test_description_t` constructor functions have optional second arguments `diagnosis_function` and `vector_diagnosis_function`, respectively.
+For this purpose, the `test_description_t` constructor function has a `diagnosis_function` argument that is optional.
 When these arguments are not `present`, the `test_t`'s `report` procedure will report the test as skipped but will terminate normally as long as the sum of the passing tests and skipped tests equals the total number of tests.
 One might accomplish this with the compiler's predefined preprocessor macro:
 ```
@@ -159,29 +159,3 @@ class string_t{
     base_name(string_t) string_t
 }
 ```
-
-Deprecated: Vector Diagnosis Function
--------------------------------------
-Julienne's `vector_diagnosis_function_i` abstract interface and the corresponding `vector_test_description_t` type were developed before Julienne's `operator(.all.)` and `operator(.and.)`.
-Because the operators replace the interface and type with simpler functionality, it is likely that a future release will remove the `vector_*` entities.
-
-The Unified Modeling Language ([UML](https://wikipedia.org/Unified_modeling_language)) class diagram below depicts the class relationships involved when test function performs multiple checks and defines a result containing an array of corresponding `test_diagnosis_t` objects:
-```mermaid
- %%{init: { 'theme':'default',  "class" : {"hideEmptyMembersBox": true} } }%%
-classDiagram
-
-class vector_test_description_t{
-    vector_test_description_t(description : string_t[1..*], vector_diagnosis_function : vector_diagnosis_function_i)
-    run() test_result_t[1..*]
-}
-vector_test_description_t --> test_diagnosis_t : run() invokes vector_diagnosis_function to construct array of
-vector_test_description_t --> test_result_t : run() uses test_diagnostics_t array to construct array of
-
-class test_result_t{
-    test_result_t(test_passed : logical, diagnosis : test_diagnosis_t)
-}
-
-class test_diagnosis_t{
-    test_diagnosis_t(test_passed : logical, diagnostics_string : string_t)
-}
-```

doc/uml/class-diagram.md

@@ -5,7 +5,6 @@ classDiagram
 
 test_t --> test_result_t : produces
 test_description_t --> test_diagnosis_t : "'run' uses to construct test_result_t"
-vector_test_description_t --> test_diagnosis_t : "'run' uses to construct test_result_t array"
 test_result_t --> test_diagnosis_t : "accepts as constructor argument"
 
 class test_t{
@@ -54,10 +53,3 @@ class test_description_t{
     + contains_text(string_t) logical
     + operator(==) logical
 }
-
-class vector_test_description_t{
-    + vector_test_description_t(description : string_t, vector_diagnosis_function : procedure(vector_diagnosis_function_i)) test_description_t
-    + run() test_result_t
-    + contains_text(character) logical
-    + contains_text(string_t) logical
-}