v0.3.20: KB Tag fixes

[icecrasher321]

Summary

• fix(kb-tag-slots): finding next slot, create versus edit differentiation (fix(kb-tag-slots): finding next slot, create versus edit differentiation #882)

Type of Change

• Bug fix

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sim (staging)	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 5, 2025 9:06pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Skipped (Inspect)			Aug 5, 2025 9:06pm

[greptile-apps]

Greptile Summary

This PR implements a comprehensive fix for knowledge base tag slot allocation reliability issues. The changes move tag slot allocation logic from unreliable client-side implementation to a robust server-side system.

Core Changes:

• Server-side slot allocation: New API endpoint /next-available-slot handles slot finding with proper database queries and field type validation
• Database constraints: Added unique composite index on knowledge_base_id + display_name to prevent duplicate tag names within knowledge bases
• Field type system: Restructured slot management with TAG_SLOT_CONFIG to support different field types (currently 'text', designed for future expansion to date/number)
• Edit vs Create differentiation: Added _originalDisplayName field to properly handle tag definition updates without creating new slots unnecessarily
• Enhanced UI: New useNextAvailableSlot hook provides clean client interface with loading states and comprehensive slot information

System Integration:
The changes integrate across multiple layers: database schema updates, API route enhancements, React hooks, and UI components. The slot allocation now uses a configuration-driven approach mapping field types to specific database columns (tag1, tag2, etc.) with proper limits. Transaction-based operations ensure data consistency during bulk tag operations. The system maintains backward compatibility while providing a foundation for future field type expansion.

Confidence score: 4/5

• This PR addresses a real reliability issue with a well-architected server-side solution that should significantly improve tag management
• Score reflects good overall approach but concerns about type assertions to 'any' and some code duplication that could affect maintainability
• Pay close attention to the API route files where type safety was compromised with any assertions

Context used:

Context - Avoid using type assertions to 'any' in TypeScript. Instead, ensure proper type definitions are used to maintain type safety. (link)

_{11 files reviewed, 6 comments}

_{Edit Code Review Bot Settings | Greptile}