GeezerVison

Why

The review of #32063 asked how the browser preview of an automation's next runs stays in agreement with the server (review, reply). The reviewer found that cron-parser accepts specs that Standard rejects, such as 0 9 * * 7, and resolves clock-change days in its own way. This adds the shared test vectors promised in that reply, plus two small fixes that the review of #32063 left open.

Part of CODAGT-1135.

What changed

• testdata/standard_vectors.json lists specs that Standard accepts and rejects (each rejection has a short reason) and the runs that Next gives around clock changes in America/New_York, Europe/Berlin, Australia/Lord_Howe and Pacific/Chatham. Times are RFC 3339 with an offset. TestStandard_Vectors checks every entry against the code. A test of the preview can read the same file, so a difference between the two fails CI on one side. The file holds the reviewer's cases: 0 9 * * 7, 0 9 L * *, 0 9 * * 1#2 and 0 0 9 * * * are rejected, 30 2 * * * on 2026-03-08 runs at 03:00 EDT, and */15 * * * * on 2026-11-01 runs at 01:45 EDT and then 02:00 EST. The run entries replace the table of TestStandard_Next_DST (same values, now read from the file).
• Standard compares the zone name rules posix, right, Local, localtime, posixrules and Factory without letter case. A host with a case-insensitive file system could load factory as the file Factory. New table cases cover factory, LOCAL, LOCALTIME, POSIX/UTC and Right/UTC.
• A test comment said that six zones changed at 15:33:32 like Juneau. They changed at other times with seconds. The comment now says so.

Scope

Next and MinInterval do not change, and neither does the syntax that Standard accepts: widening it (for example 7 for Sunday) is a product decision for the RFC. No new API and no frontend.

Tradeoffs

• The file ties the preview to every entry in it. That is its purpose.
• reason is for a person. The test checks that a rejected spec has one, not its text, so rewording a Go error does not change the contract.
• The file has no comment because JSON has none. The test's doc comment says what the file is for.

Live check

None: a library change with no caller yet.

Generated with xum • Model: anthropic:claude-sonnet-5-5 • Thinking: xhigh