pi-lens 3.8.73 → 4.0.0

package/dist/clients/source-groups.js

@@ -1,96 +0,0 @@
-export function partitionSourceFiles(sourceRoot, files, maxFiles = 12) {
-    if (maxFiles <= 0) {
-        throw new Error("maxFiles must be greater than zero");
-    }
-    return partitionAt(sourceRoot.replace(/\\/g, "/"), normalizeFiles(files), maxFiles, 0);
-}
-function normalizeFiles(files) {
-    return [...new Set(files.map((file) => file.replace(/\\/g, "/")))].sort((a, b) => a.localeCompare(b));
-}
-function partitionAt(sourceRoot, files, maxFiles, depth) {
-    if (files.length === 0)
-        return [];
-    if (files.length <= maxFiles) {
-        return [{ label: commonLabel(sourceRoot, files, depth), files }];
-    }
-    const directFiles = [];
-    const buckets = new Map();
-    for (const file of files) {
-        const relativePath = file.startsWith(`${sourceRoot}/`)
-            ? file.slice(sourceRoot.length + 1)
-            : file;
-        const parts = relativePath.split("/");
-        if (parts.length <= depth + 1) {
-            directFiles.push(file);
-            continue;
-        }
-        const segment = parts[depth];
-        if (!segment) {
-            directFiles.push(file);
-            continue;
-        }
-        const bucket = buckets.get(segment) ?? [];
-        bucket.push(file);
-        buckets.set(segment, bucket);
-    }
-    if (buckets.size === 0) {
-        return chunkFiles(currentLabel(sourceRoot, files, depth), files, maxFiles);
-    }
-    const groups = chunkFiles(currentLabel(sourceRoot, files, depth), directFiles, maxFiles);
-    for (const [segment, bucketFiles] of [...buckets.entries()].sort(([left], [right]) => left.localeCompare(right))) {
-        if (bucketFiles.length <= maxFiles) {
-            groups.push({
-                label: `${sourceRoot}/${bucketPrefix(bucketFiles, sourceRoot, depth, segment)}`,
-                files: bucketFiles,
-            });
-        }
-        else {
-            groups.push(...partitionAt(sourceRoot, bucketFiles, maxFiles, depth + 1));
-        }
-    }
-    return groups;
-}
-function chunkFiles(label, files, maxFiles) {
-    if (files.length === 0)
-        return [];
-    if (files.length <= maxFiles)
-        return [{ label, files }];
-    const chunks = [];
-    for (let index = 0; index < files.length; index += maxFiles) {
-        const part = Math.floor(index / maxFiles) + 1;
-        chunks.push({
-            label: `${label}#${part}`,
-            files: files.slice(index, index + maxFiles),
-        });
-    }
-    return chunks;
-}
-function currentLabel(sourceRoot, files, depth) {
-    if (depth === 0)
-        return sourceRoot;
-    const first = files[0];
-    if (!first)
-        return sourceRoot;
-    const relativePath = first.startsWith(`${sourceRoot}/`)
-        ? first.slice(sourceRoot.length + 1)
-        : first;
-    const parts = relativePath.split("/").slice(0, depth);
-    return parts.length === 0 ? sourceRoot : `${sourceRoot}/${parts.join("/")}`;
-}
-function commonLabel(sourceRoot, files, depth) {
-    if (depth === 0)
-        return sourceRoot;
-    if (files.length === 1)
-        return files[0] ?? sourceRoot;
-    return currentLabel(sourceRoot, files, depth);
-}
-function bucketPrefix(files, sourceRoot, depth, segment) {
-    const first = files[0];
-    if (!first || depth === 0)
-        return segment;
-    const relativePath = first.startsWith(`${sourceRoot}/`)
-        ? first.slice(sourceRoot.length + 1)
-        : first;
-    const parts = relativePath.split("/").slice(0, depth);
-    return [...parts, segment].join("/");
-}

package/dist/clients/types.js

@@ -1,11 +0,0 @@
-/**
- * LSP Types - Core types for the pi-local LSP client
- * Simplified from the full LSP spec to what we actually need
- */
-export var DiagnosticSeverity;
-(function (DiagnosticSeverity) {
-    DiagnosticSeverity[DiagnosticSeverity["Error"] = 1] = "Error";
-    DiagnosticSeverity[DiagnosticSeverity["Warning"] = 2] = "Warning";
-    DiagnosticSeverity[DiagnosticSeverity["Information"] = 3] = "Information";
-    DiagnosticSeverity[DiagnosticSeverity["Hint"] = 4] = "Hint";
-})(DiagnosticSeverity || (DiagnosticSeverity = {}));

package/docs/env_variables.md

@@ -1,10 +0,0 @@
-# Environment Variables
-
-See [`environment-variables.md`](environment-variables.md) for the full reference.
-
-Common variables:
-
-- `PILENS_DATA_DIR` — redirect per-project persistent state outside the workspace.
-- `PI_LENS_STARTUP_MODE` — choose `full`, `minimal`, or `quick` startup mode.
-- `PI_LENS_NO_CONTEXT_INJECTION=1` — keep tools, LSP, read-guard, and formatting
-  active while disabling automatic turn-end/session-start context injection.

package/rules/tree-sitter-queries/abap-disabled/delete-where.yml

@@ -1,46 +0,0 @@
-# ABAP DELETE Without WHERE
-# Detects DELETE statements without WHERE in ABAP
-id: delete-where
-name: DELETE FROM Should Have WHERE Clause
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: abap
-
-message: "DELETE FROM statement should have a WHERE clause"
-
-description: |
-  DELETE FROM without WHERE deletes ALL rows. Almost always a bug.
-
-  ✅ FIX: Add WHERE clause
-
-  ```abap
-  DELETE FROM employees WHERE id = lv_id.  " GOOD
-  ```
-
-query: |
-  (delete_statement
-    (delete) @DELETE
-    (from_clause)
-    (where_clause)? @WHERE)
-
-metavars:
-  - DELETE
-  - WHERE
-
-post_filter: missing_where
-
-tags:
-  - reliability
-  - abap
-  - data-loss
-
-examples:
-  bad: |
-    DELETE FROM employees.  " BAD
-
-  good: |
-    DELETE FROM employees WHERE id = 123.  " GOOD
-
-has_fix: false

package/rules/tree-sitter-queries/cpp/no-confused-move-forward.yml

@@ -1,59 +0,0 @@
-# No Confused std::move/std::forward
-# Detects potential confusion between std::move and std::forward
-id: no-confused-move-forward
-name: std::move and std::forward Should Not Be Confused
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: cpp
-
-message: "std::move and std::forward should not be confused"
-
-description: |
-  std::move unconditionally casts to rvalue, while std::forward
-  conditionally casts based on template parameter. Using the wrong
-  one can lead to subtle bugs and unexpected copies/moves.
-
-  ✅ FIX: Use std::move for known objects, std::forward for templates
-
-  ```cpp
-  template<typename T>
-  void process(T&& t) {
-      other(std::forward<T>(t));  // Correct - preserve value category
-  }
-  ```
-
-query: |
-  (call_expression
-    function: (qualified_identifier
-      name: (identifier) @FUNC
-      (#match? @FUNC "^(move|forward)$"))
-    arguments: (argument_list) @ARGS)
-
-post_filter: confused_move_forward
-
-metavars:
-  - FUNC
-  - ARGS
-
-tags:
-  - reliability
-  - cpp
-  - move-semantics
-  - cppcoreguidelines
-
-examples:
-  bad: |
-    template<typename T>
-    void wrapper(T&& t) {
-        return foo(std::move(t));  // BAD - breaks perfect forwarding
-    }
-
-  good: |
-    template<typename T>
-    void wrapper(T&& t) {
-        return foo(std::forward<T>(t));  // GOOD - preserves category
-    }
-
-has_fix: false

package/rules/tree-sitter-queries/cpp/noexcept-functions.yml

@@ -1,58 +0,0 @@
-# Noexcept Functions
-# Detects functions that should be noexcept
-id: noexcept-functions
-name: Exception-Unfriendly Functions Should Be noexcept
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: cpp
-
-message: "Function should be declared noexcept"
-
-description: |
-  Functions that don't throw exceptions should be marked noexcept.
-  This enables compiler optimizations and better error handling.
-  This is a MISRA C++ 2023 rule.
-
-  ✅ FIX: Add noexcept specifier
-
-  ```cpp
-  int add(int a, int b) noexcept {  // GOOD - noexcept
-      return a + b;
-  }
-  ```
-
-query: |
-  (function_definition
-    type: (primitive_type) @RET
-    (function_declarator
-      name: (identifier) @NAME)
-    body: (compound_statement) @BODY)
-
-metavars:
-  - RET
-  - NAME
-  - BODY
-
-post_filter: should_be_noexcept
-
-tags:
-  - reliability
-  - cpp
-  - misra-cpp2023
-  - performance
-
-examples:
-  bad: |
-    int add(int a, int b) {  // BAD - missing noexcept
-        return a + b;
-    }
-
-  good: |
-    int add(int a, int b) noexcept {  // GOOD
-        return a + b;
-    }
-
-has_fix: true
-fix_action: add_noexcept

package/rules/tree-sitter-queries/java/mockito-initialized.yml

@@ -1,66 +0,0 @@
-# Mockito Initialized
-# Detects annotated Mockito objects that may not be initialized
-id: mockito-initialized
-name: Annotated Mockito Objects Should Be Initialized
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: java
-
-message: "@Mock/@InjectMocks object should be initialized with MockitoAnnotations.openMocks()"
-
-description: |
-  @Mock, @Spy, @Captor, @InjectMocks fields must be initialized
-  before use. Call MockitoAnnotations.openMocks(this) in @Before
-  or use MockitoJUnitRunner.
-
-  ✅ FIX: Add initialization in @Before method
-
-  ```java
-  @Before
-  public void setUp() {
-      MockitoAnnotations.openMocks(this);  // GOOD
-  }
-  ```
-
-query: |
-  (field_declaration
-    (modifiers
-      (annotation
-        name: (identifier) @ANNOT (#match? @ANNOT "^(Mock|Spy|Captor|InjectMocks)$")))
-    (variable_declarator
-      name: (identifier) @FIELD))
-
-metavars:
-  - ANNOT
-  - FIELD
-
-post_filter: missing_mockito_init
-
-tags:
-  - reliability
-  - java
-  - mockito
-  - testing
-
-examples:
-  bad: |
-    @Mock
-    private Service service;  // BAD - not initialized
-
-    @Test
-    public void test() {
-        service.doSomething();  // NullPointerException!
-    }
-
-  good: |
-    @Mock
-    private Service service;
-
-    @Before
-    public void setUp() {
-        MockitoAnnotations.openMocks(this);  // GOOD
-    }
-
-has_fix: false

package/rules/tree-sitter-queries/java/no-wait-notify-on-thread.yml

@@ -1,58 +0,0 @@
-# No Wait/Notify on Thread
-# Detects wait(), notify(), notifyAll() called on Thread instances
-id: no-wait-notify-on-thread
-name: Wait/Notify Should Not Be Called on Thread Instances
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: java
-
-message: "{{METHOD}}() should not be called on Thread instances"
-
-description: |
-  Calling wait(), notify(), or notifyAll() on Thread objects can
-  conflict with the Thread's internal join mechanism, causing 
-  unexpected behavior. Use them on a separate lock object.
-
-  ✅ FIX: Use a dedicated lock object
-
-  ```java
-  private final Object lock = new Object();
-
-  synchronized (lock) {
-      lock.wait();  // GOOD - separate lock
-  }
-  ```
-
-query: |
-  (method_invocation
-    object: (identifier) @OBJ
-    name: (identifier) @METHOD
-    (#match? @METHOD "^(wait|notify|notifyAll)$"))
-
-metavars:
-  - METHOD
-  - OBJ
-
-post_filter: called_on_thread_instance
-
-tags:
-  - reliability
-  - java
-  - multi-threading
-  - bugs
-
-examples:
-  bad: |
-    Thread thread = new Thread(runnable);
-    thread.wait();  // BAD - on Thread instance
-    thread.notify();  // BAD
-
-  good: |
-    Object lock = new Object();
-    synchronized (lock) {
-        lock.wait();  // GOOD - on separate lock
-    }
-
-has_fix: false

package/rules/tree-sitter-queries/java/short-circuit-logic.yml

@@ -1,57 +0,0 @@
-# Short Circuit Logic
-# Detects non-short-circuit operators in boolean contexts
-id: short-circuit-logic
-name: Short-Circuit Logic Should Be Used in Boolean Contexts
-severity: error
-category: maintainability
-defect_class: correctness
-inline_tier: blocking
-language: java
-
-message: "Use '{{OP}}' instead of '{{BAD_OP}}' for short-circuit evaluation"
-
-description: |
-  Use && and || for boolean logic (short-circuit). & and | are
-  bitwise operators that evaluate both sides, causing unnecessary
-  computation and potential errors.
-
-  ✅ FIX: Use && or ||
-
-  ```java
-  if (obj != null && obj.isValid()) {  // GOOD - short-circuit
-  ```
-
-query: |
-  (binary_expression
-    (identifier) @LEFT
-    "&" @BAD_OP
-    (identifier) @RIGHT)
-  (binary_expression
-    (identifier) @LEFT
-    "|" @BAD_OP
-    (identifier) @RIGHT)
-
-metavars:
-  - LEFT
-  - BAD_OP
-  - RIGHT
-
-post_filter: boolean_operands
-
-tags:
-  - maintainability
-  - java
-  - cert
-  - performance
-
-examples:
-  bad: |
-    if (a & b) { }  // BAD - bitwise AND
-    if (x | y) { }  // BAD - bitwise OR
-
-  good: |
-    if (a && b) { }  // GOOD - short-circuit
-    if (x || y) { }  // GOOD - short-circuit
-
-has_fix: true
-fix_action: replace_with_short_circuit

package/rules/tree-sitter-queries/java/spring-session-attributes-setcomplete.yml

@@ -1,75 +0,0 @@
-# Spring SessionAttributes setComplete
-# Detects @Controller classes with @SessionAttributes that don't call setComplete
-id: spring-session-attributes-setcomplete
-name: SessionAttributes Controllers Must Call setComplete
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: java
-
-message: "@Controller with @SessionAttributes must call setComplete on SessionStatus"
-
-description: |
-  Controllers using @SessionAttributes must call setComplete() on the SessionStatus
-  parameter to clean up session attributes. Otherwise, session data leaks
-  and causes memory issues.
-
-  ✅ FIX: Call setComplete() when done with session attributes
-
-  ```java
-  @Controller
-  @SessionAttributes("user")
-  public class UserController {
-      @RequestMapping("/complete")
-      public String complete(SessionStatus status) {
-          status.setComplete();  // Clear session attributes
-          return "done";
-      }
-  }
-  ```
-
-query: |
-  (class_declaration
-    (modifiers
-      (annotation
-        name: (identifier) @ANNOT1 (#eq? @ANNOT1 "Controller"))
-      (annotation
-        name: (identifier) @ANNOT2 (#eq? @ANNOT2 "SessionAttributes"))))
-
-metavars:
-  - ANNOT1
-  - ANNOT2
-
-post_filter: missing_setcomplete_call
-
-tags:
-  - reliability
-  - java
-  - spring
-  - session
-  - memory-leak
-
-examples:
-  bad: |
-    @Controller
-    @SessionAttributes("data")
-    public class MyController {
-        @PostMapping("/submit")
-        public String submit(SessionStatus status) {  // Missing setComplete()
-            return "done";
-        }
-    }
-
-  good: |
-    @Controller
-    @SessionAttributes("data")
-    public class MyController {
-        @PostMapping("/submit")
-        public String submit(SessionStatus status) {
-            status.setComplete();  // GOOD - clean up
-            return "done";
-        }
-    }
-
-has_fix: false

package/rules/tree-sitter-queries/plsql-disabled/delete-update-where.yml

@@ -1,56 +0,0 @@
-# DELETE and UPDATE Without WHERE
-# Detects DELETE and UPDATE statements without WHERE clauses in PL/SQL
-id: delete-update-where
-name: DELETE and UPDATE Should Contain WHERE Clauses
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: plsql
-
-message: "{{STATEMENT}} statement should contain a WHERE clause"
-
-description: |
-  DELETE and UPDATE without WHERE clauses affect ALL rows in the table.
-  This is almost always a bug and can cause data loss.
-
-  ✅ FIX: Add a WHERE clause to limit affected rows
-
-  ```sql
-  DELETE FROM employees WHERE id = emp_id;  -- GOOD
-  UPDATE employees SET status = 'inactive' WHERE id = emp_id;  -- GOOD
-  ```
-
-query: |
-  (delete_statement
-    (delete) @DELETE
-    (from_clause)
-    (where_clause)? @WHERE)
-  (update_statement
-    (update) @UPDATE
-    (table_reference)
-    (where_clause)? @WHERE)
-
-metavars:
-  - DELETE
-  - UPDATE
-  - WHERE
-
-post_filter: missing_where_clause
-
-tags:
-  - reliability
-  - plsql
-  - sql
-  - data-loss
-
-examples:
-  bad: |
-    DELETE FROM employees;  -- BAD - deletes all rows!
-    UPDATE employees SET salary = 0;  -- BAD - updates all rows!
-
-  good: |
-    DELETE FROM employees WHERE id = 123;  -- GOOD
-    UPDATE employees SET salary = 0 WHERE department = 'TEMP';  -- GOOD
-
-has_fix: false

package/rules/tree-sitter-queries/plsql-disabled/end-loop-semicolon.yml

@@ -1,51 +0,0 @@
-# END LOOP Semicolon
-# Detects END LOOP without following semicolon
-id: end-loop-semicolon
-name: END LOOP Should Be Followed By Semicolon
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: plsql
-
-message: "END LOOP should be followed by a semicolon"
-
-description: |
-  The END LOOP keyword must be followed by a semicolon.
-  Missing semicolon causes a syntax error.
-
-  ✅ FIX: Add semicolon after END LOOP
-
-  ```sql
-  LOOP
-      EXIT WHEN condition;
-  END LOOP;  -- GOOD - has semicolon
-  ```
-
-query: |
-  (loop_statement
-    (end_loop) @ENDLOOP)
-
-metavars:
-  - ENDLOOP
-
-post_filter: missing_following_semicolon
-
-tags:
-  - reliability
-  - plsql
-  - syntax
-
-examples:
-  bad: |
-    LOOP
-        EXIT WHEN x > 10;
-    END LOOP  -- BAD - missing semicolon
-
-  good: |
-    LOOP
-        EXIT WHEN x > 10;
-    END LOOP;  -- GOOD
-
-has_fix: true
-fix_action: add_semicolon

package/rules/tree-sitter-queries/plsql-disabled/fetch-bulk-collect-limit.yml

@@ -1,47 +0,0 @@
-# FETCH BULK COLLECT With LIMIT
-# Detects FETCH ... BULK COLLECT without LIMIT clause
-id: fetch-bulk-collect-limit
-name: FETCH BULK COLLECT INTO Should Use LIMIT Clause
-severity: error
-category: reliability
-defect_class: correctness
-inline_tier: blocking
-language: plsql
-
-message: "FETCH ... BULK COLLECT INTO should not be used without a LIMIT clause"
-
-description: |
-  FETCH ... BULK COLLECT without LIMIT fetches ALL rows into memory.
-  This can cause out-of-memory errors for large result sets.
-
-  ✅ FIX: Add LIMIT clause to control batch size
-
-  ```sql
-  FETCH cursor BULK COLLECT INTO collection LIMIT 1000;  -- GOOD
-  ```
-
-query: |
-  (fetch_statement
-    (fetch) @FETCH
-    (bulk_collect_into_clause) @BULK)
-
-metavars:
-  - FETCH
-  - BULK
-
-post_filter: missing_limit_clause
-
-tags:
-  - reliability
-  - plsql
-  - performance
-  - memory
-
-examples:
-  bad: |
-    FETCH cursor BULK COLLECT INTO employees;  -- BAD - no LIMIT
-
-  good: |
-    FETCH cursor BULK COLLECT INTO employees LIMIT 1000;  -- GOOD
-
-has_fix: false