chore: release v0.2.0

[github-actions]

🤖 New release

• vlanctl: 0.1.0 -> 0.2.0 (⚠ API breaking changes)

⚠ vlanctl breaking changes

--- failure constructible_struct_adds_field: struct exhaustively constructible through public API adds field ---

Description:
A pub struct that could be exhaustively constructed with a literal using only public API has a new pub field, breaking existing exhaustive literals.
        ref: https://doc.rust-lang.org/reference/expressions/struct-expr.html
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.50.0/src/lints/constructible_struct_adds_field.ron

Failed in:
  field State.backend in /tmp/.tmpAcw2qy/vlanctl/src/state.rs:49
  field State.parent in /tmp/.tmpAcw2qy/vlanctl/src/state.rs:56
  field RecordingRunner.stdout_queue in /tmp/.tmpAcw2qy/vlanctl/src/net.rs:49

Changelog

0.2.0 - 2026-09-30

Added

• --report for a caller that cannot read vlanctl's output, and Serialize on Profile
• a second Windows backend on the adapter driver's VLAN keyword, chosen by profile shape
• Windows backend through Hyper-V virtual adapters and netsh
• (commands) tell "could not check" apart from "failed" after a clean run
• (commands) let a caller recover which interfaces failed verification
• (conflict) say why a probe could not run, as something to match on
• (conflict) ask the wire whether an address is already held
• (permanence) render a profile to netplan, renderer-aware
• (commands) prove an apply against the host, not the exit code
• (commands) prove a teardown against the host, not the exit code

Documentation

• describe the Windows backend for readers of the crate

Fixed

• (conflict) import Instant only where the ARP probe uses it
• (windows) don't report the driver backend's own parent as a teardown survivor
• (windows) put the parent's own address back after the switch is removed
• (windows) fail loudly when New-VMSwitch can't actually bind the adapter
• (windows) leave the stack's multicast and broadcast neighbors alone on teardown
• (windows) let the driver backend re-apply, and say why netsh failed
• tear the previous profile down through the backend that applied it
• (permanence) take the renderer rules the bench proved, not the ones it disproved

---

This PR was generated with release-plz.