update snapshots

Author: x0rw

.github/auto-pr-tests/test_issue_01.snapshot

@@ -1,10 +1,7 @@
-================
-test gatest ga
-================
 =====CONTENT=====
 
 .. guideline:: test ga
-    :id: gui_irRvGs6pQsDQ 
+    :id: gui_3Wl9gOTto7p2 
     :category: advisory
     :status: draft
     :release: 1.1.1-1.1.1
@@ -16,13 +13,13 @@ test gatest ga
     hehehehe
 
     .. rationale:: 
-        :id: rat_dtzzrjsA2ShY 
+        :id: rat_PVjXjtM9G383 
         :status: draft
 
         test ga
 
     .. non_compliant_example::
-        :id: non_compl_ex_z824usgcSNr8 
+        :id: non_compl_ex_ABSVsT97MwLG 
         :status: draft
 
         test ga
@@ -32,7 +29,7 @@ test gatest ga
             dfhsdfkjshdfskdjhftest ga
 
     .. compliant_example::
-        :id: compl_ex_tzRbMfkM4NHX 
+        :id: compl_ex_Z9TjeDsRTnwL 
         :status: draft
 
         test ga

.github/auto-pr-tests/test_issue_02.snapshot

@@ -1,10 +1,7 @@
-================
-reduce-human-error
-================
 =====CONTENT=====
 
 .. guideline:: Recursive function are not allowed
-    :id: gui_NR0NkGkFOfEl 
+    :id: gui_9YIhwNMWWGvW 
     :category: required
     :status: draft
     :release: 1.3.0-latest
@@ -16,13 +13,13 @@ reduce-human-error
     Any function shall not call itself directly or indirectly
 
     .. rationale:: 
-        :id: rat_q7Vd2qfzZEpV 
+        :id: rat_ZaZYjwUzZzvU 
         :status: draft
 
         Recursive functions can easily cause stack overflows, which may result in exceptions or, in some cases, undefined behavior (typically some embedded systems). Although the Rust compiler supports `tail call optimization <https://en.wikipedia.org/wiki/Tail_call>`_\ , this optimization is not guaranteed and depends on the specific implementation and function structure. There is an `open RFC to guarantee tail call optimization in the Rust compiler <https://github.com/phi-go/rfcs/blob/guaranteed-tco/text/0000-explicit-tail-calls.md>`_\ , but this feature has not yet been stabilized. Until tail call optimization is guaranteed and stabilized, developers should avoid using recursive functions to prevent potential stack overflows and ensure program reliability.
 
     .. non_compliant_example::
-        :id: non_compl_ex_MjZZmMuITSnb 
+        :id: non_compl_ex_imbh3NpZjDSh 
         :status: draft
 
         The below function ``concat_strings`` is not complaint because it call itself and depending on depth of data provided as input it could generate an stack overflow exception or undefine behavior.
@@ -48,7 +45,7 @@ reduce-human-error
               }
 
     .. compliant_example::
-        :id: compl_ex_SdfkmboJ2Cih 
+        :id: compl_ex_fLIgZp7Lnwpb 
         :status: draft
 
         The following code implements the same functionality using iteration instead of recursion. The ``stack`` variable is used to maintain the processing context at each step of the loop. This approach provides explicit control over memory usage. If the stack grows beyond a predefined limit due to the structure or size of the input, the function returns an error rather than risking a stack overflow or out-of-memory exception. This ensures more predictable and robust behavior in resource-constrained environments.

.github/auto-pr-tests/test_issue_03.snapshot

@@ -1,10 +1,7 @@
-================
-numerics, reduce-human-error, maintainability, portability, surprising-behavior
-================
 =====CONTENT=====
 
 .. guideline:: Integer shift shall only be performed through `checked_` APIs
-    :id: gui_L1efkdhJroHY 
+    :id: gui_zMVugBA2A8hz 
     :category: mandatory
     :status: draft
     :release: 1.7.0-latest
@@ -32,7 +29,7 @@ numerics, reduce-human-error, maintainability, portability, surprising-behavior
     * ``isize``
 
     .. rationale:: 
-        :id: rat_eo9iSNAyUWop 
+        :id: rat_Ccy1VVgvSXVr 
         :status: draft
 
         This is directly inspired by `INT34-C. Do not shift an expression by a negative number of bits or by greater than or equal to the number of bits that exist in the operand <https://wiki.sei.cmu.edu/confluence/display/c/INT34-C.+Do+not+shift+an+expression+by+a+negative+number+of+bits+or+by+greater+than+or+equal+to+the+number+of+bits+that+exist+in+the+operand>`_.
@@ -95,7 +92,7 @@ numerics, reduce-human-error, maintainability, portability, surprising-behavior
         This API has consistent behavior across ``Debug`` and ``Release``\ , and makes the programmer intent explicit, which effectively solves this issue.
 
     .. non_compliant_example::
-        :id: non_compl_ex_4RnVPjQs06uM 
+        :id: non_compl_ex_keoHBPbqHD8t 
         :status: draft
 
         As seen below in the ``non_compliant_example()`` function:
@@ -131,7 +128,7 @@ numerics, reduce-human-error, maintainability, portability, surprising-behavior
               }
 
     .. compliant_example::
-        :id: compl_ex_n0Is3JLe1YwT 
+        :id: compl_ex_IG96LnSjFLTt 
         :status: draft
 
         As seen below in the ``compliant_example()`` function: