d668a3a66a Migrate entity graph from SQLite to Neo4j backend API (#9)
* Migrate entity graph from local SQLite to remote Neo4j backend API

Replace Tauri IPC invoke() calls with REST API calls to /api/entity-graph/
endpoints. EntityManager public API is unchanged so all consumers (AIProvider,
EntityQuery, SkillRegistry) need no modifications.

- Rewrite manager.ts to use apiClient instead of Tauri invoke()
- Add Neo4j response types and conversion helpers in types.ts
- Remove Rust entity_db.rs (607 lines) and rusqlite dependency
- Remove 12 ai_entity_* commands from Tauri generate_handler

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Add Git workflow guidelines to CLAUDE.md

- Introduced a new section outlining the requirement for all pull requests to target the `develop` branch instead of `main`. This update aims to standardize the contribution process and improve collaboration among developers.

* Enhance EntityManager with optimistic concurrency control for tag management

- Introduced MAX_TAG_RETRIES constant to handle HTTP 409 Conflict errors during tag addition and removal.
- Refactored addTag and removeTag methods to implement retry logic using If-Match headers for optimistic concurrency control.
- Updated search and getByTag methods to utilize URLSearchParams for improved query handling.
- Simplified entity fetching logic in getById and search methods to enhance performance and clarity.

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-31 20:56:54 +05:30

Tauri + React + Typescript

This template should help get you started developing with Tauri, React and Typescript in Vite.

S
Description
No description provided
Readme GPL-3.0
220 MiB
Languages
Rust 59.1%
TypeScript 37.9%
JavaScript 1.6%
Shell 1.2%
CSS 0.1%