Graceful error handling

Prioritize graceful error handling over panicking by providing fallbacks and propagating rich context. When operations can fail:

1. For non-critical failures, use fallbacks instead of unwrap(): ```rust // Instead of this: let pos = std.stream_position().unwrap();

// Prefer this: let pos = std.stream_position().unwrap_or(0);

2. For functions that may panic with assertions, add `#[track_caller]` to improve error diagnostics:
```rust
#[track_caller]
pub fn global_queue_interval(&mut self, val: u32) -> &mut Self {
    assert!(val > 0, "global_queue_interval must be greater than 0");
    // ...
}

1. When exposing errors, implement the full std::error::Error trait including the source() method to maintain the error chain.

2. In documentation examples, demonstrate proper error handling rather than ignoring or silencing errors: ```rust // Instead of ignoring errors: let _ = compress_data(reader).await;

// Show proper error handling: compress_data(reader).await?; ```

1. Consider providing configuration options for users to handle certain error conditions differently when appropriate.