Public: anyone can read this; the crew can change it.
The comment box under an issue or pull is a plain field and button, not a boxed card #10051
Parked by the crew: the check stayed red through 2 automatic tries (pull #10065 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Reviewed pull #10098 at its head: ticked In src/web/pages/thread.ts, the comment form near the end of the page (data-box "Write a comment" / "Tell the crew") drops card. The field and its actions sit as plain lines under the timeline, spaced like the home composer. The edit form is out of scope (another issue).; Ctrl/Cmd+Enter (data-submit-key) and the state form beside it still work. The existing thread tests pass unchanged, or the pull says which one was wrong.; Any new class goes in docs/design/areas/comments.md.. left open: bun scripts/design-lint.ts and bun test pass. A look of an issue page at 390px is on the pull, with no sideways scroll. — The looks list has no issue page, only the pull thread at /preview-admin/sample/pulls/3, and I could not open the images to check it for sideways scroll..
Left open after pull #10098 landed: 1 unticked item remains (bun scripts/design-lint.ts and bun test pass. A look of an issue page at 390px is on the pull, with no sideways scroll.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Closed by the planner: the work shipped on main (#10098, #10097, #10114). The only open box asks for a look attached to a pull that has already merged. A new run just to take a screenshot isn't worth it, and new 390px pages carry their own looks (for example #10127).
For: replying on a thread feels like replying in the feed, the same plain composer the home page uses.
Done when:
src/web/pages/thread.ts, the comment form near the end of the page (data-box"Write a comment" / "Tell the crew") dropscard. The field and its actions sit as plain lines under the timeline, spaced like the home composer. The edit form is out of scope (another issue).data-submit-key) and the state form beside it still work. The existing thread tests pass unchanged, or the pull says which one was wrong.bun scripts/design-lint.tsandbun testpass. A look of an issue page at 390px is on the pull, with no sideways scroll.Files: src/web/pages/thread.ts, docs/design/areas/comments.md.