docs: refactor Kobo API findings into a reference document #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "kobo-api-docs-refactor"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
docs/kobo-api-findings.md(chronological field notes) withdocs/kobo-api.md— a reference-shaped document for external self-hosters documenting the Kobo sync protocol.KoboReader.sqlitestate. Contributing footer with three lightweight maintenance conventions.internal/kobo/handler.gonow has a subsection with Implementation, Called by, Purpose, Request, Response, Quirks, and Reference implementations fields.README.mdlinks updated to point at the new file.docs/superpowers/specs/2026-04-20-kobo-api-docs-refactor-design.md; implementation plan atdocs/superpowers/plans/2026-04-20-kobo-api-docs-refactor.md.Test plan
docs/kobo-api.mdin a markdown viewer — ToC links resolve, code fences close, Chapter 5 anchor links jump to the correct Chapter 4 subsections.internal/kobo/handler.gohas a matching subsection (expected: 19 H4 endpoint headings)./v1/initialization,/v1/library/sync,/v1/library/{id}/metadata,/v1/analytics/gettests, and the download endpoint.docs/kobo-api-findings.mdis gone andREADME.mdno longer links to it.