[skip ci] doc: update generated wiki pages (wiki/Linter.md,wiki/[Linting Rule] Dead Code.md)

Author: actions-user

wiki/[Linting Rule] Dead Code.md

@@ -1,4 +1,4 @@
-_This document was generated from '[src/documentation/wiki-linter.ts](https://github.com/flowr-analysis/flowr/tree/main//src/documentation/wiki-linter.ts)' on 2026-01-03, 16:58:45 UTC presenting an overview of flowR's linter (v2.7.6). Please do not edit this file/wiki page directly._
+_This document was generated from '[src/documentation/wiki-linter.ts](https://github.com/flowr-analysis/flowr/tree/main//src/documentation/wiki-linter.ts)' on 2026-01-22, 13:24:22 UTC presenting an overview of flowR's linter (v2.8.9). Please do not edit this file/wiki page directly._
 <h2 id="dead-code">Dead Code&emsp;<sup>[<a href="https://github.com/flowr-analysis/flowr/wiki/Linter">overview</a>]</sup></h2>
 
 <span title="This rule is used to detect issues that do not directly affect the semantics of the code, but are still considered bad practice."><a href='#smell'>![smell](https://img.shields.io/badge/smell-yellow) </a></span> <span title="This rule is used to detect issues that are related to the reproducibility of the code. For example, missing or incorrect random seeds, or missing data."><a href='#reproducibility'>![reproducibility](https://img.shields.io/badge/reproducibility-teal) </a></span> <span title="This rule is used to detect issues that are related to the (re-)usability of the code. For example, missing or incorrect error handling, or missing or incorrect user interface elements."><a href='#usability'>![usability](https://img.shields.io/badge/usability-teal) </a></span>
@@ -41,16 +41,16 @@ The linting query can be used to run this rule on the above example:
 
 _Results (prettified and summarized):_
 
-Query: **linter** (0 ms)\
+Query: **linter** (1 ms)\
 &nbsp;&nbsp;&nbsp;╰ **Dead Code** (dead-code):\
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;╰ certain:\
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;╰ Code at 1.17\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;╰ _Metadata_: <code>consideredNodes: 7, searchTimeMs: 0, processTimeMs: 0</code>\
-_All queries together required ≈0 ms (1ms accuracy, total 2 ms)_
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;╰ _Metadata_: <code>consideredNodes: 7, searchTimeMs: 1, processTimeMs: 0</code>\
+_All queries together required ≈1 ms (1ms accuracy, total 1 ms)_
 
 <details> <summary style="color:gray">Show Detailed Results as Json</summary>
 
-The analysis required _2.1 ms_ (including parsing and normalization and the query) within the generation environment.
+The analysis required _0.7 ms_ (including parsing and normalization and the query) within the generation environment.
 
 In general, the JSON contains the Ids of the nodes in question as they are present in the normalized AST or the dataflow graph of flowR.
 Please consult the [Interface](https://github.com/flowr-analysis/flowr/wiki/Interface) wiki page for more information on how to get those.
@@ -76,17 +76,17 @@ Please consult the [Interface](https://github.com/flowr-analysis/flowr/wiki/Inte
         ],
         ".meta": {
           "consideredNodes": 7,
-          "searchTimeMs": 0,
+          "searchTimeMs": 1,
           "processTimeMs": 0
         }
       }
     },
     ".meta": {
-      "timing": 0
+      "timing": 1
     }
   },
   ".meta": {
-    "timing": 0
+    "timing": 1
   }
 }
 ```
@@ -225,13 +225,101 @@ if(TRUE) 1; stopifnot(FALSE); 2
 We expect the linter to report the following:
 
 ```ts
- certainty: LintingResultCertainty.Certain, range: [1, 13, 1, 28] },
-{ certainty: LintingResultCertainty.Certain, range: [1, 31, 1, 31] },
+ certainty: LintingResultCertainty.Certain, range: [1, 31, 1, 31] },
 ```
 
 
 See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L23) for the test-case implementation.
 
+<h4 id="Test_Case:_stop_condition">Test Case: stop condition</h4>
+
+
+Given the following input:
+
+```r
+`
+x <- 2
+
+if(u) {
+  stop(42)
+  x <- 3
+}
+
+print(2)
+`
+```
+
+
+
+We expect the linter to report the following:
+
+```ts
+ certainty: LintingResultCertainty.Certain, range: [6, 3, 6, 8]
+```
+
+
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L26) for the test-case implementation.
+		
+<h4 id="Test_Case:_return">Test Case: return</h4>
+
+
+Given the following input:
+
+```r
+return(); 2
+```
+
+
+
+We expect the linter to report the following:
+
+```ts
+ certainty: LintingResultCertainty.Certain, range: [1,11,1,11]
+```
+
+
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L38) for the test-case implementation.
+		
+<h4 id="Test_Case:_try">Test Case: try</h4>
+
+
+Given the following input:
+
+```r
+try(stop(1)); 2
+```
+
+
+
+We expect the linter to report the following:
+
+```ts
+* no lints
+```
+
+
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L41) for the test-case implementation.
+		
+<h4 id="Test_Case:_try_complex">Test Case: try complex</h4>
+
+
+Given the following input:
+
+```r
+f <- function() { try(stop(1)); 2 }; f(); stop(1); 2
+```
+
+
+
+We expect the linter to report the following:
+
+```ts
+ certainty: LintingResultCertainty.Certain, range: [1, 52, 1, 52]
+```
+
+
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L42) for the test-case implementation.
+		
 <h4 id="Test_Case:_always">Test Case: always</h4>
 
 
@@ -250,7 +338,7 @@ We expect the linter to report the following:
 ```
 
 
-See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L30) for the test-case implementation.
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L48) for the test-case implementation.
 
 <h4 id="Test_Case:_never">Test Case: never</h4>
 
@@ -270,7 +358,7 @@ We expect the linter to report the following:
 ```
 
 
-See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L33) for the test-case implementation.
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L51) for the test-case implementation.
 
 <h4 id="Test_Case:_TRUE_FALSE">Test Case: TRUE FALSE</h4>
 
@@ -290,7 +378,7 @@ We expect the linter to report the following:
 ```
 
 
-See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L39) for the test-case implementation.
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L57) for the test-case implementation.
 
 <h4 id="Test_Case:_FALSE_FALSE">Test Case: FALSE FALSE</h4>
 
@@ -311,7 +399,7 @@ We expect the linter to report the following:
 ```
 
 
-See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L42) for the test-case implementation.
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L60) for the test-case implementation.
 		
 <h4 id="Test_Case:_FALSE_TRUE">Test Case: FALSE TRUE</h4>
 
@@ -332,7 +420,7 @@ We expect the linter to report the following:
 ```
 
 
-See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L46) for the test-case implementation.
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L64) for the test-case implementation.
 		
 <h4 id="Test_Case:_after_infinite_repeat">Test Case: after infinite repeat</h4>
 
@@ -352,7 +440,7 @@ We expect the linter to report the following:
 ```
 
 
-See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L53) for the test-case implementation.
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L71) for the test-case implementation.
 		
 <h4 id="Test_Case:_after_infinite_while">Test Case: after infinite while</h4>
 
@@ -372,4 +460,4 @@ We expect the linter to report the following:
 ```
 
 
-See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L56) for the test-case implementation.
+See [here](https://github.com/flowr-analysis/flowr/tree/main//test/functionality/linter/lint-dead-code.test.ts#L74) for the test-case implementation.