Migrate hero_indexer to standard Hero Service 5-crate architecture #2

New issue

Open

opened 2026-02-23 10:32:30 +00:00 by despiegk · 0 comments

despiegk commented

2026-02-23 10:32:30 +00:00

Owner

Description

The hero_indexer project uses a monolithic 2-crate layout (heroindex server + heroindex_client) that doesn't follow the Hero Service standard. It needs to be split into the 5-crate pattern used by hero_redis, hero_voice, and hero_services:

hero_indexer — core library (types, index manager, RPC handlers)
hero_indexer_openrpc — backend binary (raw JSON-RPC over Unix socket)
hero_indexer_http — HTTP admin UI + proxy (port 8809)
hero_indexer_client — async client SDK
hero_indexer_rhai — Rhai scripting bindings (placeholder)

### Description The hero_indexer project uses a monolithic 2-crate layout (heroindex server + heroindex_client) that doesn't follow the Hero Service standard. It needs to be split into the 5-crate pattern used by hero_redis, hero_voice, and hero_services: - `hero_indexer` — core library (types, index manager, RPC handlers) - `hero_indexer_openrpc` — backend binary (raw JSON-RPC over Unix socket) - `hero_indexer_http` — HTTP admin UI + proxy (port 8809) - `hero_indexer_client` — async client SDK - `hero_indexer_rhai` — Rhai scripting bindings (placeholder)