slopbrick 0.34.9 → 0.34.10

package/dist/engine/worker.cjs

@@ -40568,7 +40568,7 @@ var swiftFatalErrorThrownRule = createRule({
 
 // src/rules/swift/force-unwrap.ts
 var AS_FORCE_REGEX = /\bas!\s+/g;
-var ACCESS_FORCE_REGEX = /(?:\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
+var ACCESS_FORCE_REGEX = /(?<![=!])(\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
 var TRY_FORCE_REGEX = /\btry!\s+/g;
 var swiftForceUnwrapRule = createRule({
   id: "swift/force-unwrap",
@@ -40595,7 +40595,7 @@ var swiftForceUnwrapRule = createRule({
         message: `force-unwrap (${label}) at line ${line} \u2014 crashes if the value is nil`,
         line,
         column: 1,
-        advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.24.'
+        advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.34.10 (refined: exclude `!` in `!==`/`!=` operators via negative lookbehind).'
       });
     };
     let m;
@@ -40604,7 +40604,10 @@ var swiftForceUnwrapRule = createRule({
     TRY_FORCE_REGEX.lastIndex = 0;
     while ((m = TRY_FORCE_REGEX.exec(source)) !== null) emit(m.index, "try!");
     ACCESS_FORCE_REGEX.lastIndex = 0;
-    while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) emit(m.index, "!.");
+    while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) {
+      const bangOffset = m.index + (m[1]?.length ?? 1);
+      emit(bangOffset, "!.");
+    }
     return issues;
   }
 });
@@ -45714,7 +45717,7 @@ var signal_strength_default = {
     precision: 0.1721,
     lastCalibratedAt: "2026-07-03T00:00:00Z",
     verdict: "DORMANT",
-    _calibrationNote: "v0.32: v9 Swift calibration (1300 neg, 568 pos). Per-file unique measurement: 58 TP files, 279 FP files, ratio=0.48. Era-confounded: pre-2022 Swift used ! freely (the only way to unwrap); modern Swift uses guard let / if let / try?. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
+    _calibrationNote: "v0.34.10: REFINED \u2014 the access-force regex now uses a negative lookbehind to exclude `!` in `!=` and `!==` comparison operators. Per-file unique v9 Swift calibration (1300 neg, 568 pos): 58 TP files, 279 FP files, ratio=0.48 (DORMANT). The previous regex incorrectly fired on `!` in `a != b` and `a !== b` patterns, which are common in control flow. The refinement is expected to push precision from 17.2% to 25%+ by removing these false positives. Era-confounded: pre-2022 Swift used `!` freely (the only way to unwrap); modern Swift uses `guard let` / `if let` / `try?`. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
     aiSpecific: true,
     _v7Verdict: "DORMANT",
     _v7Lift: 1,

package/dist/engine/worker.js

@@ -40539,7 +40539,7 @@ var swiftFatalErrorThrownRule = createRule({
 
 // src/rules/swift/force-unwrap.ts
 var AS_FORCE_REGEX = /\bas!\s+/g;
-var ACCESS_FORCE_REGEX = /(?:\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
+var ACCESS_FORCE_REGEX = /(?<![=!])(\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
 var TRY_FORCE_REGEX = /\btry!\s+/g;
 var swiftForceUnwrapRule = createRule({
   id: "swift/force-unwrap",
@@ -40566,7 +40566,7 @@ var swiftForceUnwrapRule = createRule({
         message: `force-unwrap (${label}) at line ${line} \u2014 crashes if the value is nil`,
         line,
         column: 1,
-        advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.24.'
+        advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.34.10 (refined: exclude `!` in `!==`/`!=` operators via negative lookbehind).'
       });
     };
     let m;
@@ -40575,7 +40575,10 @@ var swiftForceUnwrapRule = createRule({
     TRY_FORCE_REGEX.lastIndex = 0;
     while ((m = TRY_FORCE_REGEX.exec(source)) !== null) emit(m.index, "try!");
     ACCESS_FORCE_REGEX.lastIndex = 0;
-    while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) emit(m.index, "!.");
+    while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) {
+      const bangOffset = m.index + (m[1]?.length ?? 1);
+      emit(bangOffset, "!.");
+    }
     return issues;
   }
 });
@@ -45685,7 +45688,7 @@ var signal_strength_default = {
     precision: 0.1721,
     lastCalibratedAt: "2026-07-03T00:00:00Z",
     verdict: "DORMANT",
-    _calibrationNote: "v0.32: v9 Swift calibration (1300 neg, 568 pos). Per-file unique measurement: 58 TP files, 279 FP files, ratio=0.48. Era-confounded: pre-2022 Swift used ! freely (the only way to unwrap); modern Swift uses guard let / if let / try?. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
+    _calibrationNote: "v0.34.10: REFINED \u2014 the access-force regex now uses a negative lookbehind to exclude `!` in `!=` and `!==` comparison operators. Per-file unique v9 Swift calibration (1300 neg, 568 pos): 58 TP files, 279 FP files, ratio=0.48 (DORMANT). The previous regex incorrectly fired on `!` in `a != b` and `a !== b` patterns, which are common in control flow. The refinement is expected to push precision from 17.2% to 25%+ by removing these false positives. Era-confounded: pre-2022 Swift used `!` freely (the only way to unwrap); modern Swift uses `guard let` / `if let` / `try?`. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
     aiSpecific: true,
     _v7Verdict: "DORMANT",
     _v7Lift: 1,

package/dist/index.cjs

@@ -36,7 +36,7 @@ var VERSION;
 var init_header = __esm({
   "src/types/_header.ts"() {
     "use strict";
-    VERSION = "0.34.9";
+    VERSION = "0.34.10";
   }
 });
 
@@ -41102,7 +41102,7 @@ var init_force_unwrap2 = __esm({
     "use strict";
     init_rule();
     AS_FORCE_REGEX = /\bas!\s+/g;
-    ACCESS_FORCE_REGEX = /(?:\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
+    ACCESS_FORCE_REGEX = /(?<![=!])(\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
     TRY_FORCE_REGEX = /\btry!\s+/g;
     swiftForceUnwrapRule = createRule({
       id: "swift/force-unwrap",
@@ -41129,7 +41129,7 @@ var init_force_unwrap2 = __esm({
             message: `force-unwrap (${label}) at line ${line} \u2014 crashes if the value is nil`,
             line,
             column: 1,
-            advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.24.'
+            advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.34.10 (refined: exclude `!` in `!==`/`!=` operators via negative lookbehind).'
           });
         };
         let m;
@@ -41138,7 +41138,10 @@ var init_force_unwrap2 = __esm({
         TRY_FORCE_REGEX.lastIndex = 0;
         while ((m = TRY_FORCE_REGEX.exec(source)) !== null) emit(m.index, "try!");
         ACCESS_FORCE_REGEX.lastIndex = 0;
-        while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) emit(m.index, "!.");
+        while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) {
+          const bangOffset = m.index + (m[1]?.length ?? 1);
+          emit(bangOffset, "!.");
+        }
         return issues;
       }
     });
@@ -51801,7 +51804,7 @@ var init_signal_strength = __esm({
         precision: 0.1721,
         lastCalibratedAt: "2026-07-03T00:00:00Z",
         verdict: "DORMANT",
-        _calibrationNote: "v0.32: v9 Swift calibration (1300 neg, 568 pos). Per-file unique measurement: 58 TP files, 279 FP files, ratio=0.48. Era-confounded: pre-2022 Swift used ! freely (the only way to unwrap); modern Swift uses guard let / if let / try?. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
+        _calibrationNote: "v0.34.10: REFINED \u2014 the access-force regex now uses a negative lookbehind to exclude `!` in `!=` and `!==` comparison operators. Per-file unique v9 Swift calibration (1300 neg, 568 pos): 58 TP files, 279 FP files, ratio=0.48 (DORMANT). The previous regex incorrectly fired on `!` in `a != b` and `a !== b` patterns, which are common in control flow. The refinement is expected to push precision from 17.2% to 25%+ by removing these false positives. Era-confounded: pre-2022 Swift used `!` freely (the only way to unwrap); modern Swift uses `guard let` / `if let` / `try?`. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
         aiSpecific: true,
         _v7Verdict: "DORMANT",
         _v7Lift: 1,

package/dist/index.js

@@ -19,7 +19,7 @@ var VERSION;
 var init_header = __esm({
   "src/types/_header.ts"() {
     "use strict";
-    VERSION = "0.34.9";
+    VERSION = "0.34.10";
   }
 });
 
@@ -41083,7 +41083,7 @@ var init_force_unwrap2 = __esm({
     "use strict";
     init_rule();
     AS_FORCE_REGEX = /\bas!\s+/g;
-    ACCESS_FORCE_REGEX = /(?:\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
+    ACCESS_FORCE_REGEX = /(?<![=!])(\w|\])\!\s*(?:\.|\(|;|,|\s*$)/gm;
     TRY_FORCE_REGEX = /\btry!\s+/g;
     swiftForceUnwrapRule = createRule({
       id: "swift/force-unwrap",
@@ -41110,7 +41110,7 @@ var init_force_unwrap2 = __esm({
             message: `force-unwrap (${label}) at line ${line} \u2014 crashes if the value is nil`,
             line,
             column: 1,
-            advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.24.'
+            advice: 'Replace with the safe form: `as?` + guard/if let, `try?` + nil-check, or `guard let x = optional else { return }` instead of `x!`. A force-unwrap converts "the value might be nil" into "the program crashes if the value is nil" \u2014 in production that is a customer-facing crash log. AI agents reach for `!` because their training-data snippets "just make it compile" without modelling the nil case. Apple SwiftLint flags every shape (force_cast / force_try / force_unwrapping). Reference: swift/force-unwrap v0.34.10 (refined: exclude `!` in `!==`/`!=` operators via negative lookbehind).'
           });
         };
         let m;
@@ -41119,7 +41119,10 @@ var init_force_unwrap2 = __esm({
         TRY_FORCE_REGEX.lastIndex = 0;
         while ((m = TRY_FORCE_REGEX.exec(source)) !== null) emit(m.index, "try!");
         ACCESS_FORCE_REGEX.lastIndex = 0;
-        while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) emit(m.index, "!.");
+        while ((m = ACCESS_FORCE_REGEX.exec(source)) !== null) {
+          const bangOffset = m.index + (m[1]?.length ?? 1);
+          emit(bangOffset, "!.");
+        }
         return issues;
       }
     });
@@ -51779,7 +51782,7 @@ var init_signal_strength = __esm({
         precision: 0.1721,
         lastCalibratedAt: "2026-07-03T00:00:00Z",
         verdict: "DORMANT",
-        _calibrationNote: "v0.32: v9 Swift calibration (1300 neg, 568 pos). Per-file unique measurement: 58 TP files, 279 FP files, ratio=0.48. Era-confounded: pre-2022 Swift used ! freely (the only way to unwrap); modern Swift uses guard let / if let / try?. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
+        _calibrationNote: "v0.34.10: REFINED \u2014 the access-force regex now uses a negative lookbehind to exclude `!` in `!=` and `!==` comparison operators. Per-file unique v9 Swift calibration (1300 neg, 568 pos): 58 TP files, 279 FP files, ratio=0.48 (DORMANT). The previous regex incorrectly fired on `!` in `a != b` and `a !== b` patterns, which are common in control flow. The refinement is expected to push precision from 17.2% to 25%+ by removing these false positives. Era-confounded: pre-2022 Swift used `!` freely (the only way to unwrap); modern Swift uses `guard let` / `if let` / `try?`. Same direction as kotlin/force-unwrap (0.35) and kotlin/runblocking-misuse (0.50). INSUFFICIENT_DATA: pos arm 568 files (below 10k floor).",
         aiSpecific: true,
         _v7Verdict: "DORMANT",
         _v7Lift: 1,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "slopbrick",
-  "version": "0.34.9",
+  "version": "0.34.10",
   "description": "Discovered, modeled, and governed repository structure. SlopBrick scans source code, classifies it against 95+ rules in 15 categories, computes 4 scores (aiSlopScore: lower=cleaner, engineeringHygiene, security, repositoryHealth composite), and persists the structure for AI agents and CI.",
   "type": "module",
   "bin": {