Part of #14.
## Context
The title explicitly calls out **signatures**; none exist today.
## Scope
- [ ] Create / edit / delete signatures; a per-account default; persisted in settings or the DB.
- [ ] Rich (HTML) signature content, reusing the #36 editor.
- [ ] Auto-insert on new compose / reply / forward (configurable), with correct placement
relative to quoted text.
- [ ] Settings UI to manage signatures.
## Acceptance criteria
- A configured signature is inserted automatically per its rules and remains editable before
send.
- Per-account defaults are honored when composing from that account.
## Relevant files
- `data/settings/*` (or a new DB table), `domain/model/AccountSettings.kt`,
`ui/compose/ComposeViewModel.kt`, new signature settings screen
## Dependencies
Depends on #36 (editor) and #37 (send path).
Already delivered — the rich HTML signatures feature (SignatureEntity/DAO/SignatureRepository with per-account default + cascade cleanup, SignatureEditScreen reusing the #36 rich editor, auto-insert on new compose and on reply/forward above the quoted original gated by a per-account toggle, and the Signatures settings UI) is fully implemented, migrated (DB schema v10), and tested on main. Delivered by #47 (feature) + #7 (per-account enable toggle). Ticket was open only administratively; closing as completed.
Already delivered — the rich HTML signatures feature (SignatureEntity/DAO/SignatureRepository with per-account default + cascade cleanup, SignatureEditScreen reusing the #36 rich editor, auto-insert on new compose and on reply/forward above the quoted original gated by a per-account toggle, and the Signatures settings UI) is fully implemented, migrated (DB schema v10), and tested on main. Delivered by #47 (feature) + #7 (per-account enable toggle). Ticket was open only administratively; closing as completed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #14.
Context
The title explicitly calls out signatures; none exist today.
Scope
relative to quoted text.
Acceptance criteria
send.
Relevant files
data/settings/*(or a new DB table),domain/model/AccountSettings.kt,ui/compose/ComposeViewModel.kt, new signature settings screenDependencies
Depends on #36 (editor) and #37 (send path).
Already delivered — the rich HTML signatures feature (SignatureEntity/DAO/SignatureRepository with per-account default + cascade cleanup, SignatureEditScreen reusing the #36 rich editor, auto-insert on new compose and on reply/forward above the quoted original gated by a per-account toggle, and the Signatures settings UI) is fully implemented, migrated (DB schema v10), and tested on main. Delivered by #47 (feature) + #7 (per-account enable toggle). Ticket was open only administratively; closing as completed.