<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
This PR adds support for `<dl>`, `<dt>`, and `<dd>` HTML tags in
messages.
<img width="417" height="208" alt="Rendered message containing a
description list."
src="https://github.com/user-attachments/assets/da6cfeb9-00a3-44ac-989d-37014f640fb7"
/>
As with the tables PR, this PR does not add support for editing the
description list.
> [!Warning]
>
> The Matrix spec seems to recommend not supporting description lists:
https://spec.matrix.org/v1.19/client-server-api/#mroommessage-msgtypes
>
> I don't see any risk or harm in implementing them anyway, as they have
no way of being a vector for cyberattacks. (Should a MSC be submitted to
add them?)
Fixes#2050.
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
- [x] Created without the usage of AI
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!--
Write any explanation required here, but do not generate the explanation
using AI!! You MUST prove you understand what the code in this PR does.
You MUST explain what modifications you have made in order to ensure
that the result is compatible with THE LICENSE
By deleting this section or comment, in code or in body, the PR should
be rejected and closed.
-->
The embedded call widget publishes its MatrixRTC membership as a sticky
event, which ClientWidgetApi refuses without
org.matrix.msc4407.send.sticky_event. The MembershipManager then shut
down and the call dropped.
Grant the send and receive capabilities and implement sendStickyEvent,
sendDelayedStickyEvent and readStickyEvents on CallWidgetDriver.
Also register an MSC4480 sticky_events extension on sliding sync, since
matrix-js-sdk only reads sticky events out of /sync v2.
### Description
This pull request introduces and documents a clear policy restricting
the use of autonomous AI agents in this repository. It adds a new
`AGENTS.md` file with detailed guidelines, updates the contribution
documentation, and adds supporting policy files and editor settings to
ensure compliance and clarity for all contributors.
#### Type of change
docs change?
### Checklist:
- [x] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
no ai :3, but copied content from [linux's ai
guidelines](https://github.com/torvalds/linux/blob/master/Documentation/process/coding-assistants.rst)
Signed-off-by: Rye <[email protected]>
### Description
By default, Sable only shows a timestamp on the first message in a group
of consecutive messages from the same sender. This adds a
`showAllTimestamps` setting (default: off) that renders a timestamp on
every message, even grouped/collapsed ones. The toggle is in Settings →
General → Messages, below "Message Spacing".
When enabled, collapsed messages render a right-aligned timestamp in
place of the empty header, without the username, avatar, or pronouns
that appear on ungrouped messages. The layout direction respects the
same Row/RowReverse logic as the full header (compact and right-aligned
bubble layouts).
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
### AI disclosure:
- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
The implementation was AI-assisted: adding the `showAllTimestamps`
boolean to the `Settings` interface and defaults, reading it via
`useSetting` in `Message.tsx` and conditionally rendering a
timestamp-only header for collapsed messages, and adding the
`SettingToggle` in `General.tsx`. I reviewed each change, verified the
collapsed header layout matches the existing direction logic, and ran
typecheck, lint, format, and tests in a containerized environment.
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
Update
[MSC4461](https://github.com/matrix-org/matrix-spec-proposals/pull/4461)
support from v2 to v3. Also adds support for the keep_trigger option
when sending messages (not yet in settings)
See #1279
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [X] My code follows the style guidelines of this project
- [X] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [X] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fixes #
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->