Why
Editing an issue or change request title and description leaves the page for a separate form, while editing a comment happens in place. A correction to a typo or a clearer explanation is a small edit, so it should not cost a navigation and should keep the discussion, sidebar, and any other open state where it was. The prefilled text areas also open at a fixed small height, so the text a reader is correcting is mostly below the fold inside the field.
Scope
- Put the title and description into an edit mode on the issue and change pages.
- Keep the existing
/editpage as the no-JavaScript fallback. - Use the existing HTMX write path, so a saved or refused edit replaces only the affected regions and keeps what the reader typed when the write is refused.
- Size prefilled edit text areas to their content on opening and after a swap, while leaving them vertically resizable.
- Apply the same sizing to the comment edit field, which already edits in place.
Acceptance criteria
- Edit on an issue or change swaps its title to a text input and its description to a text area without navigating.
- Save replaces the title and description with the new values in place; the discussion and sidebar are not re-rendered.
- Cancel closes the in-place editor and the page still shows the previous text.
- A refused edit (for example, a blank title) keeps the form open with the typed values and the reason.
- The
/editpage still works without JavaScript. - Prefilled edit text areas open at approximately the height of their content and can still be resized vertically.
- Tests cover the inline response for both an issue and a change, and the relevant Go and workflow checks pass.