@mlagie/sql-connector 2.0.8 → 2.0.9

package/package.json

@@ -1,13 +1,20 @@
 {
   "name": "@mlagie/sql-connector",
-  "version": "2.0.8",
+  "version": "2.0.9",
   "description": "Le module sql-connector permet de gérer les connexions à une base de données MySQL, de définir des schémas de tables, et d'interagir avec les données de manière simple et efficace.",
   "main": "index.js",
+  "files": [
+    "src",
+    "docs",
+    "index.d.ts",
+    "index.js"
+  ],
   "scripts": {
     "test": "rm -r coverage ; node --experimental-vm-modules node_modules/jest/bin/jest.js --runInBand",
     "test:publish": "npm publish --dry-run",
     "test:watch": "node --experimental-vm-modules node_modules/jest/bin/jest.js --watch",
     "test:coverage": "rm -r coverage ; node --experimental-vm-modules node_modules/jest/bin/jest.js --coverage",
+    "coverage:report": "node scripts/coverage-report.js",
     "security": "npx eslint . --max-warnings 0 --ignore-pattern './tests/*'"
   },
   "repository": {
@@ -38,18 +45,27 @@
   "license": "MIT",
   "type": "commonjs",
   "bugs": {
-    "url": "https://github.com/lagie-marin/sql-connector/issues"
+    "url": "https://github.com/mlagie/sql-connector/issues"
   },
-  "homepage": "https://github.com/lagie-marin/sql-connector#readme",
+  "homepage": "https://github.com/mlagie/sql-connector#readme",
   "private": false,
   "dependencies": {
     "@mlagie/logger": "1.0.2",
-    "mysql2": "3.22.5"
+    "mysql2": "3.23.1"
   },
   "devDependencies": {
     "@eslint/js": "^10.0.1",
-    "eslint": "^10.6.0",
+    "eslint": "^10.8.0",
     "eslint-plugin-security": "^4.0.1",
-    "jest": "^30.4.2"
+    "jest": "30.4.2"
+  },
+  "overrides": {
+    "test-exclude": "^8.0.0",
+    "glob": "^13.0.6",
+    "minimatch": "^10.2.2",
+    "brace-expansion": "^5.0.9"
+  },
+  "allowScripts": {
+    "unrs-resolver@1.12.2": true
   }
-}
+}

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,43 +0,0 @@
----
-name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: ''
-assignees: lagie-marin
-
----
-
-## Bug Description
-
-## Steps to Reproduce
-
-1. Call the method `...`
-2. Pass the following options/parameters `...`
-3. Execute the code
-4. See the error
-
-## Code Snippet / Logs
-
-**JavaScript Code:**
-
-```javascript
-// Insert the JavaScript code that triggers the issue here
-const result = await MyModel.find({ ... });
-```
-
-## Error Logs / Output
-
-```txt
-TypeError: ... is not a function
-    at ...
-```
-
-## Expected Behavior
-
-Example: The `find()` method should return a native JavaScript Array of `ModelInstance` objects so that `.length` or indexation like `[0]` works out of the box when multiple rows are returned.
-
-## Environment
-
-- sql-connector version: vX.X.X
-- Node.js version: vXX.XX.X
-- Database (MySQL/MariaDB...): MySQL vX.X

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,29 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
-assignees: lagie-marin
-
----
-
-## Feature Type
-- [ ] New method / API addition
-- [ ] Performance improvement
-- [ ] Architecture Refactoring (ORM / Data Mapping)
-- [ ] Other: 
-
-## Problem Statement
-*Example: Currently, the ORM wraps the raw driver payload `[rows, fields]` inside a single global `ModelInstance`. This forces developers to leak internal database structure by accessing nested arrays like `data[0][0]` when handling records, destroying proper encapsulation.*
-
-## Proposed Solution
-*Example: Refactor the `find()` method to map and split the query results. It should return a native Array where each row is mapped into its own independent `ModelInstance`. Implement dynamic data-mapping (via continuous references, Getters/Setters, or a Proxy) to allow direct property access (`job.status`) without cloning the memory footprint.*
-
-## Desired Developer Experience (DX / Example)
-```javascript
-// Provide an example of how the ideal code should look after this feature:
-const jobs = await InjectionJobs.find({ where: { status: "running" } });
-
-console.log(jobs.length);    // Native array length works
-console.log(jobs[0].status); // Direct property access on the instance
-await jobs[0].updateOne({ status: "success" }); // Instance methods remain fully bound

package/.github/workflows/publish.yml

@@ -1,80 +0,0 @@
-name: Publish Package
-
-on:
-  workflow_dispatch:
-  release:
-    types: [published]
-  push:
-    branches:
-      - "**"
-  pull_request:
-    branches:
-      - main
-jobs:
-  check_security:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout GH repository
-        uses: actions/checkout@v6
-      - name: setup node
-        uses: actions/setup-node@v6
-        with:
-          node-version: 22
-      - name: Install deps
-        run: npm ci
-      - name: Audit deps
-        continue-on-error: false
-        run: |
-          npm audit
-      - name: Check security of module
-        continue-on-error: false
-        run: |
-          npm run security
-  integrity:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout GH repository
-        uses: actions/checkout@v6
-      - name: setup node
-        uses: actions/setup-node@v6
-        with:
-          node-version: 22
-      - name: Install deps
-        run: npm ci
-      - name: Run integrity check
-        continue-on-error: false
-        run: |
-          npm run test
-  publish:
-    needs:
-      - check_security
-      - integrity
-    if: github.event_name == 'release' || github.event_name == 'workflow_dispatch'
-    runs-on: ubuntu-latest
-    environment: sqlc
-    permissions:
-      contents: read
-      id-token: write # Requis pour la provenance (--provenance)
-
-    steps:
-      # 1. Récupérer le code source
-      - name: Checkout du code
-        uses: actions/checkout@v6
-
-      # 2. Configurer Node.js pour registry.npmjs.org
-      - name: Configurer Node.js
-        uses: actions/setup-node@v6
-        with:
-          node-version: "22"
-          registry-url: "https://registry.npmjs.org/" # <-- Cible npmjs
-          scope: "@mlagie"
-
-      # 3. Installer les dépendances
-      - name: Installer les dépendances
-        run: npm ci
-
-      # 4. Publier sur le vrai registre npm
-      - name: Publier sur npmjs.com
-        run: npm publish --provenance --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

package/eslint.config.mjs

@@ -1,37 +0,0 @@
-import js from "@eslint/js";
-import security from "eslint-plugin-security";
-
-export default [
-  {
-    ignores: ["eslint.config.mjs"]
-  },
-  js.configs.recommended,
-  {
-    files: ["**/*.js"],
-    languageOptions: {
-      sourceType: "commonjs",
-      globals: {
-        console: "readonly",
-        exports: "readonly",
-        module: "readonly",
-        process: "readonly",
-        require: "readonly",
-        __dirname: "readonly",
-        __filename: "readonly"
-      }
-    },
-    plugins: {
-      security
-    },
-    rules: {
-      ...security.configs.recommended.rules,
-      "no-unused-vars": [
-        "error",
-        {
-          argsIgnorePattern: "^(?:_|resolve|reject)$",
-          varsIgnorePattern: "^_$"
-        }
-      ]
-    }
-  }
-];

package/releases/1.4.8.md

@@ -1,43 +0,0 @@
-# **Release v1.4.8 — sql-connector**
-
-## **Présentation**
-Cette version poursuit la refonte de `sql-connector` avec une documentation plus lisible, une séparation claire entre les langues, et plusieurs améliorations de fiabilité sur les modèles et la génération SQL.
-
-## **Nouveautés**
-
-### Documentation bilingue
-- La documentation a été restructurée pour séparer plus clairement le contenu en français et en anglais.
-- Le README racine sert désormais de point d'entrée rapide vers la documentation.
-- Le dossier `docs/` est utilisé pour regrouper les pages de documentation par langue.
-
-### Synchronisation et schémas
-- `Model.syncAllTables()` continue de comparer le schéma JS avec la base et applique les différences utiles de manière plus sûre.
-- La longueur par défaut est désormais gérée correctement pour les types `VARCHAR` et `INT` quand `length` n'est pas défini.
-- Une erreur explicite est levée si un champ est déclaré à la fois `primary_key` et `unique`.
-
-### Modèles et requêtes
-- `updateOne()` ignore automatiquement les champs `undefined`.
-- Les mises à jour utilisent une condition `WHERE` plus robuste, en privilégiant les clés primaires quand elles sont disponibles.
-- La génération des conditions SQL a été améliorée pour mieux normaliser les chaînes, les dates et les valeurs JSON.
-
-### Dépendances et maintenance
-- `glob` a été ajouté pour améliorer la détection des fichiers de backup SQL.
-- Les logs de synchronisation et d'exécution ont été renforcés pour faciliter le débogage.
-
-## **Migration depuis v1.4.5**
-
-### Points principaux
-1. La documentation a été réorganisée autour d'un accès plus simple par langue.
-2. Les opérations de mise à jour de modèles sont maintenant plus fiables.
-3. Les règles de génération SQL sont plus strictes et plus prévisibles.
-
-### Recommandation
-- Vérifiez vos schémas si vous utilisiez des champs sans `length`, des mises à jour avec des valeurs `undefined`, ou des colonnes déclarées à la fois `primary_key` et `unique`.
-
-## **Documentation**
-Pour plus de détails, consultez la documentation du projet dans `README.md` et le dossier `docs/`.
-
-## **Liens utiles**
-- [GitHub Repository](https://github.com/lagie-marin/sql-connector)
-- [npm Package](https://www.npmjs.com/package/@mlagie/sql-connector)
-- [Issues](https://github.com/lagie-marin/sql-connector/issues)

package/releases/1.5.0.md

@@ -1,127 +0,0 @@
-# **Release v1.5 — sql-connector**
-
-## Overview
-
-This release introduces a major improvement to the query system in sql-connector, focusing on flexibility, performance, and developer experience.
-
-The new version simplifies query building, adds support for advanced SQL features (such as aggregation and date formatting), and improves consistency across model operations.
-
----
-
-## New Features
-
-### Enhanced Query Builder (findAll)
-
-- findAll() now supports advanced SQL features through a clean and extensible configuration object.
-- Developers can build complex queries without writing raw SQL.
-
-Supported features:
-
-- SUM, DATE_FORMAT, and custom field transformations
-- GROUP BY, ORDER BY, HAVING, and LIMIT
-- Multiple aggregations in a single query
-
-Example:
-
-```js
-Model.findAll({
-  select: [
-    { dateFormat: ['date_day', '%Y-%m'], as: 'period' },
-    { sum: 'error' },
-    { sum: 'reload' },
-  ],
-  groupBy: ['period'],
-  orderBy: [{ field: 'period', direction: 'ASC' }]
-});
-```
-
----
-
-### Dynamic Field Builder
-
-- Query fields are now processed individually through a modular builder.
-- Enables combining multiple transformations (e.g., multiple SUM, DATE_FORMAT) without hardcoding specific cases.
-- Improves extensibility for future SQL functions (AVG, COUNT, etc.).
-
----
-
-### Simplified Query Construction
-
-- Query generation now follows a fixed SQL order (WHERE → GROUP BY → HAVING → ORDER BY → LIMIT) without unnecessary sorting.
-- Improves performance and avoids overhead from dynamic reordering.
-- Keeps the implementation simple and predictable.
-
----
-
-### Improved Aggregation Support
-
-- Designed for analytics use cases:
-  - Time-based grouping (day, month, year)
-  - Multi-metric aggregation
-  - Clean integration with frontend dashboards
-
----
-
-### Better Developer Experience
-
-- No need to write raw SQL for common queries
-- Clear and readable query configuration
-- Consistent API across simple and advanced queries
-
----
-
-## Improvements
-
-### customRequest function
-
-- customRequest provides all the information instead of taking the first element of the request.
-
-### Model Usage
-
-- findAll() is now instance-based instead of static for better flexibility and dependency injection.
-- Enables multiple database connections and improved testability.
-
----
-
-### Performance Optimization
-
-- Removed unnecessary iteration and sorting logic in query building.
-- Query generation now runs in constant time structure (no scaling overhead with new features).
-
----
-
-### Code Maintainability
-
-- Cleaner separation between:
-  - field building
-  - query parts
-  - execution
-
-- Easier to extend without modifying core logic.
-
-## Migration from v1.4.x
-
-### Main changes
-
-1. Switch to instance-based model usage
-2. Update findAll calls to use the new select format
-3. Adapt queries using aggregation to the new field builder system
-
-### Recommendation
-
-- Replace raw SQL queries with the new findAll configuration when possible
-- Review existing analytics queries to leverage built-in aggregation support
-
-## Documentation
-
-See the updated documentation in:
-
-- [README.md](../README.md)
-
-## Useful Links
-
-- GitHub Repository: <https://github.com/lagie-marin/sql-connector>
-
-- npm Package: <https://www.npmjs.com/package/@mlagie/sql-connector>
-
-- Issues: <https://github.com/lagie-marin/sql-connector/issues>

package/releases/2.0.0.md

@@ -1,32 +0,0 @@
-# **Release v2.0.0 — Security Hardening & Prototype Pollution Prevention**
-
-This release focuses heavily on `security improvements` across the ORM's core model management and data access layers. We have successfully mitigated potential security vulnerabilities regarding dynamic property access and file path operations, satisfying `eslint-plugin-security` analysis.
-
-## **Key Changes & Security Fixes**
-
-### **1. Prototype Pollution & Object Injection Prevention**
-
-- **Problem**: Using dynamic bracket notations like obj[key] where key originates from user inputs or database schemas exposed the application to **Object Injection** and **Prototype Pollution** (allowing attackers to alter critical global properties via keys like `__proto__` or `constructor`).
-
-- **Fix**: Introduced a centralized `safe.js` security utility leveraging `Reflect.get()` and `Reflect.set()` coupled with a strict property blacklist (`__proto__`, `constructor`, `prototype`).
-  - Migrated all dynamic model lookups and topological sorting dictionaries in `Model.js` to safe wrappers.
-  - Secured dynamic getters and setters mapped to data columns in `ModelInstance.js`.
-
-### **2. Path Traversal & Safe Database Backups**
-
-- **Problem**: Dynamically naming automated backup files (**.sql**) based on database table names without validation triggered `detect-non-literal-fs-filename` warnings, opening up potential `Path Traversal` vector concerns.
-
-- **Fix**: Implemented string sanitization via regex (`/[^a-zA-Z0-9_]/g`) on table-driven variables prior to passing arguments to standard `fs` sync methods (`writeFileSync`, `readFileSync`, `unlinkSync`, `renameSync`).
-  - Fully resolved all local `fs` filename security alerts.
-
-### **3. General Code Refactoring**
-
-- Replaced native object literals `{}` with prototype-less structures `(Object.create(null))` for configuration mappings and dependency graph resolution arrays to prevent unexpected inheritance bugs.
-
-## **Component Impact**
-
-|             File              |                             Changes Made                          |                         Warning Cleared                     |
-|-------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------|
-| `src/utils/security/safe.js`  | Created utility with `Reflect` API + validation blacklist         | None (Fully clean)                                          |
-| `src/models/Model.js`         | Patched `syncAllTables`, topological sort, and `fs` operations    | `detect-object-injection`, `detect-non-literal-fs-filename` |
-| `src/models/ModelInstance.js` | Secured active schema columns maps inside constructor proxies     | `detect-object-injection`                                   |

package/releases/2.0.1.md

@@ -1,23 +0,0 @@
-# Release v2.0.1 — Hotfix: Application Launch Crash (Variable Reference Error)
-
-This patch release resolves a critical regression introduced in `v2.0.0` that completely blocked applications from starting when using `@mlagie/sql-connector`.
-
-## Problem
-
-Upon initializing the package or starting the parent application, a runtime crash occurred due to an undefined or incorrectly scoped variable. This prevented the ORM from establishing connections and loading models properly, causing the host application to crash immediately on boot.
-
-## What Was Fixed
-
-* **Variable Scope Resolution:** Fixed the broken variable reference causing the startup crash during initialization.
-* **Boot Reliability:** Restored seamless application launches when importing and configuring the SQL connector.
-
----
-
-## 📦 Component Impact
-
-| Impacted Area | Description | Status |
-| :--- | :--- | :--- |
-| **Core Initialization** | Uncaught reference/variable error blocking `npm start` | **Fixed** |
-| **Stability** | Application crash on package import | **Resolved** |
-
-*If you encountered initialization errors with v2.0.0, please upgrade your dependency to v2.0.1 immediately.* `npm update @mlagie/sql-connector`

package/releases/2.0.2.md

@@ -1,20 +0,0 @@
-# Release v2.0.2 — Performance Optimization & Code Cleanup
-
-This patch release focuses on optimizing the internal runtime footprint and improving overall execution performance by removing legacy, unused code paths and dependencies.
-
-## What Was Improved
-
-* **Dead Code Elimination:** Removed unused functions, legacy variables, and obsolete logic that were lingering from previous architecture overhauls (such as the old `serveur` logger reference).
-* **Performance Boost:** Cleaning up these elements reduces CPU overhead and memory usage during runtime model instantiation and schema synchronization.
-* **Code Maintenance:** Streamlined internal loops and conditional structures to ensure the ORM remains fast, lightweight, and maintainable.
-
----
-
-## Component Impact
-
-| Impacted Area | Description | Status |
-| :--- | :--- | :--- |
-| **ModelInstance & Models** | Removal of unused references and obsolete properties | **Optimized** |
-| **Runtime Footprint** | Decreased execution overhead during database mappings | **Improved** |
-
-*This is a fully backward-compatible patch. Upgrading is highly recommended to benefit from the performance improvements.* `npm update @mlagie/sql-connector`

package/releases/2.0.3.md

@@ -1,20 +0,0 @@
-# 🛡️ Release v2.0.3 — Security Overhaul: Prepared Statements (`.execute`)
-
-This major patch introduces a complete migration from raw `.query()` to parameterized Prepared Statements (`.execute()`) for all data-driven database operations, offering definitive protection against SQL Injection.
-
-## What Was Improved
-
-* **Prepared Statements Migration:** Replaced `.query()` with `.execute()` in critical data-handling pipelines (`save`, `generate_uuid`, `updateOne`, `deleteOne`).
-* **Native Value Escaping:** Transitioned from manual string manipulation/escaping functions to the database driver's native binary protocol placeholder mechanism (`?`).
-* **Bulletproof Security:** User inputs are now strictly bound as parameters, ensuring they are never interpreted as executable SQL commands by the database server.
-
----
-
-## Component Impact
-
-| Impacted Area | Description | Status |
-| :--- | :--- | :--- |
-| **Model.js** | Upgraded `save` and `generate_uuid` to use native placeholder bindings | **Secured** |
-| **ModelInstance.js** | Rewritten `updateOne`, `delete`, and `deleteOne` to prevent unsafe raw query concatenation | **Secured** |
-
-*Upgrading is highly recommended for all environments handling user-supplied data.* `npm update @mlagie/sql-connector`

package/releases/2.0.4.md

@@ -1,42 +0,0 @@
-# Release v2.0.4 — SQL Safety Hardening, CI/CD Pipeline & 100% Unit Test Coverage
-
-This release focuses on total SQL security enforcement across the ORM core, introducing a fully sandboxed unit testing suite, automated pipeline hooks, and eliminating raw string injection vectors.
-
-## Breaking Security Change (Important)
-
-- **Raw WHERE Strings Deprecated**: To ensure absolute resistance against SQL Injections, passing raw strings directly to the `where` clause (e.g., `{ where: "WHERE id = 1" }`) **is no longer allowed**. The engine now enforces structured object configurations (e.g., `{ where: { id: 1 } }`), forcing all column keys through `escapeIdentifier()` and all arguments through parameter serialization.
-
-## What Was Improved
-
-- **Stricter SQL Identifier Handling**: Centralized identifier escaping and splitting inside `utils/sql.js` now natively supports qualified names (such as `MyTable.myrow`) and pre-backticked configurations, eliminating redundant wrapping.
-
-- **100% Core Test Coverage**: Implemented a global testing architecture at the project root using Jest with **--experimental-vm-modules** to support dynamic logging imports. 100% of internal utilities (`safe.js`, `sql.js`, `formatObject.js`, `generateCondition.js`, `buildQuery.js`) are now under continuous validation.
-
-- **Isolated MySQL Mock Engine**: Created an offline test harness (`tests/mysqlMock.js`) using `jest.requireActual` to keep core string-escaping utilities intact while safely mocking pools, connections, and deep multi-dimensional database responses.
-
-- **Group By Expression Support**: Improved `GROUP BY` handling to natively parse and wrap SQL expressions such as `DATE_FORMAT(...)` without throwing strict validation failures.
-
-- **Fail-Safe CI/CD Automation**: Updated GitHub Actions (`publish.yml`) to automatically spawn `push`, `pull_request`, and `release` hooks. The NPM deployment workflow will now `instantly abort/skip` if a single security audit or unit test fails.
-
-## Component Impact
-
-|      Impacted Area         |                                                   Description                                                              |      Status      |
-|----------------------------|----------------------------------------------------------------------------------------------------------------------------|------------------|
-| Model.js / ModelInstance.js| Aligned generate_uuid() array de-structuring and secured query execution workflows against unhandled runtime crashes.      | Hardened & Fixed |
-| buildQuery.js / sql.js     | Intercepts raw strings to reject unauthorized keywords while allowing safe, isolated expression formatters.                | Secured          |
-| tests/ (New)               | Centralized testing suite at the workspace root containing independent .test.js files for edge-case and injection testing. | Covered          |
-| .github/workflows/         | Refactored publish.yml with continuous integrity verification gates ahead of release targets.                              | Automated        |
-
-## Quick Test Verification
-
-To execute the newly integrated unit testing harness locally before deployment, run:
-
-```sh
-# Execute the entire suite sequentially
-npm run test
-
-# Target a specific module in watch-mode (Developer Experience)
-npm test -- --watch --onlyFailures
-```
-
-*This patch significantly locks down database interfaces and ensures zero regression on core utility calculations. Run npm update @mlagie/sql-connector to fetch the latest changes*

package/releases/2.0.5.md

@@ -1,65 +0,0 @@
-# Release v2.0.5 — Aggregation Engine Expansion (COUNT, DISTINCT & Group Matrix Resolution)
-
-This release expands the dynamic query builder capability to support structured multi-row statistical analysis (`COUNT` and `DISTINCT`) while maintaining full architectural alignment with our strict SQL Safety parameters.
-
-## What Was Improved
-
-- **Native Secure** `COUNT` `Aggregation Matrix`: Introduced the structured `{ count: "*" }` or `{ count: "column_name" }` block into `utils/buildQuery.js`. This allows developers to safely generate standard SQL COUNT() aggregations without raw string shortcuts triggering safety breaches in escapeIdentifier().
-
-- **Distinct Value Interception Support**: Optimized fields evaluation layout to support `DISTINCT` processing inside column mappings and `GROUP BY` structural nodes, resolving compatibility limits under aggressive `ONLY_FULL_GROUP_BY` database runtime settings.
-
-- `Granular Regression Controls`: Hardened testing architecture with direct atomic assertions on nested selection objects to ensure utility stability over complex ingestion flows.
-
-## **Unit Test Additions** (`tests/buildQuery.test.js`)
-
-To ensure functional continuity, the selection building block test matrix has been expanded with the following scenarios:
-
-```js
-describe('buildQuery - Advanced Fields & Aggregations', () => {
-
-    test('Should safely compile COUNT(*) aggregated calculations with an expression alias', () => {
-        const fields = [{ count: '*', as: 'total_user' }];
-        expect(buildSelect(fields)).toBe('COUNT(*) AS `total_user`');
-    });
-
-    test('Should safely compile COUNT(column) on structured column identifiers', () => {
-        const fields = [{ count: 'id', as: 'unique_ids' }];
-        expect(buildSelect(fields)).toBe('COUNT(`id`) AS `unique_ids`');
-    });
-
-    test('Should correctly process multi-column GROUP BY arrays to avoid ONLY_FULL_GROUP_BY validation issues', () => {
-        const options = { 
-            select: ['status', 'email', { count: '*', as: 'total_user' }], 
-            groupBy: ['status', 'email'] 
-        };
-        const parts = buildQueryParts(options);
-
-        expect(parts).toContain('GROUP BY `status`, `email`');
-    });
-});
-```
-
-## Component Impact
-
-|        Impacted Area         |                                                     Description                                                         |    Status    |
-|------------------------------|-------------------------------------------------------------------------------------------------------------------------|--------------|
-| **buildQuery.js**            | Added `field.count` mapping to isolate raw expressions (`*`) safely from structural identifiers formatting.             | **Upgraded** |
-| **tests/buildQuery.test.js** | Integrated targeted coverage checking for isolated function behaviors and multi-field groups.                           | **Covered**  |
-| **Data Ingestion Modules**   | Safely resolving analytical aggregations (like cross-team platform data pipeline counters) in single-trip transactions. | **Resolved** |
-
-## Usage Example (Analytics Ingestion)
-
-Instead of passing unstable raw operations, leverage the new token syntax in your models:
-
-```js
-const teamNameData = await ProjectPipeline.find({
-    select: [
-        "team",
-        "source",
-        { count: "*", as: "total_pipelines" } // Raw counting handled securely
-    ],
-    groupBy: ["team", "source"] // Aligned with database safety policies
-});
-```
-
-*This release is fully covered by our automated CI/CD pipeline verification gates. Run npm update `@mlagie/sql-connector` to align your staging environments.*