The plates step needs the install, because the WorldFrame does

`test-no-install` caught it: a plate is parented to the `WorldFrame`, which
comes from FrameXML off the patch chain, so with `WOW_DATA=` there is nothing to
parent to and nothing for the fixture's own scan to walk. Skipped without the
install like its render and use-probe siblings — which is also the honest
statement about that VM, since a plate addon can do nothing in it either.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SgstFWtn1RxEJ5kVrpgYwn

crates/benilla-app/src/addon_harness/probe_tests.rs

@@ -140,8 +140,13 @@ fn a_folder_without_a_manifest_is_refused() {
 /// parent a frame to it. So this test is also the contract check on the plate's own shape — a
 /// plate that stopped being a `Button`, or stopped putting its border first, would read here as
 /// an addon that adopted nothing.
+///
+/// Needs the install: a plate is parented to the `WorldFrame`, and the `WorldFrame` comes from
+/// FrameXML off the patch chain. With no chain there is nothing to parent to and nothing for the
+/// fixture's own scan to walk, which is also why a plate addon can do nothing in that VM.
 #[test]
 fn the_plate_step_seats_plates_and_counts_the_ones_an_addon_adopted() {
+    benilla_formats::wow_data_or_skip!();
     let fx = Fixtures::new("plates");
     fx.addon(
         "Plater",