v0.8.53: indexing fixes

[waleedlatif1]

• improvement(ui): centralize product colours in global CSS (improvement(ui): centralize product colours in global CSS #8116)
• fix(knowledge): index the connector tombstone check so a sync stops scanning the whole document table (fix(knowledge): index the connector tombstone check so a sync stops scanning the whole document table #8122)
• fix(knowledge): bound source titles and tag values so an oversized index row cannot fail a connector sync (fix(knowledge): bound source titles and tag values so an oversized index row cannot fail a connector sync #8123)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 22, 2026 3:50am UTC

[greptile-apps]

Confidence Score: 4/5

The behavioral changes appear sound, but the repository’s component-local styling requirement must be satisfied before merging.

Findings

1.  Global Styling Violates Requirements ▶

Summary

This PR improves knowledge connector indexing reliability and centralizes several UI colors.

• Adds a partial connector tombstone index using the repository’s concurrent-index migration pattern.
• Bounds indexed document filenames and tag values, truncating machine-provided connector values without splitting surrogate pairs.
• Moves collaborator and product colors to CSS variables and updates selection/caret rendering for both CSS-variable and legacy hex colors.
• The global theme edit conflicts with the repository’s explicit styling requirements.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  API[Document API input] --> Validate[Reject filenames and tags over 512 units]
  Connector[Connector source data] --> Truncate[Truncate titles and mapped tags to 512 units]
  Validate --> Write[Document persistence]
  Truncate --> Write
  Write --> Indexes[Filename and tag btree indexes]
  Sync[Connector tombstone query] --> Tombstone[Partial connector tombstone index]

Loading

_{Reviews (1) · Last reviewed commit: "fix(knowledge): bound source titles and ..."}

[greptile-apps]

Global Styling Violates Requirements

This adds eight color variables in a new global @theme block. The repository requires styling changes to remain local to components and specifically says to avoid editing globals.css unless absolutely necessary. This requirement must be satisfied before merging by keeping these colors in the relevant component styles or retaining local color values.

Rule Used: Avoid editing the globals.css file unless absolutely necessary. Move style changes to local component files instead. (source)

Learned From
simstudioai/sim#367

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!