@illuma-ai/agents 1.5.0 → 1.5.1

package/dist/types/memory/mmr.d.ts

@@ -1,7 +1,7 @@
 /**
  * Maximal Marginal Relevance (MMR) re-ranking — Phase 2.
  *
- * Ported from upstream `extensions/memory-core/src/memory/mmr.ts` with
+ * Ported from a reference implementation `extensions/memory-core/src/memory/mmr.ts` with
  * minor adaptation for our `MemoryEntry` shape (content vs snippet, id vs
  * path+startLine). Behavior is identical: normalize scores, iteratively
  * pick the item that maximizes `λ * relevance - (1-λ) * max_similarity`
@@ -10,9 +10,9 @@
  * @see Carbonell & Goldstein, "The Use of MMR, Diversity-Based Reranking" (1998)
  */
 export interface MMRConfig {
-    /** Opt-in. Upstream default is false. */
+    /** Opt-in. Default is false. */
     enabled: boolean;
-    /** 0 = max diversity, 1 = max relevance. Upstream default 0.7. */
+    /** 0 = max diversity, 1 = max relevance. Default 0.7. */
     lambda: number;
 }
 export declare const DEFAULT_MMR_CONFIG: MMRConfig;

package/dist/types/memory/paths.d.ts

@@ -8,7 +8,7 @@
  *
  * ## Why a whitelist?
  *
- * Earlier upstream-faithful designs used date-keyed files
+ * Earlier historical designs used date-keyed files
  * (`memory/YYYY-MM-DD.md`), which have three problems for a persistent
  * multi-user agent:
  *

package/dist/types/memory/temporalDecay.d.ts

@@ -1,14 +1,14 @@
 /**
  * Temporal decay — Phase 2.
  *
- * Ported from upstream `extensions/memory-core/src/memory/temporal-decay.ts`.
+ * Ported from a reference implementation `extensions/memory-core/src/memory/temporal-decay.ts`.
  * Ages dated memory files (`memory/YYYY-MM-DD.md`) using exponential decay
  * `multiplier = exp(-ln(2) / halfLifeDays * ageInDays)`. At half-life, the
  * score is exactly halved.
  *
  * Evergreen files (MEMORY.md, memory/topics.md, any non-dated file inside
  * memory/) do NOT decay — they represent durable knowledge and should stay
- * hot regardless of age. This mirrors upstream's `isEvergreenMemoryPath`.
+ * hot regardless of age. This mirrors the standard `isEvergreenMemoryPath`.
  *
  * Since our pgvector rows carry `createdAt`, we don't need filesystem stat
  * fallback — the row timestamp is authoritative for any file without a

package/dist/types/memory/types.d.ts

@@ -1,7 +1,7 @@
 /**
  * Autonomous memory — core types.
  *
- * Ported from upstream's memory-core pattern, adapted for Postgres + pgvector
+ * Ported from the reference implementation's memory-core pattern, adapted for Postgres + pgvector
  * and shaped so a future graph-backend layer (Graphiti, Neo4j agent-memory, etc.)
  * can be added alongside the vector store without changing the tool contracts.
  *
@@ -75,7 +75,7 @@ export interface MemorySearchOptions {
     minScore?: number;
     /**
      * Phase 2 toggles — when the backend supports them. Each is independently
-     * opt-in; all false = upstream Phase 1 behavior.
+     * opt-in; all false = Phase 1 behavior.
      */
     mmr?: {
         enabled?: boolean;
@@ -144,7 +144,7 @@ export interface MemoryConfig {
     search?: {
         maxResults?: number;
         maxInjectedChars?: number;
-        /** Phase 2 — enable MMR reranking (upstream-aligned defaults when true). */
+        /** Phase 2 — enable MMR reranking (defaults when true). */
         mmr?: {
             enabled?: boolean;
             lambda?: number;

package/dist/types/messages/format.d.ts

@@ -110,7 +110,7 @@ export declare const labelContentByAgent: (contentParts: MessageContentComplex[]
  *   When SkillTool is invoked, the body is injected as a HumanMessage into LangGraph state
  *   but NOT persisted to conversation history. On follow-up runs the skill body is lost.
  *   Pass `skills` to reconstruct the HumanMessage at the right position after each skill
- *   ToolMessage. Upstream PRs #96 / #97.
+ *   ToolMessage. PRs #96 / #97.
  * @returns - Object containing formatted messages and updated indexTokenCountMap if provided.
  */
 export declare const formatAgentMessages: (payload: TPayload, indexTokenCountMap?: Record<number, number | undefined>, tools?: Set<string>, skills?: Map<string, string>, options?: FormatAgentMessagesOptions) => {

package/dist/types/tools/ToolNode.d.ts

@@ -9,7 +9,7 @@ import type { ResolvedArgsByCallId } from '@/tools/toolOutputReferences';
 /**
  * Per-call batch context for `runTool`. Bundles every optional batch-scoped
  * value the method needs so the signature stays at three positional params
- * even as new context fields are added. Upstream-aligned (PR #117).
+ * even as new context fields are added. (PR #117).
  */
 type RunToolBatchContext = {
     /** Position of this call within the parent ToolNode batch. */
@@ -51,7 +51,7 @@ export declare class ToolNode<T = any> extends RunnableCallable<T, T> {
     private hookRegistry?;
     /**
      * Tool output reference registry threaded down from Run / Graph
-     * (upstream PR #114). When set, dispatchToolEvents resolves
+     * (PR #114). When set, dispatchToolEvents resolves
      * `{{tool<i>turn<n>}}` placeholders in args before invoking each tool
      * and stores successful outputs under their stable reference keys for
      * subsequent calls in the same run to pipe through.
@@ -112,7 +112,7 @@ export declare class ToolNode<T = any> extends RunnableCallable<T, T> {
     /**
      * Runs a single tool call with error handling.
      *
-     * @param batchContext  Optional per-batch context (upstream PR #117).
+     * @param batchContext  Optional per-batch context (PR #117).
      *   Threaded from `run()` for tool output reference annotation. The
      *   `batchScopeId` field carries an anonymous synthetic scope when the
      *   caller has no `run_id`, so concurrent batches don't collide on the

package/dist/types/tools/memory/shared.d.ts

@@ -67,7 +67,7 @@ export interface MemoryGetToolResult {
 export declare function buildMemorySearchUnavailableResult(error: string | undefined): MemorySearchToolResult;
 /**
  * Clamp a ranked result list to a total character budget.
- * Ported from upstream `tools.citations.ts::clampResultsByInjectedChars`.
+ * Ported from a reference implementation `tools.citations.ts::clampResultsByInjectedChars`.
  */
 export declare function clampResultsByInjectedChars<T extends {
     content: string;

package/dist/types/types/agent-cache.d.ts

@@ -9,13 +9,14 @@
  * for the active provider; consumers decide what content to put in each
  * block.
  *
- * Why this is generic rather than ranger-specific
+ * Why this is generic rather than tier-named
  * ------------------------------------------------
  * Earlier iterations exposed `platform_instructions` and `cache_ttl:
- * { platform, agent }` — vocabulary borrowed from a multi-tenant chat
- * platform's mental model. That leaked a specific consumer's domain into
- * the library and made it confusing for other consumers (CLI tools,
- * desktop apps, gateways) which have no notion of "platforms" or "agents".
+ * { platform, agent }` — vocabulary borrowed from a specific consumer's
+ * multi-tenant chat-platform mental model. That leaked one consumer's
+ * domain into the library and made it confusing for other consumers
+ * (CLI tools, desktop apps, gateways) which have no notion of
+ * "platforms" or "agents".
  *
  * The current shape lets every consumer define their own cache-tier
  * organization without the library knowing or caring.

package/dist/types/types/graph.d.ts

@@ -264,10 +264,11 @@ export type GraphEdge = {
     /**
      * EdgeType.HANDOFF — one-way routing: parent emits an `lc_transfer_to_*`
      *   tool call and exits, child takes over and responds directly to the
-     *   user. Aligns with upstream's handoff semantics.
+     *   user. Aligns with the standard handoff semantics.
      * EdgeType.DIRECT — fixed graph edges for automatic sequential / parallel
-     *   transitions. Ranger preserves its enriched wiring (fan-in with prompt,
-     *   parallel groups, ApprovalGateNode, excludeResults / agentMessages).
+     *   transitions. Downstream consumers may layer additional wiring on top
+     *   (fan-in with prompt, parallel groups, approval-gate nodes,
+     *   excludeResults / agentMessages).
      */
     edgeType?: import('@/common').EdgeType;
     /**
@@ -458,7 +459,7 @@ export interface SummarizationConfig {
      */
     initialSummary?: string;
     /**
-     * Upstream-aligned optional fields. When the host wants the summarization
+     * optional fields. When the host wants the summarization
      * pass to run on a different LLM than the agent's own (e.g. a cheaper
      * model for compaction), these provider/model overrides flow through to
      * the summarize callback.
@@ -622,9 +623,9 @@ export interface AgentInputs {
         tokenCount: number;
     };
     /**
-     * Upstream-aligned opt-in for summarization. When false, the agent never
+     * opt-in for summarization. When false, the agent never
      * invokes the summarize callback regardless of context utilization.
-     * Defaults to undefined (treated as enabled in Ranger to preserve prior
+     * Defaults to undefined (treated as enabled by default to preserve prior
      * behaviour); hosts that want strict opt-in semantics should set it
      * explicitly.
      */

package/dist/types/types/messages.d.ts

@@ -4,7 +4,7 @@ export type AnthropicMessages = Array<AnthropicMessage | BaseMessage>;
 export type AnthropicMessage = Anthropic.MessageParam;
 /**
  * Per-message ref metadata stamped onto a `ToolMessage` at execution time
- * (upstream PR #117). Read by `annotateMessagesForLLM` to apply transient
+ * (PR #117). Read by `annotateMessagesForLLM` to apply transient
  * annotation to a copy of the message right before it goes on the wire to
  * the provider. Never read after the run-scoped registry has been cleared.
  *

package/dist/types/types/run.d.ts

@@ -121,7 +121,7 @@ export type RunConfig = {
      */
     hooks?: HookRegistry;
     /**
-     * Tool output reference configuration (upstream PRs #114 / #117).
+     * Tool output reference configuration (PRs #114 / #117).
      * When `enabled` is true, the Run constructs a single
      * ToolOutputReferenceRegistry and threads it to every ToolNode built by
      * the graph so `{{tool<i>turn<n>}}` placeholders resolve across agents.

package/dist/types/types/tools.d.ts

@@ -60,13 +60,13 @@ export type ToolNodeOptions = {
     /**
      * Maximum characters for a single tool result (head+tail truncation).
      * When omitted, derived from the agent's `maxContextTokens` (30%
-     * heuristic), capped at HARD_MAX_TOOL_RESULT_CHARS. Upstream-aligned —
-     * Ranger's truncation today is driven by other knobs, but accepting
-     * this option keeps the test surface portable.
+     * heuristic), capped at HARD_MAX_TOOL_RESULT_CHARS. —
+     * downstream consumers may drive truncation through other knobs;
+     * accepting this option keeps the test surface portable.
      */
     maxToolResultChars?: number;
     /**
-     * Run-scoped tool output reference configuration (upstream PR #114).
+     * Run-scoped tool output reference configuration (PR #114).
      * When `enabled` is true, ToolNode registers successful outputs and
      * substitutes `{{tool<i>turn<n>}}` placeholders found in string args.
      * Ignored when `toolOutputRegistry` is also provided (the host-supplied
@@ -255,7 +255,7 @@ export type ToolExecuteResult = {
 /** Map of tool names to tool definitions */
 export type LCToolRegistry = Map<string, LCTool>;
 /**
- * Configuration for the tool output reference feature (upstream PR #114).
+ * Configuration for the tool output reference feature (PR #114).
  *
  * When `enabled: true`, ToolNode stores each successful tool output under
  * a stable key `tool<idx>turn<turn>` and the LLM can pipe a previous output

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@illuma-ai/agents",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "main": "./dist/cjs/main.cjs",
   "module": "./dist/esm/main.mjs",
   "types": "./dist/types/index.d.ts",

package/src/agents/AgentContext.ts

@@ -108,7 +108,7 @@ export class AgentContext {
     });
 
     /**
-     * Track upstream-aligned subagent inputs on the context. `_sourceInputs`
+     * Track subagent inputs on the context. `_sourceInputs`
      * preserves the original AgentInputs so SubagentExecutor can self-spawn
      * (`SubagentConfig.self === true`) without separate config; the other
      * two flow straight from agentConfig.
@@ -1004,7 +1004,7 @@ export class AgentContext {
    * appended unfiltered; outside event-driven mode they pass through
    * `filterToolsForBinding`. Centralizing the decision here prevents the
    * accounting/binding paths from drifting apart, which was the root
-   * cause of the original miscount (Fixes upstream #121).
+   * cause of the original miscount (Fixes #121).
    */
   private getEffectiveInstanceTools(): t.GraphTools | undefined {
     if (!this.tools) {

package/src/agents/__tests__/AgentContext.crossAgentTier1.live.test.ts

@@ -11,8 +11,9 @@
  * traffic).
  *
  * What it does NOT prove (out of scope here):
- *   - That ranger's actual `client.js` system block split is correct.
- *     That's verified by Phase 3 ranger-side tests.
+ *   - That a downstream consumer's actual system-block-assembly logic
+ *     produces a byte-identical Tier 1. That's the consumer's
+ *     responsibility (and its own tests).
  *
  * Run:
  *   BEDROCK_AWS_REGION=us-east-1 \
@@ -52,7 +53,8 @@ const describeFn = haveBedrock ? describe : describe.skip;
 
 /**
  * Tier 1 — platform-wide content. Same string for every "agent" in this
- * test, mimicking ranger's branding + tool routing + common tool docs.
+ * test, mimicking a multi-tenant platform's shared branding + tool-routing
+ * + common-tool documentation block.
  * Padded above 1024 tokens so Bedrock will write/read the cache (1024-token
  * minimum cache write threshold).
  */

package/src/agents/__tests__/AgentContext.test.ts

@@ -377,7 +377,7 @@ describe('AgentContext', () => {
     });
 
     it('excludes deferred-undiscovered instance tools from token accounting', async () => {
-      /* Regression for upstream #122 / #121.
+      /* Regression for #122 / #121.
        * `calculateInstructionTokens` previously summed every entry in
        * `this.tools` regardless of whether `getToolsForBinding` would
        * actually emit it. That over-reported tokens and triggered

package/src/common/__tests__/enum.test.ts

@@ -22,7 +22,7 @@ describe('EdgeType enum', () => {
     expect(EdgeType.HANDOFF).toBe('handoff');
   });
 
-  it('has correct DIRECT value (fixed graph edges with Ranger fan-in / parallel / approval-gate logic)', () => {
+  it('has correct DIRECT value (fixed graph edges, consumers may layer fan-in / parallel / approval-gate logic)', () => {
     expect(EdgeType.DIRECT).toBe('direct');
   });
 

package/src/common/enum.ts

@@ -103,19 +103,19 @@ export enum Providers {
 
 export enum EdgeType {
   /**
-   * Upstream-aligned handoff: one-way routing where the parent agent exits
+   * handoff: one-way routing where the parent agent exits
    * via a `lc_transfer_to_<destination>` tool call, the child takes over,
    * and the child responds directly to the user. Replaces what used to be
-   * called "TRANSFER" in earlier Ranger versions; the parent-calls-child
+   * called "TRANSFER" in older versions; the parent-calls-child
    * supervisor pattern (formerly `EdgeType.HANDOFF`) is gone — use the
    * Subagent primitive (Tier 5) for deep delegation instead.
    */
   HANDOFF = 'handoff',
   /**
-   * Fixed graph edges for automatic transitions. Naming matches upstream.
-   * Ranger keeps its enriched wiring on top of this edge type:
-   * fan-in with prompt + {results}, parallel groups, ApprovalGateNode
-   * insertion, and the `excludeResults` agentMessages channel.
+   * Fixed graph edges for automatic transitions. Standard naming.
+   * Downstream consumers may layer additional wiring on top of this edge
+   * type: fan-in with prompt + {results}, parallel groups, approval-gate
+   * node insertion, and the `excludeResults` agentMessages channel.
    */
   DIRECT = 'direct',
 }
@@ -195,15 +195,15 @@ export enum Callback {
 export enum Constants {
   OFFICIAL_CODE_BASEURL = 'https://api.illuma.ai/v1',
   EXECUTE_CODE = 'execute_code',
-  /** Tool name for the bash execution primitive (upstream Tier 3). */
+  /** Tool name for the bash execution primitive (Tier 3). */
   BASH_TOOL = 'execute_bash',
-  /** Tool name for the bash programmatic-tool-calling variant (upstream Tier 3). */
+  /** Tool name for the bash programmatic-tool-calling variant (Tier 3). */
   BASH_PROGRAMMATIC_TOOL_CALLING = 'run_tools_with_bash',
-  /** Tool name for the read-file primitive (upstream Tier 3). */
+  /** Tool name for the read-file primitive (Tier 3). */
   READ_FILE = 'read_file',
-  /** Tool name for the SkillTool primitive (upstream Tier 2). */
+  /** Tool name for the SkillTool primitive (Tier 2). */
   SKILL_TOOL = 'skill',
-  /** Tool name for the Subagent primitive (upstream Tier 5). */
+  /** Tool name for the Subagent primitive (Tier 5). */
   SUBAGENT = 'subagent',
   TOOL_SEARCH = 'tool_search',
   PROGRAMMATIC_TOOL_CALLING = 'run_tools_with_code',
@@ -270,7 +270,7 @@ export enum MessageTypes {
 /**
  * Tool names that use the code execution environment (shared session, file
  * tracking). Used by ToolNode to inject session context + file refs into
- * `invokeParams` before tool execution. Upstream-aligned constant.
+ * `invokeParams` before tool execution. constant.
  */
 export const CODE_EXECUTION_TOOLS: ReadonlySet<string> = new Set([
   Constants.EXECUTE_CODE,

package/src/graphs/Graph.ts

@@ -187,7 +187,7 @@ export abstract class Graph<
   hookRegistry?: import('@/hooks').HookRegistry;
   /**
    * Optional tool-output reference registry threaded down from Run
-   * (upstream PR #114). When set, every ToolNode built by this graph
+   * (PR #114). When set, every ToolNode built by this graph
    * stores successful outputs here and resolves `{{tool<i>turn<n>}}`
    * placeholders in args before invoking the tool.
    *
@@ -198,7 +198,7 @@ export abstract class Graph<
    */
   toolOutputRegistry?: import('@/tools/toolOutputReferences').ToolOutputReferenceRegistry;
   /**
-   * Run-scoped tool output reference configuration (upstream PR #117).
+   * Run-scoped tool output reference configuration (PR #117).
    * When `enabled` is true, the graph lazily allocates a single
    * `ToolOutputReferenceRegistry` on first `getOrCreateToolOutputRegistry()`
    * call and shares it with every ToolNode the graph compiles, so
@@ -1109,7 +1109,7 @@ export class StandardGraph extends Graph<t.BaseGraphState, t.GraphNode> {
     }
 
     /**
-     * Lazy tool-output reference annotation (upstream PR #117). Right
+     * Lazy tool-output reference annotation (PR #117). Right
      * before the message array hits the provider, walk it and apply
      * `[ref: tool<i>turn<n>]` prefixes / `_ref` JSON fields to a
      * transient copy. The persisted ToolMessages stay clean — only what
@@ -1720,7 +1720,7 @@ export class StandardGraph extends Graph<t.BaseGraphState, t.GraphNode> {
              * Fire PreCompact (#103) before the LLM call. Observational —
              * hosts may use the input to schedule auxiliary work, but a
              * deny/ask decision does NOT block compaction here because
-             * Ranger's summarizer runs in the background and a refusal
+             * the summarizer runs in the background and a refusal
              * has nowhere to go: pruning still needs to happen at 100%
              * regardless. Errors are swallowed so a hook bug cannot
              * masquerade as a context-overflow failure.
@@ -2716,7 +2716,7 @@ If I seem to be missing something we discussed earlier, just give me a quick rem
     }
 
     /**
-     * Subagent injection (upstream Tier 5): when the agent has SubagentConfig
+     * Subagent injection (Tier 5): when the agent has SubagentConfig
      * entries and depth budget remaining, inject a `subagent` DynamicStructuredTool
      * into graphTools. The tool's executor receives this graph's hookRegistry and
      * a lazy handler-registry getter (Run wires handlerRegistry AFTER createWorkflow,

package/src/graphs/MultiAgentGraph.ts

@@ -1006,7 +1006,7 @@ export class MultiAgentGraph extends StandardGraph {
 
     /**
      * Add approval-gate nodes for sequence edges that declare an approvalGate
-     * config (Ranger-only feature, not present upstream). Gates fire
+     * config (consumer extension, not part of the standard interface). Gates fire
      * regardless of ExecutionContext and sit between source and destination.
      */
     const gatedEdges = new Set<t.GraphEdge>();

package/src/graphs/gapFeatures.test.ts

@@ -1,7 +1,7 @@
 /**
  * gapFeatures.test.ts
  *
- * Integration tests for the four LibreChat gap features:
+ * Integration tests for the four gap features:
  * 1. Tool Discovery Caching
  * 2. SummarizationConfig (trigger types, initialSummary)
  * 3. EMA Pruning Calibration

package/src/graphs/phases/__tests__/memoryFlushPhase.test.ts

@@ -1,7 +1,7 @@
 import { shouldFlushMemory } from '../memoryFlushPhase';
 
 describe('shouldFlushMemory', () => {
-  // Use upstream-aligned defaults: soft=4000, reserve=20000 means a 200k
+  // Use defaults: soft=4000, reserve=20000 means a 200k
   // window fires at 176k. Explicit numbers here keep the test independent
   // from the constants file.
   const base = {

package/src/graphs/phases/memoryFlushPhase.ts

@@ -1,7 +1,7 @@
 /**
  * Memory flush phase — trigger logic + reflection invocation.
  *
- * Ported from upstream's post-turn flush handler. The agent is re-invoked
+ * Ported from the reference implementation's post-turn flush handler. The agent is re-invoked
  * with a reflection system prompt and the `memory_append` tool unlocked;
  * it writes notes to its future self, then the graph returns to normal.
  *
@@ -45,7 +45,7 @@ export interface ShouldFlushInput {
 /**
  * Pure trigger function: fires when the current context is within
  * `softThreshold + reserveFloor` tokens of the model window. Matches
- * upstream's formula.
+ * the standard formula.
  */
 export function shouldFlushMemory(input: ShouldFlushInput): boolean {
   if (

package/src/hooks/HookRegistry.ts

@@ -24,7 +24,7 @@ type MatcherBucket = Partial<Record<HookEvent, HookMatcher<HookEvent>[]>>;
  *
  * ## Why `Map<sessionId, MatcherBucket>` and not `Record`
  *
- * LibreChat runs thousands of parallel sessions in one Node process, and
+ * Real consumers run thousands of parallel sessions in one Node process, and
  * hook registration happens inside hot paths (tool loading, agent spawning).
  * A `Record<sessionId, ...>` has to be spread on every insertion, which is
  * O(n) per call and O(n²) total for a batch of parallel registrations. A

package/src/hooks/index.ts

@@ -1,6 +1,6 @@
 // src/hooks/index.ts
 //
-// Hook lifecycle system for `@librechat/agents`. Re-exported from
+// Hook lifecycle system for `@illuma-ai/agents`. Re-exported from
 // `src/index.ts` and consumed by `Run.processStream` (RunStart,
 // UserPromptSubmit, Stop, StopFailure), `ToolNode.dispatchToolEvents`
 // (PreToolUse, PostToolUse, PostToolUseFailure, PermissionDenied),

package/src/hooks/matchers.ts

@@ -129,7 +129,7 @@ function skipGroupSyntaxPrefix(pattern: string, start: number): number {
  * This catches the common forms but not all. Ambiguous-alternation ReDoS
  * like `(a|a)+` is not detected. Pathologically long patterns are also
  * caught by {@link MAX_PATTERN_LENGTH}. Hosts that accept user-supplied
- * patterns must still validate upstream.
+ * patterns must still validate standard.
  */
 export function hasNestedQuantifier(pattern: string): boolean {
   const stack: QuantifierFrame[] = [];
@@ -248,7 +248,7 @@ function compile(pattern: string): RegExp | null {
  *    never re-enter the regex compiler.
  *
  * These are a floor, not a ceiling. Hosts that accept user-supplied
- * patterns should still validate upstream. The design report §3.8 routes
+ * patterns should still validate standard. The design report §3.8 routes
  * persistable hooks through a host-side compiler before they reach this
  * module.
  */

package/src/hooks/types.ts

@@ -7,7 +7,7 @@ import type { BaseMessage } from '@langchain/core/messages';
  * These mirror the subset of Claude Code's event surface that makes sense
  * for a library context (no filesystem/CLI-specific events). See
  * `docs/hooks-design-report.md` §3.2 for the mapping to existing
- * `@librechat/agents` emission points.
+ * `@illuma-ai/agents` emission points.
  */
 export const HOOK_EVENTS = [
   'RunStart',

package/src/llm/anthropic/utils/server-tool-inputs.test.ts

@@ -4,11 +4,11 @@ import type { BaseMessage } from '@langchain/core/messages';
 import { _convertMessagesToAnthropicPayload } from './message_inputs';
 
 describe('_convertMessagesToAnthropicPayload — server tool use (web search) multi-turn', () => {
-  /* Skipped: ranger intentionally diverged from upstream's
+  /* Skipped: this fork intentionally diverged from the reference implementation's
    * `_convertLangChainToolCallToAnthropic` — local always emits
    * `tool_use` regardless of `srvtoolu_` ID prefix (see message_inputs.ts
-   * line ~144). These tests assert upstream's server_tool_use emission
-   * which ranger does not implement. The text→server_tool_use correction
+   * line ~144). These tests assert the standard server_tool_use emission
+   * which this fork does not implement. The text→server_tool_use correction
    * test (next, "corrects text-typed server tool blocks") still passes
    * because that path lives in `_formatContent`. */
   it.skip('corrects tool_use blocks with srvtoolu_ IDs to server_tool_use', () => {
@@ -161,7 +161,7 @@ describe('_convertMessagesToAnthropicPayload — server tool use (web search) mu
     });
   });
 
-  /* Skipped: depends on upstream's server_tool_use emission, see header. */
+  /* Skipped: depends on the standard server_tool_use emission, see header. */
   it.skip('filters server tool calls when content is a string', () => {
     const messageHistory: BaseMessage[] = [
       new HumanMessage('search for X'),
@@ -204,7 +204,7 @@ describe('_convertMessagesToAnthropicPayload — server tool use (web search) mu
     expect(serverToolBlocks).toHaveLength(0);
   });
 
-  /* Skipped: depends on upstream's server_tool_use emission, see header. */
+  /* Skipped: depends on the standard server_tool_use emission, see header. */
   it.skip('handles empty string content with only server tool calls', () => {
     const messageHistory: BaseMessage[] = [
       new HumanMessage('search for X'),
@@ -229,7 +229,7 @@ describe('_convertMessagesToAnthropicPayload — server tool use (web search) mu
     expect(assistantContent[0].text).toBe(' ');
   });
 
-  /* Skipped: depends on upstream's server_tool_use emission, see header. */
+  /* Skipped: depends on the standard server_tool_use emission, see header. */
   it.skip('preserves regular tool_use blocks alongside corrected server tool blocks', () => {
     const messageHistory: BaseMessage[] = [
       new HumanMessage('search for X and calculate 2+2'),
@@ -358,7 +358,7 @@ describe('_convertMessagesToAnthropicPayload — server tool use (web search) mu
   });
 
   /**
-   * Regression for LibreChat discussion #12806.
+   * Regression for discussion #12806.
    *
    * Anthropic web_search responses can include text blocks whose text is
    * whitespace-only (e.g. ' ', '\n', '\t') alongside server_tool_use and

package/src/llm/bedrock/__tests__/bedrock-caching.test.ts

@@ -361,7 +361,7 @@ describe('Bedrock Prompt Caching', () => {
     };
 
     describe('Bedrock system message with promptCache: true', () => {
-      /* Updated contract (2026-05-01, upstream PR #128 alignment): Bedrock
+      /* Updated contract (2026-05-01, PR #128 alignment): Bedrock
        * system message gets a `cachePoint` block inline so the system
        * prefix is cached at the AWS account level (cross-user). Previously
        * cachePoint was only added at the tool level, leaving the system
@@ -487,7 +487,7 @@ describe('Bedrock Prompt Caching', () => {
 
         // Bedrock system messages now carry an inline cachePoint so the
         // system prefix gets cached at the AWS account level (matching
-        // upstream PR #128). Tool-level cachePoint from
+        // PR #128). Tool-level cachePoint from
         // IllumaBedrockConverse.invocationParams() runs independently.
         expect(Array.isArray(content)).toBe(true);
         expect(content.some((c) => 'cachePoint' in c)).toBe(true);

package/src/llm/bedrock/cacheSupport.ts

@@ -10,7 +10,7 @@
  *
  * Consumers can extend the allowlist with `bedrockCacheModelPatterns` in
  * `clientOptions` for proprietary or pre-release model IDs not yet in
- * the upstream library.
+ * the reference library.
  */
 
 /**

package/src/llm/bedrock/index.ts

@@ -77,8 +77,8 @@ export type ToolGroupSelector = (toolName: string) => string;
 /**
  * Default group selector — puts all tools in a single group named 'core'.
  * Equivalent to 'single' strategy but explicit. Consumers override this
- * to enable per-source grouping (e.g. ranger uses `_mcp_` substring to
- * separate core from MCP tools).
+ * to enable per-source grouping (e.g. by inspecting tool-name substrings
+ * to separate stable framework tools from volatile MCP-sourced tools).
  */
 export const DEFAULT_TOOL_GROUP_SELECTOR: ToolGroupSelector = () => 'core';
 

package/src/llm/openai/index.ts

@@ -896,8 +896,8 @@ export interface XAIUsageMetadata
 }
 
 export class ChatMoonshot extends ChatOpenAI {
-  static lc_name(): 'LibreChatMoonshot' {
-    return 'LibreChatMoonshot';
+  static lc_name(): 'IllumaMoonshot' {
+    return 'IllumaMoonshot';
   }
 
   protected _convertMessages(messages: BaseMessage[]): OpenAICompletionParam[] {

package/src/llm/openai/utils/index.ts

@@ -302,7 +302,7 @@ export function _convertMessagesToOpenAIParams(
   model?: string,
   options?: ConvertMessagesOptions
 ): OpenAICompletionParam[] {
-  /* DeepSeek reasoning roundtrip (upstream PR #136): reasoning_content on
+  /* DeepSeek reasoning roundtrip (PR #136): reasoning_content on
    * an AI message must be re-sent only when the message participates in a
    * tool-call exchange. Track context across the message flat-map. */
   let hasReasoningToolCallContext = false;
@@ -454,7 +454,7 @@ export function _convertMessagesToOpenAIParams(
       }
     }
 
-    /* DeepSeek reasoning roundtrip (upstream PR #136): emit
+    /* DeepSeek reasoning roundtrip (PR #136): emit
      * reasoning_content only when the message is part of a tool-call
      * exchange — either the message itself has tool_calls, or a previous
      * AI/tool message established the context. Skipping the gate causes