Rust-a-Log 0.1.1: LAN logs and remote TUI

Rust-a-Log 0.1.1 adds authenticated LAN log collection and remote viewing.

• Bind the collector to a LAN address with a token from RUAL_TOKEN.
• Use rual connect HOST:PORT --tui or --json to view a receiver on another machine.
• Retain source status, recent history, structured fields, and discarded counts in remote views.
• Configure LAN endpoints and tokens in Go, Node.js/TypeScript, .NET, and Java adapters.
• Add standard-library adapters for Python logging and Ruby Logger.
• Preserve the fast file reader, filters, following, and rotation.
• Bound incomplete frames, handshake deadlines, queues, history, and slow subscriber writes.

The README includes service configuration, LAN examples, SSH tunnels, and all six language adapters.
A Windows Python service sent logs directly to a Mac receiver across the LAN.
A Mac TUI read the Windows receiver over direct LAN TCP after a scoped Windows firewall rule.
The rule restricts access to the rual executable, receiver IP, TCP port 7331, and one Mac viewer on the Private profile.
Live updates, source selection, level and text filters, pause, structured fields, and wrong-token rejection passed.
An SSH tunnel is optional. The README includes the Windows firewall and PowerShell setup.
All adapter examples passed token-authenticated integration checks.

Archives include the executable, license, documentation, and adapter sources. Linux binaries use musl for static linking.
Windows binaries support x64. macOS archives support Intel and Apple Silicon; Linux archives support x64 and ARM64.
Each target passed native Rust tests and an executable version check. Check downloads with SHA256SUMS.

Direct TCP sends tokens and logs without encryption. Use a trusted LAN or an SSH tunnel.
Streams are best effort. Remote viewers require a new connect command after disconnection.
macOS binaries are unsigned and are not notarized.

Install with cargo install rust-a-log --version 0.1.1 --locked.