[rmcdaniel]

Part of #325. Follows #570, which has merged.

Native now lists, updates and backfills schedules as published Server 2.5.14 does.

What changes

• Listing (GET /api/schedules). Supports PHP's filters with Laravel's validation messages and PHP's refusal bodies, including last_safe_cursor.
  • The schedule visibility query accepts equality predicates joined by AND. They work on ScheduleId, Status, WorkflowType, TaskQueue, Note and registered search attributes.
  • Continuation tokens are signed as PHP signs them, using DW_SERVER_KEY or APP_KEY. When neither is set, native uses its auth token, not a per-container key, so tokens survive restarts and work on every node. Each token is bound to its namespace and filters, and is refused once its cursor is gone.
  • The SQL is built from fixed fragments with bound values on every database family.
• Update (PUT /api/schedules/{id}). Merges the action with the stored one, recomputes the run quota and next fire time, and records PHP's changed_fields.
• Backfill (POST /api/schedules/{id}/backfill). Fires every occurrence in the range once, from the start time up to but not including the end time, as triggerForBackfill does.
  • Buffering policies start every occurrence, already fired occurrences are skipped, and the run quota ends the backfill.
  • Fire times carry PHP's offsets: the schedule zone's for a cron occurrence, UTC for an interval.
• Validation fix. Laravel sizes a non-numeric value under a numeric rule by its string length. Native now does the same, so page_size=x reports only the integer rule.

Deliberate differences

• Backfill times must be ISO-8601. PHP's other strtotime forms, such as +1 day or @timestamp, get the date validation message.
• A backfill range with more than 10,000 occurrences is refused with 422 backfill_range_too_large. PHP has no limit.
• An update to a specification that cannot be evaluated returns 422. PHP returns an unhandled 500.

Evidence

• New cron-oracle/backfill-dates.php: PHP's date rule and instant for 700 seeded strings. Native refuses everything PHP refuses and matches every instant to the microsecond.
• The next-fire corpus now also records PHP's offsets (600 cases), and native matches all of them.
• New schedule-catalog parity fixture (72 requests, with a reviewed PHP copy). Locally, published PHP, embedded and native pass it, and PHP and native agree on every normalized response.
• A PHP-on-PostgreSQL HTTP diff matched native on 81 responses. The only differences were the deliberate ones above.
• Schedule tests pass on SQLite, PostgreSQL, MySQL 8.4 and MariaDB 10.11.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud