rodecaster-protocol 0.15.0

JUCE var / ValueTree codec and transport frame for the RODECaster Pro II / Duo wire protocol
Documentation
# Hardware capture corpus

These fixtures are external protocol evidence. They must originate from real
RODECaster hardware, not from this crate's encoders.

## Full-sync fixtures

`<model>/fw-<version>/full-sync.frame` is one complete TCP transport frame:

```text
[u32 LE magic][u32 LE payload length][JUCE full-sync payload]
```

The checked-in frame is sanitized with `examples/sanitize_full_sync.rs`. The
sanitizer preserves node and property names, ordering, value types, array and
binary lengths, model discriminator, and firmware version. It replaces all
identity, credential, user-content, and state values with neutral values.

Every fixture directory contains a `manifest.toml` recording its provenance,
expected topology, and checksum. Raw captures must never be committed.

## Adding a full sync

1. Capture the `rc_audio_mixer` response to a fresh GUI/client connection.
2. Extract exactly one complete transport frame.
3. Keep the raw frame outside the repository.
4. Sanitize it:

   ```bash
   cargo run --example sanitize_full_sync -- raw.frame full-sync.frame
   ```

5. Inspect the sanitizer summary and create `manifest.toml`.
6. Add model-contract assertions in `tests/captured_full_sync.rs`.
7. Run the complete test suite and strict Clippy.

The integration test recursively verifies that only sanitizer-approved values
remain. This is a second guard against accidentally committing device secrets.

## Behavioral traces

The next corpus layer will store directional command/event traces under
`<model>/fw-<version>/traces/`. A trace must record the user action and raw
frames observed in each direction. Expected semantic events and command bytes
must be authored from the capture, never generated by the crate under test.