{
  "context": "Evaluates how the solution uses @ckeditor/ckeditor5-mention to keep mention data consistent. Focuses on configuring feeds, relying on Mention post-fixers, and using the mention command to enforce cleanup and attribute propagation instead of manual string handling.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Mention setup",
      "description": "Initializes the editor with the Mention plugin (MentionEditing + MentionUI) from @ckeditor/ckeditor5-mention so the built-in mention attribute and post-fixers are active, and exposes the registered 'mention' command for insertion.",
      "max_score": 20
    },
    {
      "name": "Feed config",
      "description": "Defines config.mention.feeds with the @ marker and feed items (including optional text overrides) so mentions carry the correct id/_text payload produced by toMentionAttribute during insertion.",
      "max_score": 15
    },
    {
      "name": "Post-fixer cleanup",
      "description": "Relies on MentionEditing post-fixers to drop partial or broken mentions when the trigger is removed or the mention is split, avoiding stale mention attributes instead of manual DOM/text scrubbing.",
      "max_score": 25
    },
    {
      "name": "Attribute propagation",
      "description": "Keeps formatting consistent across mentions by letting mention post-fixers (_addMentionAttributes/_toMentionAttribute) propagate selection attribute changes across the entire mention when styling part of it.",
      "max_score": 20
    },
    {
      "name": "Selection guard",
      "description": "Ensures typing next to a mention does not inherit the mention attribute by relying on the built-in selection post-fixer and MentionCommand behavior that strips mention metadata from adjacent text insertion.",
      "max_score": 20
    }
  ]
}