Revit Automate Test

Use this skill to prove a Revit plugin works through the same path a user actually uses:

understand feature behavior
  -> map user actions to automation primitives
  -> build/deploy package
  -> real Revit .addin loading mechanism
  -> current deployed artifact evidence
  -> Revit Journal/plugin log startup evidence
  -> real ribbon/command/WPF UI entry point
  -> Revit model-view mouse input when the plugin waits for user picks
  -> independent result evidence

Do not replace host E2E validation with direct service calls unless the user explicitly asks for service-level testing. Do not treat bundled scripts as the test plan. The agent must analyze each plugin feature, choose the right action sequence, execute it with the scripts, and judge the result from independent evidence.