settings: give freeModel.enabled a home in Agents (fix base web red)
Base web is red: webviews/src/pages/settings/categories.test.ts "every page row has exactly one home" fails because freeModel.enabled (cx-ds09i part 1) has no card on the settings page.
This gives it one. SettingsPageLayout now lists the schema group settings.group.freeModel ("AI Models", already in the catalog and strings.json) in the Agents category, after Computer Use. The setting is about which model agents use, and its keywords are agents and models, so Agents fits it better than Accounts. Accounts has only host cards and no schema groups. No new strings and no new category.
If Lawrence's cx-ds09i part 2 places this row differently, his PR simply moves it.
The settings export was regenerated on the fleet (export-settings step 06c1a34e213c91bf2153ab93, exclusive). The only change is the new group in page.agents. The MDM exports are unchanged.
No UI recording: this adds one settings row to an existing card layout.
Testing
- Red on base
ee8d80672c35:heavy --mem 4G bun test src/pages/settings/categories.test.tsgives 5 pass, 1 fail (- "freeModel.enabled"missing from the placed rows). - Green on head: the same command gives 6 pass, 0 fail.
heavy --mem 4G bun run check(webviews): pass.- The Swift export suite (
scripts/measure/export-settings-artifacts.shon the fleet) exited 0 on the layout commit. crash_ratchet.pyok.lint-ios-package-conventions.shok.check-concurrency.shreports one existing base hit inControlWorkspaceInfoCache.swift(cx-1ox9m). This PR does not touch that file.
Changelog
none
🤖 Generated with Claude Code
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the failing settings categories test by giving freeModel.enabled a home: an "AI Models" group in the Agents category, after Computer Use. The setting controls the free AI model agents use while signed out; no new strings or categories were added.
The settings schema export was regenerated on the merged head. The setting.sidebar.workspaceRow.notification default stays false to match base; the earlier autofix had regenerated it with the pre-#20483 value (true), so the fleet export was kept.