[Bug]: Studio preview composer differs from Windows Codex runtime

[2003Tim]

Platform / 平台

Windows

OS version / 系统版本

Windows 11

CPU / 架构

Windows x64

Codex Desktop version / source / Codex 桌面版版本或来源

Codex Desktop 26.803, official download

Dream Skin version / 皮肤工具版本

1.5.14

Problem category / 问题类型

Layout broken / white screen / 布局异常或白屏

Self-check / 自检

• Ran Verify / doctor (or Windows verify script) / 已运行 Verify 或 doctor
• Tried Restore, then re-apply / 已尝试完全恢复后再应用
• Official Codex still opens without the skin tools / 不用皮肤工具时官方 Codex 仍可正常打开
• Searched existing issues / 已搜索现有 Issue

Steps to reproduce / 复现步骤

1. On Windows, import and apply the attached blue-archive-arona-1.0.0.zip , theme-link
2. Open DreamSkin Studio and inspect the Composer preview. It correctly shows a light-blue translucent glass surface.
3. In the official Codex Desktop app (26.803), switch Appearance to Dark, then open both Home and a Thread.
4. Switch Appearance to Light and repeat on Home and a Thread.
5. Compare the real Composer with the Studio preview.

The theme uses valid Safe CSS:

[data-ds-part="composer"] {
  background-color: rgba(244, 250, 255, 0.10);
  border-color: rgba(255, 255, 255, 0.28);
  border-width: 1px;
  border-style: solid;
  border-radius: 24px;
  box-shadow: 0 8px 22px rgba(25, 57, 83, 0.07);
  backdrop-filter: blur(8px) saturate(1.06) brightness(1.02);
}

### Expected behavior / 期望结果

The Studio Safe CSS preview and real Codex runtime should use the same Skin API contract for `[data-ds-part="composer"]`.

The Composer should remain a light-blue translucent glass surface in both Dark and Light Codex appearance modes:

- the wallpaper remains visible through the surface;
- the specified blur, light border, radius, and shadow are applied;
- theme authors do not need to add `!important`;
- Home and Thread should behave consistently.

### Actual behavior / 实际结果

The theme renders correctly in DreamSkin Studio, but differs in real Windows Codex:

- Dark appearance: the Composer becomes a solid dark gray/black native-looking panel.
- Light appearance: the Composer becomes a pink-white native-looking panel.
- The result follows Codex appearance tokens instead of the valid Community Safe CSS visual design.
- This happens on both Home and Thread.

The theme ZIP is valid; this appears to be a DreamSkin runtime / Skin API compatibility and CSS cascade issue, not a theme CSS issue.

### Modified official Codex install? / 是否改过官方 Codex 安装？

No — official app only / 否，仅官方安装

### Logs / Verify / doctor output（recommended）/ 日志与校验输出（强烈建议）

Investigation findings:

- Codex 26.803 no longer exposes `.composer-surface-chrome` as the real Composer surface.
- The visible Composer surface is `_ComposerLayoutRoot_*`; Home additionally has an internal `_ComposerLayoutBody_*` native surface.
- The native appearance values observed on the real renderer include:
  - Light: `--color-background-control: rgba(255,246,251,.96)`
  - Dark: `--color-background-control: rgba(45,45,45,.96)`
- These native surfaces explain the pink-white and dark-gray Composer results.
- DreamSkin runtime rules using `background` / `border: 0 !important` can conflict with Community Safe CSS longhands such as `background-color`, `border-color`, `border-width`, and `border-style`.
- Increasing selector specificity alone does not reliably fix the CSS-layer `!important` ordering issue.

Existing open and closed issues were searched. The closest issues discuss Composer layout or visual regression coverage, but none tracks this Studio-preview versus real-runtime Composer Safe CSS contract mismatch.

### Screenshots / video / 截图或录屏

<img width="2478" height="1440" alt="Image" src="https://github.com/user-attachments/assets/510a9c76-193d-4f41-8891-69880072c4a7" />
安装主题后日间模式首页
<img width="2478" height="1440" alt="Image" src="https://github.com/user-attachments/assets/2c36d358-4503-4fc7-8e52-d8dd4bf021b6" />
安装主题后夜间模式设置页面

<img width="2478" height="1440" alt="Image" src="https://github.com/user-attachments/assets/49b59fdd-6014-4a58-ad6f-3333de25f956" />
夜间模式设置界面

<img width="2478" height="1440" alt="Image" src="https://github.com/user-attachments/assets/e85f2c4f-c886-46f3-88fb-a0cffcd8298e" />
夜间模式首页

<img width="2393" height="1316" alt="Image" src="https://github.com/user-attachments/assets/04ba5c50-6ea1-4cba-9e1e-d76c2e8aee19" />
网页端预览首页

<img width="2393" height="1316" alt="Image" src="https://github.com/user-attachments/assets/d62ea8bc-6dcf-4210-a8d7-8534f792ceb0" />
网页端预览对话界面

### Extra context / 其他信息

This is not a request to modify Codex binaries, `app.asar`, API keys, or model settings.

Please fix the DreamSkin runtime / Skin API contract rather than requiring theme authors to change `appearance` or add unsupported `!important` declarations.

Suggested direction:

1. Bind `data-ds-part="composer"` to the stable visual Composer Root rather than an internal Footer.
2. Keep the Home internal native Composer body transparent when the public Composer Root owns the visual surface.
3. Preserve Safe CSS validation restrictions.
4. Define a controlled cascade bridge for Safe CSS properties that the public Composer API explicitly allows.
5. Add shared Windows/macOS regressions for dark/light, Home/Thread, no Community Composer CSS, and Composer DOM replacement.

The same `blue-archive-arona-1.0.0.zip` should work without a theme-specific workaround.

### Confirmation / 确认

- [x] I did not paste API keys or secrets / 我未粘贴 API Key 或其它密钥
- [x] I understand this is an unofficial theme tool (loopback CDP only) / 我理解这是非官方换肤工具（仅本机 CDP）

[Fei-Away]

已处理：报告中的 Composer/Studio 视觉契约修复已随客户端公开版本 发布（tag ，提交 ）。实现使用稳定的 作为公共 Composer 视觉根，并加入受控 Safe CSS bridge，同时覆盖 Home/Thread 的相关 surface；没有把旧的 Body 内部选择器当作公共根。v1.5.15 的 Windows CI（含安装包）通过，macOS 本机 live verify/doctor 也通过。请用 v1.5.15 重测；原报告针对的是 1.5.14，因此关闭为已发布修复。

[Fei-Away]

补充完整记录：报告中的 Composer/Studio 视觉契约修复已随客户端公开版本 v1.5.15 发布（tag v1.5.15，提交 b44e729）。实现使用稳定的 ComposerLayoutRoot 作为公共 Composer 视觉根，并加入受控 Safe CSS bridge，同时覆盖 Home/Thread 的相关 surface；没有把旧的 Body 内部选择器当作公共根。v1.5.15 的 Windows CI（含安装包）通过，macOS 本机 live verify/doctor 也通过。请用 v1.5.15 重测；原报告针对的是 1.5.14，因此关闭为已发布修复。