Typed error hierarchy for Wolbarg 0.6 — ValidationError, RerankError, StorageLockedError, CancellationError, and more.

Hierarchy

WolbargError — base
ConfigurationError — bad config
- ProviderNotConfiguredError — method needs a missing provider (e.g. compress without llm)
InitializationError — open / probe failed
ValidationError — bad method arguments (including hybrid/rerank misconfig)
DatabaseError / EmbeddingError / CompressionError
RerankError — built-in reranker HTTP / empty ranking failure
MemoryNotFoundError
VersionConflictError — CAS mismatch on expectedVersion
StorageLockedError — code WOLBARG_STORAGE_LOCKED
CancellationError — AbortSignal cancelled an in-flight operation
wrapOperationError — helper to wrap unknown errors

Fail-closed hybrid / rerank (0.6.0)

Situation	Error
`hybrid: true` without `keywordSearch`	`ValidationError`
`rerank: true` without `reranker`	`ValidationError`
Built-in reranker provider failure	`RerankError`

There is no silent semantic-only or identity-order fallback. See Hybrid Search and Rerankers.

Thrown when SQLite write-lock retries are exhausted under multi-process contention.

Field	Meaning
Code	`WOLBARG_STORAGE_LOCKED`
When	`BEGIN IMMEDIATE` / busy retries exceed `concurrency.maxRetries`
Suggestion	Increase retries / `lockTimeoutMs`, reduce writer fan-out, or switch to Postgres

Thrown when signal aborts during remember / recall / update / compress / forget (and related helpers). In-flight embedding HTTP aborts.

GraphCheckpointNotSupportedError and graph-related ProviderNotConfiguredError examples are obsolete — graph memory was removed in 0.6.0.