[rmcdaniel]

Datetime visibility literals are currently passed to Laravel as DateTime objects. SQL preparation formats their local wall time and drops microseconds, so equivalent offsets and neighboring instants return the wrong runs. Bind the existing UTC/microsecond representation before building typed attribute and system timestamp predicates.

This is the separate Server predicate portion of durable-workflow/workflow#898 and complements durable-workflow/workflow#914. It does not change the package pin or repair existing rows.

Validation: a constructed SQLite table cohort executes forty actual Eloquent predicates against five equivalent UTC/offset values, including local-day boundaries, a one-microsecond neighbor, equality/inequality, IN/negated IN, ranges, system StartTime and namespace isolation. Unchanged source fails all forty without query errors; the corrected class passes all forty. The initial fixture used unsupported Field NOT IN syntax and remains a separate unsuccessful setup; the qualified fixture uses the existing NOT Field IN grammar. Production PHP/SQL dependencies come from the published Server2.11.1 image with only the candidate support class explicitly mounted. This is source-component SQL evidence, not installed acceptance of a new image or a full HTTP test result.

Committed API regressions exercise the same cases through the workflow-list route. Fresh exact-head normal CI and network-database/HTTP acceptance remain required. No schema, Composer, release metadata, native/shared/runner/OpenAPI or frozen-actor edit. Existing published-image and security prerequisites are unchanged.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud