mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-11-07 14:38:23 -10:00
b82e02fa37
* feat(web-shell): support host settings item exclusions * test(web-shell): capture settings panel with host exclusions in visuals The visual preview flagged that no scenario renders the settings panel, leaving the host exclusion feature invisible to the before/after preview. Add a settings harness page that maps ?exclude= onto the host-only settings prop (the standalone entry never passes it) and two scenarios: the default panel and the panel with representative exclusions, gated on row/category assertions so a filtering regression fails loudly. Co-authored-by: Qwen-Coder <[email protected]> * fix(web-shell): scope settings-exclusion dialog closes to the owning item The exclusion force-close effect ran blanket resets on every dialog state, so a stale settings key closed pickers later opened from a command or the status bar, and the /model branch-head reset erased the key on sub-paths that open no dialog, disarming exclusion for a dialog that was still open. Close only the dialog the held key owns, clear the key only where /model takes over a dialog surface, share one builtin-id predicate, and drop the duplicated empty-state description. Pin each behavior with mutation-probed tests. * fix(web-shell): cover live settings exclusions and host forwarding * fix(web-shell): close settings-exclusion gaps from review (#11975) - add the missing setting:omni alias for omni.enabled, plus a cli-side drift test comparing the live served settings set against the published alias table in both directions - pin the App -> SettingsMessage presentation handoff - scope command-takeover clears to the surface each command owns; drop the bare-/model and --voice clears that could only disarm a settings-launched surface - pin the close-ladder arms, builtin item ids, nav badge/scoping, card gate, and user-scope exclusion with falsifiable tests - stop inventing the Model category during the initial settings load - promote the README section to a top-level Chinese section with prop rows, and make the visual harness theme assertion falsifiable * fix(web-shell): drop duplicate omni settings alias (#11975) The merge of the two parallel fix branches kept both 'setting:omni-media-delivery' (maintainer's) and 'setting:omni' (bot's) as public aliases for omni.enabled. Keep the maintainer-chosen descriptive alias and remove the redundant one before the new alias API ships; repoint the omni witness test at the surviving alias. * test(web-shell): close settings-exclusion test gaps from review (#11975) Address the remaining review findings on the settings presentation exclusions PR: - Pin the scoped /auth takeover against over-clearing: a settings-launched fast picker (held key 'fastModel') must still close when its alias is excluded after /auth ran, and must stay open across /auth without an exclusion. The existing auth fixture held exactly the key /auth clears, so scoped and blanket clears were indistinguishable. - Make the served/rendered alias drift test reject two stable IDs mapping to one configuration key; the membership checks alone cannot see a duplicate, and a published duplicate cannot be withdrawn. - Move gotoSettingsHarness into the visuals harness next to the other navigation helpers and add it to the freeze-before-navigate contract. - Gate openSettingsPanel on a descriptor-derived nav button instead of a row, so reordering the fixture's first General descriptor cannot race the settings fetch. - File the showTimestamps fixture row under General (matching the real schema) instead of an invented Output category, and make the chat-width absence assertion select the UI category first so it is no longer vacuous. * test(web-shell): pin partially excluded category in settings visuals (#11975) The host-exclusions capture pinned whole-category dropout (Tools) and a builtin partial exclusion (builtin:chat-width in UI), but not a partial exclusion of a descriptor row: with output.showTimestamps filed under General in the real schema, excluding setting:timestamps must remove only that row while the category and its surviving rows stay. The two added assertions also restore the spec's declared assertion surface after the previous commit moved gotoSettingsHarness (and its two assertions) into the shared visuals harness, which the deterministic gate measured as a net loss of two assertions. --------- Co-authored-by: 铃蓝 <[email protected]> Co-authored-by: qwen-code-ci-bot <[email protected]> Co-authored-by: Qwen-Coder <[email protected]> Co-authored-by: qwen-code-dev-bot <[email protected]> Co-authored-by: Qwen Code Bot <[email protected]> Co-authored-by: qwen-code-dev-bot <[email protected]>