fix(ui): keep the process disclosure inside the reading measure

[Astro-Han]

Summary

The process disclosure's ::details-content animation grid had an implicit auto column track, which grows to the item's max-content: one unbreakable descendant inside .maka-processing-body (a long code line, an ellipsized command) widened the body past the 800px reading measure while the details' contain: paint boundary clipped every sibling at the column edge — the uniform mid-column text clipping seen in the release transcript. Reproduced live: injecting a wide child took the body from 800 to 2157px; pinning the column to minmax(0, 1fr) restores 800. Second defect on the same seam: the body's overflow: clip cut the Astryx tool rows' intentional 4px inline overhang (their padding/negative-margin pair lets hover surfaces reach the card edge; upstream absorbs it at every clip boundary — this one did not).

Fix, all inside the existing seam: pin the grid's column track, give the sequence the 4px inline padding where that overhang lands inside its paint boundary, and narrow the body's clip to the block axis (the only axis the wipe animation needs). The stale ProcessingBlock comment — still describing the scrollable capped card removed in #5518 — now describes the actual disclosure. Same PR also drops the dead declarations the audit proved removable: .maka-chat-layout duplicated the upstream ChatLayout root, position:relative on .maka-chat-shell/.maka-chatContent has no containing-block consumer, three width:100%/opacity:1 declarations are stretch-redundant or leftovers, and .agents-chat-view-root duplicated .agents-chat-panel byte for byte.

Verification

• npm run smoke:storybook — 384 stories / 416 theme renders pass, including CompletedProcessExpanded with the new assertions (every body child must stay within the details' own box).
• Defect detection proven by targeted mutation on the built bundle: removing the grid-template-columns pin from the live rule makes the body measure 941 > 800 — the assertion fails as intended.
• Live CSSOM ablation on main before cutting: removing the deleted declarations produced byte-identical geometry at every joint, including the prompt rail's sticky position under scroll.
• npm run format, npm run lint, npm --workspace @maka/desktop run typecheck:stories — clean.

completed-process-expanded, 1200px — left BEFORE (main build), right AFTER (branch). Body content insets 4px where the row overhang lands; the long Bash command ellipsizes inside the column instead of pushing siblings off it.

AI use

• Generative tooling made a substantive contribution

Tool(s) and scope: Devin — audit probes, diagnosis, implementation and verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above

[jackwener]

I reviewed ef76ad7ad5f3a2ec8c167b670d3e3017ba4e53d6.

No P0–P2.

An implicit auto column on ::details-content will grow to max-content; grid-template-columns: minmax(0, 1fr) pins that track to the reading measure. Sequence padding-inline: 4px is where the tool-row overhang lands; the body clips only on the block axis for the wipe. The CompletedProcessExpanded story now fails if a long child widens the body past the details box. I did not independently re-run the CSSOM ablation of the deleted column declarations.

Required check test is green on this head.

简体中文

我审查了 ef76ad7ad5f3a2ec8c167b670d3e3017ba4e53d6。没有 P0–P2。

::details-content 的隐式 auto 列会跟着 max-content 撑开，minmax(0, 1fr) 把列钉在阅读宽度上。工具行 4px 外伸落在 sequence 的 padding 里。故事会在长子项撑破 details 时失败。删掉的列声明我没有自己做 CSSOM 消融。本 head 上 test 绿。

---

Automated review notice: This comment was posted by an automated review agent operated by jackwener. It is not an independent human review and does not replace one.