test(ci): control branch to date the server-tools failure

[gHashTag]

Draft, not for merge. Comment-only change to queen-tick.ts so the Tests workflow's path filter fires with no behaviour change.

Tests / server-tools failed on #472 and the workflow has no prior run on this branch to compare against, so "already red" could not be asserted from history. This dates it: if server-tools fails here too, the failure predates the verdict-matching fix.

Close and delete once the answer is recorded.

[github-actions]

✅ Tests passed — 2057/2088

Suite	Passed	Failed	Skipped
✅ agent	87/87	0	0
✅ build	9/9	0	0
✅ cdp-protocol	5/5	0	0
✅ eval	93/93	0	0
✅ server-agent	272/272	0	0
✅ server-api	944/974	0	30
✅ server-browser	6/6	0	0
✅ server-integration	10/11	0	1
✅ server-lib	273/273	0	0
✅ server-pglive	3/3	0	0
✅ server-root	68/68	0	0
✅ server-skills	31/31	0	0
✅ server-tools	242/242	0	0
✅ shared	14/14	0	0

View workflow run

[gHashTag]

Answer recorded: server-tools passed here on a comment-only change, so it is not already red. Re-running the identical commit on #472 then passed as well — same SHA, one fail and one pass, and the failure was a harness crash (browser/dbus, "Test run failed before JUnit output was written") rather than an assertion. Not attributable to the verdict-matching change; recorded as a measurement, not diagnosed as flake.