[pull] main from danny-avila:main

.env.example

@@ -1232,11 +1232,13 @@ HELP_AND_FAQ_URL=https://librechat.ai
 # SCHEDULES_DISABLED=true
 
 # Coalesce streamed model/tool-argument deltas into windowed Redis publications (ms).
-# Unset or 0 (default) publishes per delta. 25 is recommended: it batches the publish
-# EVAL and the durable append across the window (fewer Redis round trips and lower
-# Redis CPU at high token rates) at the cost of up to one window of added delivery
-# latency. Enable only after EVERY replica runs a build with batch-frame support;
-# older subscribers drop coalesced frames. Values are capped at 1000.
+# Defaults to 25ms when unset; explicit 0 publishes per delta. Batches both publish
+# and durable append operations (fewer Redis round trips and repeated guard/TTL work at high
+# token rates), adding up to one window of buffering latency and crash-loss exposure
+# for unflushed deltas. In-memory streams are unchanged. Values are capped at 1000.
+# Batched publications retain individual chunk frames for older subscribers; Pub/Sub
+# message count is unchanged. Incoming chunk_batch frames remain supported for existing
+# opt-in producers. See UPGRADING.md for compatibility guidance.
 # Keep the window <= the stream-smoothing cadence (`streamRate`, default 25ms):
 # each smoothing tick emits its pieces in one burst, so a tick-sized window
 # captures exactly one batch per tick; a larger window re-batches the paced

.github/pull_request_template.md

@@ -1,47 +1,48 @@
-# Pull Request Template
+# Pull Request
 
-⚠️ Before Submitting a PR, Please Review:
-- Please ensure that you have thoroughly read and understood the [Contributing Docs](https://github.com/danny-avila/LibreChat/blob/main/.github/CONTRIBUTING.md) before submitting your Pull Request.
-
-⚠️ Documentation Updates Notice:
-- Kindly note that documentation updates are managed in this repository: [librechat.ai](https://github.com/LibreChat-AI/librechat.ai)
+> Before submitting, please review the [Contributing Guide](https://github.com/danny-avila/LibreChat/blob/main/.github/CONTRIBUTING.md).
+>
+> Documentation changes belong in the [LibreChat documentation repository](https://github.com/LibreChat-AI/librechat.ai).
 
 ## Summary
 
 <!--
-Say what breaks or is missing today, what triggers it, and how it behaves after this
-change. Link the issue with `Fixes #N`, and list any dependency your change needs.
-Two or three sentences is usually enough:
-
-"Pasting an image while the composer had focus left Send disabled until the user
-clicked back into the textarea: the upload dialog took focus and never returned it.
-Focus now returns to the composer as soon as the attachment mounts."
-
-Describe the code as it stands. A reader who has not followed the branch has no
-context for what earlier commits tried or what a review round changed. Naming the
-merged pull request that caused the bug is different — that is history the reader
-needs.
+Briefly explain:
+- What problem or limitation exists today?
+- What triggers it (input, state, or configuration)?
+- What does this PR change?
+- What is the resulting behavior?
+
+Keep this focused on the final state of the code rather than the history of the
+branch or previous review iterations. Naming the merged pull request that
+introduced a regression is the exception: that is history the reader needs.
+
+Link related issues, and name any dependency this change needs:
+Fixes #123
+Related to #123
+Depends on danny-avila/agents#123
 -->
 
 ## How it works
 
 <!--
-Optional. Delete this section when the summary already explains the change.
+Optional. Remove this section if the implementation is already obvious from the
+summary and diff.
 
-Pick one or two views that make the change reviewable, and put a sentence beside
-each. These show the format, not a required implementation pattern — replace them
-with real names from your change. Do not paste the whole diff or list every file
-you touched.
+Explain the mechanism reviewers need to understand. Pick one or two of the views
+below, whichever make the change reviewable, and put a sentence beside each rather
+than describing every changed file. Show a whole block instead of a diff when most
+of it is new, or when the omitted context would hide execution order or ownership.
 
-The mechanism, as a focused diff, when the surrounding shape already exists:
+Focused diff:
 
 ```diff
 -const parts = content.filter(isText);
 -const files = content.filter(isFile);
 +const { parts, files } = splitContent(content);
 ```
 
-Runtime order, as a call tree, keeping only the calls that carry the change:
+Runtime flow:
 
 ```text
 submitMessage
@@ -50,16 +51,16 @@ submitMessage
     setSubmission   # opens the SSE stream
 ```
 
-Ownership, as a shallow file tree, for a new module or a broad refactor:
+Ownership:
 
 ```text
 packages/api/src/agents/
-├── run.ts      # builds the run and its callbacks
+├── run.ts      # builds the run and callbacks
 ├── tools.ts    # resolves tools for the request
-└── client.ts   # streams provider output back to the route
+└── client.ts   # streams provider output
 ```
 
-Client/server or cross-service flow, as Mermaid:
+Cross-service flow:
 
 ```mermaid
 sequenceDiagram
@@ -72,41 +73,92 @@ sequenceDiagram
     API->>Client: SSE events
 ```
 
-Editing this file: keep the arrows in the example above solid (`->>`). A dashed
-Mermaid arrow spells the comment terminator, so it would close this comment early
-and spill the rest of the guidance into every description. Your own diagram sits
-outside the comment, where dashed arrows are fine.
-
-Show a whole block instead of a diff when most of it is new, or when the omitted
-context would hide execution order or ownership.
+Keep the arrows in this example solid (`->>`). A dashed Mermaid arrow spells the
+HTML comment terminator, so it would close this block early and spill the rest of
+the guidance into every description. Diagrams you write outside this comment can
+use dashed arrows freely.
 -->
 
-## Change Type
+## Type of change
 
-Please delete any irrelevant options.
+<!-- Select all that apply. -->
 
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] This change requires a documentation update
-- [ ] Translation update
+* [ ] Bug fix
+* [ ] Feature
+* [ ] Refactor
+* [ ] Performance improvement
+* [ ] Breaking change
+* [ ] Documentation
+* [ ] Translation
+* [ ] Tests / tooling / CI
 
 ## Testing
 
-Please describe your test process and include instructions so that we can reproduce your test. If there are any important variables for your testing configuration, list them here.
+<!--
+Describe how you verified the change.
+
+Include only the configuration that matters for reproducing the test.
+
+Example:
+
+1. Start LibreChat with Agents enabled.
+2. Create an agent using an Ollama endpoint.
+3. Add the Ask User tool.
+4. Send a message that triggers the tool.
+5. Confirm the question is rendered and the conversation continues after answering.
+-->
 
-### **Test Configuration**:
+**Tested environments/configuration:**
+
+<!--
+Examples:
+- Browser:
+- Provider/model:
+- Database:
+- Feature flags:
+- OS:
+-->
+
+**Automated tests:**
+
+<!--
+Examples:
+- `npm run test:client`
+- `npm run test:api`
+- Added tests in `foo.spec.ts`
+
+Write "Not applicable" when appropriate.
+-->
+
+## Screenshots / recordings
+
+<!--
+For user-facing changes, include before/after screenshots or a short recording.
+Remove this section when not applicable.
+-->
+
+## Risk / compatibility
+
+<!--
+Optional for small changes.
+
+Call out anything reviewers should pay particular attention to, such as:
+- migrations or schema changes
+- API/configuration changes
+- provider-specific behavior
+- backwards compatibility
+- performance implications
+- security-sensitive behavior
+
+Write "None" when there are no notable risks.
+-->
 
 ## Checklist
 
-Please delete any irrelevant options.
-
-- [ ] My code adheres to this project's style guidelines
-- [ ] I have performed a self-review of my own code
-- [ ] I have commented in any complex areas of my code
-- [ ] I have made pertinent documentation changes
-- [ ] My changes do not introduce new warnings
-- [ ] I have written tests demonstrating that my changes are effective or that my feature works
-- [ ] Local unit tests pass with my changes
-- [ ] Any changes dependent on mine have been merged and published in downstream modules.
-- [ ] A pull request for updating the documentation has been submitted.
+* [ ] I reviewed my own changes
+* [ ] Relevant tests have been added or updated
+* [ ] Existing relevant tests pass
+* [ ] The change does not introduce new warnings or errors
+* [ ] User-facing or complex behavior is documented where necessary
+* [ ] Required dependency changes have been merged/published
+* [ ] Required documentation PR: <!-- link or N/A -->

.github/workflows/backend-review.yml

@@ -433,7 +433,9 @@ jobs:
       - name: Run unit tests (shard ${{ matrix.shard }}/3)
         env:
           SELECTED: ${{ needs.codegraph_select.outputs.api_files }}
+          JEST_JSON: --json --outputFile=${{ github.workspace }}/jest-results/jest-results-api-${{ matrix.shard }}.json
         run: |
+          mkdir -p "$GITHUB_WORKSPACE/jest-results"
           cd api
           # A selected path can be stale in exactly two ways at this checkout (Codex P2, #15145 r6):
           # deleted on the branch — dropped, which matches full CI (the file runs nowhere) — or
@@ -448,14 +450,26 @@ jobs:
             KEEP="${KEEP# }"
             if [ -z "$KEEP" ]; then
               echo "no selected test file exists at HEAD (stale selection); running FULL"
-              npm run test:ci -- --shard=${{ matrix.shard }}/3
+              npm run test:ci -- --shard=${{ matrix.shard }}/3 $JEST_JSON
             else
               echo "codegraph: $(echo $KEEP | wc -w) selected test files (safe mode)"
-              npm run test:ci -- --shard=${{ matrix.shard }}/3 --passWithNoTests --runTestsByPath $KEEP
+              npm run test:ci -- --shard=${{ matrix.shard }}/3 --passWithNoTests --runTestsByPath $KEEP $JEST_JSON
             fi
           else
-            npm run test:ci -- --shard=${{ matrix.shard }}/3
+            npm run test:ci -- --shard=${{ matrix.shard }}/3 $JEST_JSON
           fi
+      # Per-test results keyed by head SHA (run.head_sha), for the codegraph test-evidence feed.
+      # Never part of the gate: it cannot fail the job, and a re-run overwrites its own artifact.
+      - name: Upload Jest results
+        if: ${{ !cancelled() }}
+        continue-on-error: true
+        uses: actions/upload-artifact@v6
+        with:
+          name: jest-results-api-${{ matrix.shard }}
+          path: jest-results/
+          retention-days: 7
+          if-no-files-found: ignore
+          overwrite: true
 
   test-data-provider:
     name: 'Tests: data-provider'
@@ -509,7 +523,9 @@ jobs:
       - name: Run unit tests
         env:
           SELECTED: ${{ needs.codegraph_select.outputs.dataprovider_files }}
+          JEST_JSON: --json --outputFile=${{ github.workspace }}/jest-results/jest-results-data-provider.json
         run: |
+          mkdir -p "$GITHUB_WORKSPACE/jest-results"
           cd packages/data-provider
           if [ -n "$SELECTED" ]; then
             KEEP=""
@@ -519,14 +535,26 @@ jobs:
             KEEP="${KEEP# }"
             if [ -z "$KEEP" ]; then
               echo "no selected test file exists at HEAD (stale selection); running FULL"
-              npm run test:ci
+              npm run test:ci -- $JEST_JSON
             else
               echo "codegraph: $(echo $KEEP | wc -w) selected test files (safe mode)"
-              npm run test:ci -- --passWithNoTests --runTestsByPath $KEEP
+              npm run test:ci -- --passWithNoTests --runTestsByPath $KEEP $JEST_JSON
             fi
           else
-            npm run test:ci
+            npm run test:ci -- $JEST_JSON
           fi
+      # Per-test results keyed by head SHA (run.head_sha), for the codegraph test-evidence feed.
+      # Never part of the gate: it cannot fail the job, and a re-run overwrites its own artifact.
+      - name: Upload Jest results
+        if: ${{ !cancelled() }}
+        continue-on-error: true
+        uses: actions/upload-artifact@v6
+        with:
+          name: jest-results-data-provider
+          path: jest-results/
+          retention-days: 7
+          if-no-files-found: ignore
+          overwrite: true
 
   test-data-schemas:
     name: 'Tests: data-schemas'
@@ -586,7 +614,9 @@ jobs:
       - name: Run unit tests
         env:
           SELECTED: ${{ needs.codegraph_select.outputs.dataschemas_files }}
+          JEST_JSON: --json --outputFile=${{ github.workspace }}/jest-results/jest-results-data-schemas.json
         run: |
+          mkdir -p "$GITHUB_WORKSPACE/jest-results"
           cd packages/data-schemas
           if [ -n "$SELECTED" ]; then
             KEEP=""
@@ -596,14 +626,26 @@ jobs:
             KEEP="${KEEP# }"
             if [ -z "$KEEP" ]; then
               echo "no selected test file exists at HEAD (stale selection); running FULL"
-              npm run test:ci
+              npm run test:ci -- $JEST_JSON
             else
               echo "codegraph: $(echo $KEEP | wc -w) selected test files (safe mode)"
-              npm run test:ci -- --passWithNoTests --runTestsByPath $KEEP
+              npm run test:ci -- --passWithNoTests --runTestsByPath $KEEP $JEST_JSON
             fi
           else
-            npm run test:ci
+            npm run test:ci -- $JEST_JSON
           fi
+      # Per-test results keyed by head SHA (run.head_sha), for the codegraph test-evidence feed.
+      # Never part of the gate: it cannot fail the job, and a re-run overwrites its own artifact.
+      - name: Upload Jest results
+        if: ${{ !cancelled() }}
+        continue-on-error: true
+        uses: actions/upload-artifact@v6
+        with:
+          name: jest-results-data-schemas
+          path: jest-results/
+          retention-days: 7
+          if-no-files-found: ignore
+          overwrite: true
 
   test-packages-api:
     name: 'Tests: @librechat/api (shard ${{ matrix.shard }}/4)'
@@ -677,7 +719,9 @@ jobs:
       - name: Run unit tests (shard ${{ matrix.shard }}/4)
         env:
           SELECTED: ${{ needs.codegraph_select.outputs.pkgapi_files }}
+          JEST_JSON: --json --outputFile=${{ github.workspace }}/jest-results/jest-results-packages-api-${{ matrix.shard }}.json
         run: |
+          mkdir -p "$GITHUB_WORKSPACE/jest-results"
           cd packages/api
           if [ -n "$SELECTED" ]; then
             KEEP=""
@@ -687,11 +731,23 @@ jobs:
             KEEP="${KEEP# }"
             if [ -z "$KEEP" ]; then
               echo "no selected test file exists at HEAD (stale selection); running FULL"
-              npm run test:ci -- --shard=${{ matrix.shard }}/4
+              npm run test:ci -- --shard=${{ matrix.shard }}/4 $JEST_JSON
             else
               echo "codegraph: $(echo $KEEP | wc -w) selected test files (safe mode)"
-              npm run test:ci -- --shard=${{ matrix.shard }}/4 --passWithNoTests --runTestsByPath $KEEP
+              npm run test:ci -- --shard=${{ matrix.shard }}/4 --passWithNoTests --runTestsByPath $KEEP $JEST_JSON
             fi
           else
-            npm run test:ci -- --shard=${{ matrix.shard }}/4
+            npm run test:ci -- --shard=${{ matrix.shard }}/4 $JEST_JSON
           fi
+      # Per-test results keyed by head SHA (run.head_sha), for the codegraph test-evidence feed.
+      # Never part of the gate: it cannot fail the job, and a re-run overwrites its own artifact.
+      - name: Upload Jest results
+        if: ${{ !cancelled() }}
+        continue-on-error: true
+        uses: actions/upload-artifact@v6
+        with:
+          name: jest-results-packages-api-${{ matrix.shard }}
+          path: jest-results/
+          retention-days: 7
+          if-no-files-found: ignore
+          overwrite: true