2 commits

Author	SHA1	Message	Date
Paladin173	d8f0f8f97f	Fix composer control reorder rebase collision ... Reapply footer control ordering on current upstream/master while preserving the required situational chip renderer. Persist composer_control_order with backend validation, keep the settings descriptions reorder-aware, and make primary/situational chip renderers participate in same-group drag ordering. Verified with: node --check static/boot.js; node --check static/panels.js; git diff --check; ./scripts/test.sh tests/test_issue4598_composer_control_visibility.py	2026-06-30 21:11:54 -05:00
nesquena-hermes	b549c004cb	stage #4598 (Paladin173): composer footer control visibility toggles + rebase + contract test (#4630) ... Per-control show/hide for composer footer controls (primary vs situational groups), per-profile persist + live-apply. Visibility-only — footer layout unchanged. nesquena-hermes deep-reviewed safe (Codex+Opus+suite 9930). Rebased onto master: resolved api/config.py boolean-keys conflict (kept both auth_disabled_acknowledged + the 15 hide_composer_* keys) and panels.js settings-load conflict (kept both render_user_markdown wiring + composer-control chip render). Contributor closed the en-only-i18n CI blocker (19 keys x 13 locales verified). Added the missing static- contract test (sibling pattern test_sidebar_tab_visibility.py). Co-authored-by: nesquena-hermes <agent@nesquena-hermes> Co-authored-by: Paladin173 <Paladin173@users.noreply.github.com>	2026-06-21 12:42:42 -07:00