Summary
Backend capability docs are inconsistent with the inspected implementation. Some docs still describe several backends as planned, while the worker registers implemented support for file://, optional kv://, and SQLite-backed storage.
References
- Backend docs and SDK guide describe planned backend status
- Worker backend registration includes
PosixBackend, optional KVBackend, and SQLiteBackend
- Backend registry code supports scheme-based resolution
Impact
Users may not know which URI schemes are currently supported, experimental, or planned. This can lead to incorrect examples and confusion when configuring kv:// or SQLite paths.
Suggested Fix
Create one authoritative backend support table with statuses such as implemented, optional/configured, experimental, and planned. Link all docs to that table and update examples to match the branch's actual behavior.
Summary
Backend capability docs are inconsistent with the inspected implementation. Some docs still describe several backends as planned, while the worker registers implemented support for
file://, optionalkv://, and SQLite-backed storage.References
PosixBackend, optionalKVBackend, andSQLiteBackendImpact
Users may not know which URI schemes are currently supported, experimental, or planned. This can lead to incorrect examples and confusion when configuring
kv://or SQLite paths.Suggested Fix
Create one authoritative backend support table with statuses such as implemented, optional/configured, experimental, and planned. Link all docs to that table and update examples to match the branch's actual behavior.