fix(desktop): per-job model picker for cron editor

[HexLab98]

Summary

• Add an optional Model field to the Desktop New/Edit cron job dialog so each scheduled job can pin a provider/model (or keep Default to follow the profile).
• Wire create/update payloads through the existing cron REST model/provider fields; show the pinned model in job detail.
• Localize the new labels across en/zh/zh-hant/ja.

Test plan

• Open Desktop Cron → New cron job; confirm a Model select appears under Frequency/Deliver.
• Leave Model on Default, create a job; confirm the job has no pinned model and still runs on the profile default.
• Create another job pinned to a non-default model; confirm detail shows provider · model and the next run uses that pin.
• Edit a pinned job back to Default; confirm the pin clears on save.
• Script-only jobs hide the Model field.
• From apps/desktop: npx vitest run src/app/cron/cron-job-model.test.ts

Infographic

[alt-glitch]

This was generated by AI during triage.

Related to #49948: both add Desktop per-job provider/model selection. #49948 also carries cron/API/profile plumbing, while this branch is a newer focused editor implementation with different selection and clearing behavior. Please choose a consolidation path.

[teknium1]

Thanks for filling a real Desktop gap: current main's cron editor cannot send model/provider even though the REST create schema accepts both (apps/desktop/src/app/cron/index.tsx:388-405; hermes_cli/web_server.py:10419-10427, :10739-10749).

Problems

• The picker loads active-profile model data through getGlobalModelOptions() (apps/desktop/src/hermes.ts:1010-1014), but cron list/create/update calls remain unscoped (apps/desktop/src/hermes.ts:869-903). The create endpoint defaults to profile="default" (hermes_cli/web_server.py:10763-10765), so a non-default profile can select a valid local model and save the job into a different profile.
• cronEditorUpdates() always sends model and provider (apps/desktop/src/app/cron/cron-job-model.ts:211-213). The dialog hides this control for script-only jobs (apps/desktop/src/app/cron/index.tsx:772-773), so saving one clears stored pins without an editable field.

Suggested changes

• Scope every Desktop cron API request with profileScoped() and cover non-default-profile request routing.
• Skip model/provider updates for script-only jobs and assert preservation in the helper tests.
• Please reconcile this implementation with the maintainer-linked open #49948, which already includes cron profile routing work.

Automated hermes-sweeper review.

[teknium1]

This runs for script-only edits too, even though the dialog hides the Model field. Saving a script-only job will therefore clear its stored inference pins without user intent. Gate both inference fields on !options.scriptOnlyJob, and add a preservation test.

[teknium1]

Thanks @HexLab98 for the contribution — this landed on main via #67472 (merged today, same feature: grouped provider/model picker fed by the model.options catalog, default-clears-pin semantics, script-only jobs excluded, 4 locales). The script-only concern from the sweeper review is covered there, and the profile-scoping gap is addressed in the follow-up #67493. Closing as superseded — appreciate the quick turnaround on the community request.