Why: the user asked for a reviewable plan covering (a) previews for
office/image/markdown/code files and web links, docked in the right rail
or the system overlay, (b) keeping artifact deletion as a capability with
no UI entry, and (c) implementing fs tools without enabling them.
Evidence: the proposal assesses each idea against current architecture,
defines the FilePreview capability component with a format matrix and
lazy-loaded office parsers, the SSRF-guarded url-preview endpoint, the
gated sandboxed fs tool family, four delivery phases with acceptance
criteria, and decision points D1-D5 for the user.
Impact: documentation only; implementation follows in a separate task
after D1-D5 are settled.
Refs: task feature/file-preview-proposal; extends 2026-09-30
ui-redesign-and-auth.md section 9.
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.