Problem
The core model, UI-neutral renderer, GTK widget, index library, and JSON Lines adapter are reusable, but their contracts remain pre-1.0 and are not published as supported integration artifacts. Threading, cancellation, errors, limits, versioning, and migration guarantees need documentation.
Acceptance criteria
- Supported Rust APIs document examples, errors, limits, cancellation, and thread/callback behavior.
- Independent consumers build against each supported boundary.
- The JSON Lines protocol has published schemas, golden fixtures, and version negotiation.
- Semantic-versioning and migration policies are documented.
- Generated API documentation is published from reviewed releases.
- A GObject-introspection or other non-Rust renderer binding is either specified or explicitly deferred with rationale.
Problem
The core model, UI-neutral renderer, GTK widget, index library, and JSON Lines adapter are reusable, but their contracts remain pre-1.0 and are not published as supported integration artifacts. Threading, cancellation, errors, limits, versioning, and migration guarantees need documentation.
Acceptance criteria