⬆️ chore: Bump LibreChat Packages to Latest & Support New Schema

[danny-avila]

Summary

Bumps the LibreChat packages to their latest releases and adapts the admin panel to the new schema, capabilities, permissions, and audit actions:

• @librechat/data-schemas: 0.0.56 → 0.0.74
• librechat-data-provider: 0.8.509 → 0.8.524

Audit log. LibreChat now records permission.insights_assigned / permission.insights_removed when Insights access on an agent changes. The BFF response validator only accepted grant.* actions, and the backend doesn't filter by category by default, so a single Insights entry would fail validation and break the whole audit log page. The panel now accepts all four actions and renders Insights entries with:

• an agent target
• a "View insights" subject
• a Grantee row in the detail drawer

Both the action filter and the target-type filter cover the new entries.

Role permissions. Added the new SCHEDULES permission type (Use / Create) to the role editor.

interface.schedules runtime toggle. Upstream now treats bare interface.schedules as a runtime enable/disable (RUNTIME_CONFIG_INTERFACE_FIELDS), not a permission. Before this change, the panel's interface-permission guard silently dropped that write. The guard now follows upstream:

• the boolean toggle is saved
• use / create sub-keys stay blocked
• an object with use: false collapses to false

Langfuse. Removed the forward-compat schema shim now that the pinned data-provider ships the langfuse group. Visibility handling is unchanged: the section is still hidden when LibreChat reports fanout disabled.

Config schema.

• Added section meta for the new top-level filters (Features tab), permissions, and openapi (System tab).
• Added English labels for ~190 new fields and for the new read:insights / manage:code_environments capabilities.

Follow-ups (not in this PR)

• The new langfuse.trace.* settings (userIdField, metadata fields) aren't editable yet, because the Langfuse section uses a custom connection renderer.
• Single-value literal fields such as managementApi.auth.oidc.tokenUse still render as text inputs. This is existing behaviour, and validation rejects invalid values.

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Testing

• Added coverage for the Insights audit helpers, a label/summary locale check for every audit action, and the runtime interface.schedules path and strip behaviour.
• Added sample overrides for new fields with stricter validation in the config round-trip suite.
• bunx tsc --noEmit
• bun run test (1157 tests passed)
• bun run lint
• bun run build

Not yet exercised against a live LibreChat backend.

Test Configuration:

• Bun 1.4.0

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• 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