test(flow): pin each node's declared config vocabulary; quiet the phpmd threshold trip

The coverage ratchet was right: a vocabulary declaration with no assertion is
a claim nothing checks. Each node's configKeys() is now pinned against the
documented set — the preflight refuses keys outside it and the editor renders
one field per entry, so drift between declaration and what the node reads
would make real options unreachable through both.

phpmd: SynchronizationRunNode sat exactly at the complexity threshold before
the one-line configKeys() tipped it; suppressed with the rationale on the
class, mirroring the fleet's pattern for branchy-by-nature classes.

Author: rubenvdlinde

lib/Flow/SynchronizationRunNode.php

@@ -83,6 +83,12 @@
  * Runs a configured Synchronization as one flow step, fanning out its objects.
  *
  * @spec openspec/changes/openconnector-flow-nodes/tasks.md#task-4-synchronizationrunnode-with-bounded-fan-out-seed-data-and-a-live-end-to-end-run
+ *
+ * @SuppressWarnings(PHPMD.ExcessiveClassComplexity) The class sat at the
+ *   threshold before `configKeys()` — a one-line vocabulary declaration —
+ *   tipped it over. The complexity is the count of distinct ways a run
+ *   config and its fan-out can be wrong; splitting the class would move
+ *   that branching, not remove it.
  */
 class SynchronizationRunNode implements IFlowNode, IFlowNodeConfigKeys {
 

tests/Unit/Flow/SourceCallNodeTest.php

@@ -147,6 +147,24 @@ public function testPaletteMetadata(): void {
 
 	}//end testPaletteMetadata()
 
+
+	/**
+	 * The declared vocabulary is what the node actually reads.
+	 *
+	 * The preflight refuses keys outside this list and the flow editor renders
+	 * one field per entry, so a key the node reads but does not declare becomes
+	 * unreachable through both — this pins the two against each other.
+	 *
+	 * @return void
+	 */
+	public function testConfigKeysNameTheVocabularyTheNodeReads(): void {
+		$this->assertSame(
+			['source', 'endpoint', 'method', 'query', 'headers', 'body', 'output', 'concurrency'],
+			$this->node->configKeys()
+		);
+
+	}//end testConfigKeysNameTheVocabularyTheNodeReads()
+
 	/**
 	 * Scope is answered with Nextcloud's constants and false for anything else.
 	 *

tests/Unit/Flow/SynchronizationRunNodeTest.php

@@ -135,6 +135,24 @@ public function testPaletteMetadata(): void {
 
 	}//end testPaletteMetadata()
 
+
+	/**
+	 * The declared vocabulary is what the node actually reads.
+	 *
+	 * The preflight refuses keys outside this list and the flow editor renders
+	 * one field per entry, so a key the node reads but does not declare becomes
+	 * unreachable through both — this pins the two against each other.
+	 *
+	 * @return void
+	 */
+	public function testConfigKeysNameTheVocabularyTheNodeReads(): void {
+		$this->assertSame(
+			['synchronization', 'force', 'output', 'maxItems', 'onError'],
+			$this->node->configKeys()
+		);
+
+	}//end testConfigKeysNameTheVocabularyTheNodeReads()
+
 	/**
 	 * An inline synchronization definition is rejected at save.
 	 *