docs/plans/2026-04-08-suggestion-mention-backspace.md
packages/suggestion/src/lib/withSuggestion.spec.tsx.deleteBackward('character') on a previous mention-shaped inline void.deleteSuggestion.packages/suggestion.withSuggestion tests cover text and block suggestions, but not inline void mentions.suggestion: true.deleteSuggestion exits early when editor.api.string(range) is empty before reaching setSuggestionNodes(...).deleteSuggestion still treated mention deletion like a character loop instead of an inline-void unit.[0,0]:0 instead of the mention's left edge at [0,0]:1.block-discussion-index.ts only folded Text nodes and block suggestions into summary text, so inline void suggestions like mention/date/inline equation disappeared from Delete: cards.dates like or use inline equations: .findSuggestionProps only looked for adjacent text suggestions, not adjacent inline suggestion elements.remove suggestion instead of creating a remove line-break suggestion.packages/suggestion/src/lib/withSuggestion.spec.tsx.bun test packages/suggestion/src/lib/withSuggestion.spec.tsx.pnpm install, pnpm turbo build --filter=./packages/suggestion, pnpm turbo typecheck --filter=./packages/suggestion, and pnpm lint:fix.[0,0]:1.editor.api.before(pointNext) instead of continuing the character loop.apps/www/src/registry/ui/block-discussion-index.spec.tsx with JSX-like Slate fixtures covering remove summaries for date, inline_equation, and mention.value, formatted date, and texExpression.findSuggestionProps regression proving backward deletion from the left edge of an inline void must reuse that void's remove-suggestion metadata.findSuggestionProps inspect adjacent inline suggestion elements when adjacent text suggestions are absent.withSuggestion regression for deleteBackward at the start of a paragraph, asserting it creates a remove line-break suggestion and preserves the next paragraph.isLineBreak: true for remove suggestions, aligning it with the existing accept/reject merge semantics.