Expose linked TinyBus module registration

[senamakel]

Summary

Builds on the static-link API already merged to main: one module declaration now selects dynamic or linked TinyBus exports through module_export_optional_static!, and the crate root exposes linked_module(). TinyBus uses an exact version dependency with a local workspace patch. The nested TinyBus checkout is pinned to commit 433d9ed from tinyhumansai/tinybus#29.

Draft readiness condition: TinyBus PR #29 must merge, then this repository must pin its merged commit and pass CI before this PR is marked ready or merged.

Related issue

None.

API or behavior changes

With static-link, Rust hosts can call tinyconnectors::linked_module() to register this module in process. linked remains an alias for static-link.

Validation

• cargo check -p tinyconnectors --locked
• cargo check -p tinyconnectors --features static-link --locked
• cargo fmt --all -- --check
• git diff --check
• cargo test -p tinyconnectors --features static-link --test static_link --locked

Tests

The existing static export test passes. Full repository suites were not run locally.

Documentation

The crate-root function has rustdoc; the TinyBus dependency PR documents the host registration API.

Checklist

• The change is focused on linked module integration
• No new #[ignore] or relaxed lint settings
• No secrets or credentials in the change

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

_{Comment @coderabbitai help to get the list of available commands.}