Defect in VST3 Validator's "Valid State Transition" test?

The VST3 SDK’s validator includes a test called “valid state transition”, included below. My plugin wasn’t passing this test, but on closer inspection it appears to be an issue with the validator’s behavior.

If I understand correctly, it is illegal to terminate an AudioProcessor, initialize it and then set it to active without first calling setProcessing.† The workflow diagrams in the VST3 SDK docs imply as much. I could implement fault-tolerant behavior by retaining the processing configuration between initializations, or substituting a default processing configuration, but both of these behaviors seem incorrect.

Is my plugin expected to tolerate this behavior, or is this a defect in the validator?

bool PLUGIN_API VstValidStateTransitionTest::run (ITestResult* testResult)
{
	if (!testResult || !vstPlug)
		return false;

	printTestHeader (testResult);

	for (int32 i = 0; i < 3; ++i)
	{
		tresult result = vstPlug->setActive (true);
		if (result != kResultTrue)
			return false;

		result = vstPlug->setActive (false);
		if (result != kResultTrue)
			return false;

		result = vstPlug->terminate ();
		if (result != kResultTrue)
			return false;

		result = vstPlug->initialize (gStandardPluginContext);
		if (result != kResultTrue)
			return false;
	}
	return true;
}

† (See VST3 Processor Call Sequence, from the documentation)

Hi thanks for founding it, this will be fixed in the next update. SetProcessing should be called before activation.