test(acceptance): expect multi-rule connections in flag order

TestConnectionWithMultipleRules passes filter, retry and delay flags and
asserted the old fixed order (filter, delay, retry). Rules now follow
flag order, so assert filter, retry, delay.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: leggetter

test/acceptance/connection_test.go

@@ -1495,7 +1495,7 @@ func TestConnectionWithDeduplicateRule(t *testing.T) {
 	t.Logf("Successfully created and verified connection with deduplicate rule: %s", conn.ID)
 }
 
-// TestConnectionWithMultipleRules tests creating a connection with multiple rules and verifies logical ordering
+// TestConnectionWithMultipleRules tests creating a connection with multiple rules and verifies they follow flag order
 func TestConnectionWithMultipleRules(t *testing.T) {
 	if testing.Short() {
 		t.Skip("Skipping acceptance test in short mode")
@@ -1508,8 +1508,7 @@ func TestConnectionWithMultipleRules(t *testing.T) {
 	sourceName := "test-src-multi-" + timestamp
 	destName := "test-dst-multi-" + timestamp
 
-	// Note: Rules are created in logical order (deduplicate -> transform -> filter -> delay -> retry)
-	// This order matches the API's default ordering for proper data flow through the pipeline.
+	// Rules built from --rule-* flags follow the position of each rule type's first flag
 	var conn Connection
 	err := cli.RunJSON(&conn,
 		"gateway", "connection", "create",
@@ -1541,23 +1540,23 @@ func TestConnectionWithMultipleRules(t *testing.T) {
 	require.NotEmpty(t, getConn.Rules, "Connection should have rules")
 	require.Len(t, getConn.Rules, 3, "Connection should have exactly three rules")
 
-	// Verify logical order: filter -> delay -> retry (deduplicate/transform not present in this test)
-	assert.Equal(t, "filter", getConn.Rules[0]["type"], "First rule should be filter (logical order)")
-	assert.Equal(t, "delay", getConn.Rules[1]["type"], "Second rule should be delay (logical order)")
-	assert.Equal(t, "retry", getConn.Rules[2]["type"], "Third rule should be retry (logical order)")
+	// Verify flag order: filter -> retry -> delay
+	assert.Equal(t, "filter", getConn.Rules[0]["type"], "First rule should be filter (flag order)")
+	assert.Equal(t, "retry", getConn.Rules[1]["type"], "Second rule should be retry (flag order)")
+	assert.Equal(t, "delay", getConn.Rules[2]["type"], "Third rule should be delay (flag order)")
 
 	// Verify filter rule details
 	assertFilterRuleFieldMatches(t, getConn.Rules[0]["body"], `{"type":"payment"}`, "body")
 
 	// Verify delay rule details
-	assert.Equal(t, float64(1000), getConn.Rules[1]["delay"], "Delay should be 1000 milliseconds")
+	assert.Equal(t, float64(1000), getConn.Rules[2]["delay"], "Delay should be 1000 milliseconds")
 
 	// Verify retry rule details
-	assert.Equal(t, "exponential", getConn.Rules[2]["strategy"], "Retry strategy should be exponential")
-	assert.Equal(t, float64(5), getConn.Rules[2]["count"], "Retry count should be 5")
-	assert.Equal(t, float64(60000), getConn.Rules[2]["interval"], "Retry interval should be 60000")
+	assert.Equal(t, "exponential", getConn.Rules[1]["strategy"], "Retry strategy should be exponential")
+	assert.Equal(t, float64(5), getConn.Rules[1]["count"], "Retry count should be 5")
+	assert.Equal(t, float64(60000), getConn.Rules[1]["interval"], "Retry interval should be 60000")
 
-	t.Logf("Successfully created and verified connection with multiple rules in logical order: %s", conn.ID)
+	t.Logf("Successfully created and verified connection with multiple rules in flag order: %s", conn.ID)
 }
 
 // TestConnectionWithRateLimiting tests creating a connection with rate limiting