internal/

Package chunk defines lore's chunk data model and the structure-aware chunker, decided in https://github.com/cheetahbyte/lore/issues/7 and https://github.com/cheetahbyte/lore/issues/8.

Package config implements lore's minimal config file, decided in https://github.com/cheetahbyte/lore/issues/3: only embeddings provider settings and per-crawled-source options live here, everything else is pure CLI args.

Package embed implements the optional embeddings path decided in https://github.com/cheetahbyte/lore/issues/7: vector search is opt-in, never generated in-process (no bundled/local model, per the research on issue #6) — always an external API call.

Package identity implements lore's typed-prefix source identity scheme, decided in https://github.com/cheetahbyte/lore/issues/8.

Package ingest wires the Source adapters (issue #8), the chunker (issue #7), the optional embedder (issue #7), and the Store (issue #10) together into the `lore add`/`lore refresh` flows (issue #3).

Package logging implements lore's local logging approach, decided in https://github.com/cheetahbyte/lore/issues/13: log/slog, always to stderr (stdout is reserved for MCP protocol traffic during `lore serve`), with a text or JSON handler and level controlled by --verbose or LORE_LOG_LEVEL (flag wins).

Package mcpserver implements the MCP tool surface decided in https://github.com/cheetahbyte/lore/issues/2: stdio transport, three tools (list_libraries, resolve_library, search_docs), read-only over the local index — no tool can trigger ingestion.

Package retrieval implements the hybrid FTS+vector fusion decided in https://github.com/cheetahbyte/lore/issues/7.

Package source implements the Source interface and its four adapters, decided in https://github.com/cheetahbyte/lore/issues/8: each adapter only resolves identity/versions and fetches raw content — chunking is one shared pipeline stage in the ingest package, not reimplemented per adapter.

Package store implements the Store interface decided in https://github.com/cheetahbyte/lore/issues/10: everything above this package (ingestion, retrieval, MCP handlers) talks only to Store, never to a concrete database type, so a future hosted backend can be a second implementation rather than a rewrite.