Records the 2026-09-30 afternoon fix round in the redesign proposal (new section 9) and fills the task card with scope, root causes, and conventions:
Render order = storage order: parts may only be grouped for display when grouping preserves original order (consecutive process blocks).
@ui shells mounted on host generic classes (.modal) must scope their layout with compound selectors so host styles loaded later cannot override them at equal specificity.
Also captures the full verification record (vitest/go suites, 12/12 headless run) and the non-goals (docx online preview, fs-style workspace tools).
## What
Records the 2026-09-30 afternoon fix round in the redesign proposal (new section 9) and fills the task card with scope, root causes, and conventions:
- Render order = storage order: parts may only be grouped for display when grouping preserves original order (consecutive process blocks).
- @ui shells mounted on host generic classes (`.modal`) must scope their layout with compound selectors so host styles loaded later cannot override them at equal specificity.
Also captures the full verification record (vitest/go suites, 12/12 headless run) and the non-goals (docx online preview, fs-style workspace tools).
Task card: feature/chat-order-artifact-files (Agent-System-Dev).
Why: the delivery log for the 2026-09-30 afternoon fixes (part-order
fidelity, download channel, artifact file management, settings cascade)
belongs with the redesign proposal it extends, including the two durable
conventions it produced.
Evidence: adds section 9 with root causes, the render-order-equals-
storage-order rule, the compound-selector lesson for @ui shells on host
generic classes, and the full verification record (vitest/go suites plus
the 12/12 headless run).
Impact: future UI work inherits both conventions without rediscovering
the failure modes.
Refs: task feature/chat-order-artifact-files.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Records the 2026-09-30 afternoon fix round in the redesign proposal (new section 9) and fills the task card with scope, root causes, and conventions:
.modal) must scope their layout with compound selectors so host styles loaded later cannot override them at equal specificity.Also captures the full verification record (vitest/go suites, 12/12 headless run) and the non-goals (docx online preview, fs-style workspace tools).
Task card: feature/chat-order-artifact-files (Agent-System-Dev).
c3c05678e9to8e2657c824