Track: loop-nested flow conditions never convert to CEL (upstream objectstack#4347)

[yinlianghui]

Upstream: objectstack-ai/objectstack#4347 — that is the canonical report, with the reproduction. This issue exists only to track the hotcrm side; the details live upstream so the two cannot drift apart.

What it means for hotcrm

applyConversionsToFlow does not recurse into loop.config.body, so a bare string condition inside a loop is never converted to CEL and is string-compared instead — the gate silently never opens. Three flows shipped inert because of it (opportunity_stagnation, contract_renewal, campaign_enrollment).

Current state — worked around, not blocked

• Every loop-nested condition is authored as an explicit envelope via the P tagged template (fix(flows): author conditions as CEL envelopes so they actually evaluate #565, fix(flows): unbreak main — contract_renewal throws; rewrite the two tests #565 turned red #566).
• test/flow-scheduled.test.ts walks every registered flow, including nested loops, and fails if any loop body reintroduces a bare string condition. It also asserts the walk found something, so it cannot pass vacuously.
• A companion test pins the engine asymmetry that makes the envelope necessary, so an upstream fix shows up as a deliberate review rather than a silent behaviour change.

When objectstack#4347 ships

1. Bump @objectstack/service-automation.
2. The "engine still treats a bare string differently from an envelope" test will go red — that is the signal, not a regression.
3. Decide whether to relax the loop-body guard from fail to warn. Keeping the explicit envelopes is harmless either way; the guard is what stops the class coming back.

Related: #495 (surfaced it), #563, #565, #566.