rustduck-core 1.1.0

Safe typed TSDuck core bindings for rustduck
Documentation
# rustduck-core

The safe implementation layer that turns the unsafe [`rustduck-sys`](https://docs.rs/rustduck-sys)
boundary into the typed API re-exported by the [`rustduck`](https://docs.rs/rustduck)
facade. It owns Rust lifetimes, native handle ownership, parameter validation,
typed configuration, error mapping, and callback/FFI safety membranes.

## Module ownership

- `processor.rs`, `input_switcher.rs`, `system_monitor.rs`, `analyzer.rs`,
  `section_file.rs`, `context.rs`, `report.rs`, `plugin.rs`
- `memory/`: queue, endpoint, registry, and private callback routing
- `transport_stream.rs`: packet-size and layout constants

The authoritative ownership rules are in
[architecture](https://github.com/CyberKoo/rustduck/blob/master/docs/ai/architecture.md). Raw pointer operations
belong in narrow FFI/adapter functions; ordinary queue, plugin, validation, and
public-model code stays safe Rust.

## Development

Building requires TSDuck 3.44.x; see
[rustduck-sys requirements](https://docs.rs/crate/rustduck-sys/latest).

```sh
cargo test -p rustduck-core
cargo test -p rustduck-core --test binding
cargo test -p rustduck-core --test native_failures
```

`native_failures` injects native exceptions through `rustduck-sys`' test hooks,
which this crate's tests enable with a dev-dependency instead of a public feature.

## AI development rules

[Safe Rust and APIs](https://github.com/CyberKoo/rustduck/blob/master/docs/ai/rust.md) ·
[Native boundaries](https://github.com/CyberKoo/rustduck/blob/master/docs/ai/native-boundary.md) ·
[Change workflow](https://github.com/CyberKoo/rustduck/blob/master/docs/ai/workflow.md)

## Third-party notices

This crate reaches TSDuck through `rustduck-sys`. See the workspace
[third-party notices](https://github.com/CyberKoo/rustduck/blob/master/THIRD-PARTY.md); TSDuck is BSD 2-Clause.