lziff-github 0.1.3

GitHub backend for lziff. Future plugin candidate; stays compile-time isolated from the lziff body.
Documentation

GitHub review backend for lziff.

════════════════════════════════════════════════════════════════════════ FUTURE PLUGIN — DO NOT IMPORT FROM lziff INTERNALS ════════════════════════════════════════════════════════════════════════

This crate is the GitHub-specific [ReviewProvider] implementation. It will eventually be split out into a separate process speaking the review-protocol JSON-RPC over stdio. To keep that future viable:

  • The crate's Cargo.toml depends on review-protocol and serde_json only. Adding lziff = ... here is a hard policy violation — nothing in the GitHub plugin should know what's inside the host.
  • All public types and methods are reachable through the [ReviewProvider] trait. The host (crates/lziff/src/main.rs via crates/lziff/src/review.rs) only ever obtains a Box<dyn ReviewProvider> from [make_provider] and never names GithubProvider directly.
  • We shell out to the user's gh CLI (already authenticated). Going through HTTP+OAuth is left for the eventual stand-alone plugin once we hit a perf/feature wall.