test(agent): pin the scheduled task card contract - ScheduledTaskCard

[dmitrii-f-t27]

Summary

Hold the one export of trios/agent-server/apps/agent/entrypoints/app/scheduled-tasks/ScheduledTaskCard.tsx — ScheduledTaskCard — against its contract (#1550), so the next change to that file has something to fail against.

The block is appended to lib/schedules/scheduleStorage.test.ts by the same readdir rule that file documents for the #1634 and #1580 blocks: the card imports the store suite's subject through useScheduledJobRuns, whose module that file already materialized real behind its own stand-ins.

The card is held as a full source contract, no render — and the first CI run of this PR is the measured reason: the card's graph also reaches the llm-providers store, whose own suite (lib/llm-providers/storage.test.ts) pins the defineItem interception of its own storage seam, recorded at that module's first materialization. Bun links and runs test files one by one, so whichever order the two files meet in, a card import from this suite materializes that store first (or replaces it) and poisons the llm-providers suite's pins — measured both directions (the first run failed Tests / agent with exactly that suite's nine pins). The source-contract block imports nothing: no render, no new global stand-ins, order-proof in both directions.

What is pinned:

• the switch on the enabled flag with its Disable/Enable label template, the name and quoted query, and the Disabled badge gated on the disabled flag;
• the provider and last-run rows gated on their loaded values with the relative-time line;
• the Test and Edit buttons with their handlers, labels and icons, and the delete behind its name label;
• the schedule lines through the measured set (Daily at, Every hour, Every N hours, Every minute, Every N minutes, Not scheduled) and the durations through the running note and the minute-second split;
• the run-history counted title, the completed/failed icon branches with the running spinner, and the cancel and retry controls gated behind their statuses and aria-labels with the per-row View action.

Verification

• bun test lib/schedules/scheduleStorage.test.ts — 41 pass, 0 fail (4 new tests).
• Broken-copy proof: inverting the switch-label ternary plus renaming the daily line turns exactly the first two tests red; the copy restores clean via git checkout.
• Mixed-order runs, both directions (lib/schedules/ + entrypoints/app/scheduled-tasks/ + lib/llm-providers/): 79 pass, 0 fail each way — the llm-providers suite stays green with this block in either link order.
• biome ci on the suite file: clean, no findings. tsgo --noEmit: 0 mentions of the suite file.

Closes #1550

Dmitrii Fedorov (@dmitrii-f-t27)

[tri-claw]

Summary by t27-bees

The PR adds contract tests for ScheduledTaskCard by reading its source file and asserting on regex patterns in the code. This avoids rendering the component because importing it would re-materialize the store and break the existing scheduleStorage and llm-providers test pins due to module linking order.

Worth a look

• trios/agent-server/apps/agent/lib/schedules/scheduleStorage.test.ts (lines 1245–1343): The four it blocks assert on very specific regex patterns (exact spacing, quote style, template-literal structure). Any formatting change — Prettier, a added space, switching single/double quotes — will fail the tests even though the component behavior is unchanged. The tests verify source shape, not behavior.

• trios/agent-server/apps/agent/lib/schedules/scheduleStorage.test.ts (line 1233): taskCardCode() strips only whole-line comments (//, *, /*). Inline comments inside a pattern (e.g., checked={job.enabled /* controlled */}) would remain and cause the regex to miss, producing a false negative.

• trios/agent-server/apps/agent/lib/schedules/scheduleStorage.test.ts (lines 1250, 1253, 1256): The switch assertions (checked={job.enabled}, onCheckedChange={onToggle}, the aria-label template) are coupled to the exact JSX attribute syntax. A refactor to spread props ({...switchProps}) or a wrapper component would break all three tests at once.

• trios/agent-server/apps/agent/lib/schedules/scheduleStorage.test.ts (lines 1280, 1283): The icon checks (<Play />, <Pencil />, <Trash2 />) only verify the component name appears somewhere in the file. They don't confirm the icons are actually used on the correct buttons, so a swap (e.g., Trash2 on the Test button) would still pass.

• trios/agent-server/apps/agent/lib/schedules/scheduleStorage.test.ts (lines 1295, 1298, 1301): The schedule-line assertions (Daily at ${job.scheduleTime}, Every ${job.scheduleInterval} hours, etc.) assume the singular/plural branches are written as separate ternary branches in the source. If the component switches to a helper function or a lookup table, the tests fail despite identical output.

---

_{Read: 1 files, +116 -0, the whole diff. Head c18174f. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.}

[github-actions]

✅ Tests passed — 3886/3956

Suite	Passed	Failed	Skipped
✅ agent	429/429	0	0
✅ build	9/9	0	0
✅ cdp-protocol	5/5	0	0
✅ eval	93/93	0	0
✅ server-agent	280/280	0	0
✅ server-api	2244/2313	0	69
✅ server-browser	6/6	0	0
✅ server-integration	10/11	0	1
✅ server-lib	279/279	0	0
✅ server-pglive	166/166	0	0
✅ server-root	68/68	0	0
✅ server-sim	8/8	0	0
✅ server-skills	31/31	0	0
✅ server-tools	244/244	0	0
✅ shared	14/14	0	0

View workflow run