enricobuehler
44d40808f9
`Sc2Device.strippedOutputLen` said its parity with the host's `triton::out_report_len` meant "a drift on either side fails CI". It does not: the Swift test transcribes the host numbers into a literal, so it catches an edit made in Swift and is blind to one made in Rust — which would leave the client trimming its GATT writes to a stale length. Say what the guard actually covers, on both sides, so whoever edits either table knows it owes the other.
pf-driver-proto
The shared host ↔ driver binary contract for punktfunk's Windows pf-vdisplay virtual display — the control IOCTLs and the IDD-push frame transport, defined exactly once.
It's a path dependency of both the host workspace (crates/punktfunk-host)
and the out-of-workspace driver workspace (packaging/windows/drivers/),
so it must resolve identically from either build graph. That's why it's deliberately self-contained:
no_std (+ alloc), platform-neutral (GUID/LUID are plain integers each side converts to its own OS
type), and free of *.workspace = true inheritance.
Defining every wire struct here — with const size/offset asserts and bytemuck round-trips — turns
host↔driver ABI drift into a compile error instead of a silent frame or IOCTL corruption.
See the crate root (src/) for the wire types; the Windows virtual-display design is in
the internal planning repo (punktfunk-planning: windows-virtual-display-rust-port.md).