#### Background
Through our user research we've learned how critical communication is with reverts. To improve communication when reverts to other people's edits are made, our team can improve the diff view. One way of making this improvement is encouraging users to leave a detailed, but respectful summary of the edit they've made (including reverts). This is aligned with Wiki policy.
#### User stories
**Our current summary experience can be improved to achieve the following user stories:**
- When my edit has been reverted, I want a clear distinction between the edit summary and the diff itself, so that I can process information more efficiently.
- When editing Wikipedia, I want the interface to give me clear direction for crafting helpful summaries in line with Wiki policies, so that patrollers and other users understand why I made the change that I did to an article.
- When accessing the Watchlist, I want to review a diff and clearly understand why an edit was made, so that I have the proper context to agree or dispute the change.
#### The Task
- [ ] If someone selects other, provide some guidance from [[ https://en.wikipedia.org/wiki/Help:Edit_summary | the edit summary policy ]] and the [[ https://en.wikipedia.org/wiki/Wikipedia:Reverting#Explain_reverts | reverting guidance ]]
- [ ] Do not allow people to publish without an edit summary
- [ ] Create parity for watchlist view and revision history view, to clearly call out when the edit summary is blank
#### Designs
##### 1. Edit summary flow
| 1) Scrolls to section {F35465976} | 2) Taps edit {F35461738} | 3) Makes edit {F35461736} | 4) Previews edit {F35461742} | 5) Summarizes edit {F35461928} | 6) Writes summary {F35461744} | 7) Success screen {F35461978} | 8) Chip is stored {F35466020}
###### Annotations
**4) Previews edit:** Preview is now separated from the preview (per @Moshtagh.maveddat’s excellent suggestion). It also includes the legal disclaimer as a sticky (`position: fixed`) element at the bottom of the screen.
**5) Summarizes edit:**
- Keyboard is active when users arrive on this screen to reduce steps.
- `PUBLISH` button can be tapped at any time but is de-emphasized to encourage publishing with a summary.
- Links
- `This is a minor edit` info button/icon link: https://en.wikipedia.org/wiki/Help:Minor_edit
- `Watch this page` info button/icon link: https://en.wikipedia.org/wiki/Help:Watchlist
- `Learn more about edit summaries` link: https://en.wikipedia.org/wiki/Help:Edit_summary
- [[ https://material.io/components/chips | Chips ]] prefill the input field with plain text. Tapping a chip always clears the input field first.
- If a user
**6) Writes summary:** `PUBLISH` button turns into `colorAccent` once the input field is populated with text.
**8) Chip is stored:**
- This feature exists already and might help users prepopulate the field if tasks are done repeatedly. We will keep it to respect existing user flows.
- After publishing an edit summary with custom text, the contents of the custom text (e.g., “Formatting") are saved as a chip below the input field.
- Chips appear in a horizontally scrollable list, per [Material](https://material.io/components/chips#input-chips)’s definition.
- Chips with custom text can be removed by tapping the “remove” icon
##### 2. Optimize the `Watchlist` screen
Please add `Empty edit summary` copy/info from Revision history to the Watchlist for consistency:
| Revision history | Watchlist
| {F35455744} | {F35462007}