Ramnique Singh d42fb26bcc allow per-track model + provider overrides ... Track block YAML gains optional `model` and `provider` fields. When set, the track runner passes them through to `createRun` so this specific track runs on the chosen model/provider; when unset the global default flows through (`getTrackBlockModel()` + the resolved provider). The track skill picks up the new fields automatically via the embedded `z.toJSONSchema(TrackBlockSchema)` and adds an explicit "Do Not Set" section: copilot leaves them omitted unless the user named a specific model or provider for the track. Common bad reasons ("might be faster", "in case it matters", complex instruction) are called out so the defaults stay the path of least resistance. Track modal Details tab shows the values when set, in the same conditional `<dt>/<dd>` style as the lastRun fields. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-24 16:58:18 +05:30
..
apps	allow per-track model + provider overrides	2026-04-24 16:58:18 +05:30
packages	allow per-track model + provider overrides	2026-04-24 16:58:18 +05:30
.gitignore	bootstrap new electron app	2026-01-16 12:05:33 +05:30
eslint.config.mts	ignore renderer eslint	2026-01-16 12:05:33 +05:30
package.json	integrate electron forge	2026-01-17 10:28:44 +05:30
pnpm-lock.yaml	preserve formatting in chat input text	2026-04-23 21:29:51 +05:30
pnpm-workspace.yaml	fix pnpm postinstall	2026-01-21 10:47:44 +05:30
TRACKS.md	Add tracks — auto-updating note blocks with scheduled and event-driven triggers	2026-04-14 13:51:45 +05:30
tsconfig.base.json	bootstrap new electron app	2026-01-16 12:05:33 +05:30