Why

The docs show the async respond API introduced after v0.3.0, but their dependency blocks still select the v0.3.0 Git tag. Copying the Rust example produces E0308 and E0277. The published Python wheel also has the old synchronous API.

What

• Use the same main branch for libsy and protocol in Getting Started, the libsy README, and the Rust API reference.
• Explain that these examples follow the unreleased async API, while v0.3.0 uses synchronous respond.
• Point Python readers to building matching bindings from the same source checkout.

Three documentation files: 18 additions / 8 deletions. No runtime changes, new tests, or quickstart restructuring. This is separate from the library-first onboarding work.

Validation

• Reproduced the original Rust compilation errors with the documented v0.3.0 dependencies.
• Compiled the actual Rust handler as an external consumer against all three updated dependency blocks; each resolved main at 5415db205 and passed.
• Built the Python wheel from the same checkout, then exercised the documented async respond line with a mock judge call. The handler ran and the expected target was selected.
• Ran the linked Python embedding example with that wheel.
• Strict MkDocs build passed.
• Warning-strict rustdoc build passed for libsy and protocol.
• git diff --check passed.

No live provider calls or release publication.

Summary by CodeRabbit

• Documentation
  • Updated setup and API documentation to clarify that current examples use the asynchronous response API, while version 0.3.0 uses the synchronous API.
  • Updated dependency examples to reference the repository’s current development branch.
  • Clarified Python client response types and guidance for building bindings from the current source.