Rule schema: conditions array/null union shape returns 400 on visual-builder PUT

[rubenvdlinde]

Surfaced during the #877 browser smoke-test (PR #908).

The Rule schema declares conditions as a union type (array or null). When the visual condition builder serialises a non-empty condition tree as a JSON object (e.g. {"and": [{"var": ["user.email"]}]}) and PUTs it, OR's validation rejects it with HTTP 400 — the schema only accepts array or null at that path, not an object.

Repro

1. Create a rule via the openconnector UI (/rules → Add)
2. Open the rule detail page (feat(rules): bespoke Rule editor with visual condition + action builder (closes #833) #873)
3. Use the visual condition builder to add a single var leaf
4. Save → PUT returns 400 {"error":"Validation failed: conditions must be array or null"}

Root cause

JsonLogic's canonical shape is a top-level object ({op: [...args]}), not an array. The schema typing is wrong.

Fix options

1. Change conditions type to object or object | null to match JsonLogic shape (preferred)
2. Wrap the visual builder's output in an array at the frontend level ([{and: [...]}]) — but then backend evaluators need updating to unwrap

Option 1 is the right model. The backend already expects JsonLogic shape per jwadhams/json-logic-php's API.

Scope

Schema migration in OR's openconnector register (the rule schema definition lives in lib/Repair/InitializeRegister.php or similar). Test that existing rules with null conditions stay null; existing rules with already-wrapped-in-array conditions get unwrapped or stay wrapped (backend tolerates both).

[rubenvdlinde]

Shipped via PR #928 (merged 2026-05-23).

Live-verified against dev container before merge:

• POST /objects/openconnector/rule with object-shape conditions ({"and": [{"var": ["user.email"]}]}) -> 200 (was 400)
• PUT update with deeper builder output (and of var + ==) -> 200, object round-trips
• PUT with conditions: null -> 200, null preserved (backwards compat for existing rules)
• POST without conditions -> 200, defaults to null

Schema descriptor (lib/Settings/openconnector_register.json) updated, rule schema bumped 1.0.0 -> 1.1.0, top-level register version bumped 1.0.0 -> 1.1.0 so ConfigurationService::importFromApp() picks up the new shape on next occ upgrade. Closing.