Improve /status quick action accuracy and quote handling

Problem Description

The /status quick action has inconsistent text parsing behavior that causes commands to fail unexpectedly, while also providing misleading preview text that doesn't accurately reflect whether the command will succeed or fail.

Current Behavior

  • /status in dev → Shows preview "Set status to in dev" → Works correctly
  • /status "in dev" → Shows preview "Set status to "in dev"" → Fails with error

Both commands show similar preview text, but only the first one actually works. The core issue is that the command parser doesn't properly handle quoted text, leading to both execution failures and misleading previews.

Expected Behavior

  1. Robust Text Parsing: The system should handle various input formats consistently:

    • Unquoted text: /status in dev
    • Quoted text: /status "in dev" (should work by stripping quotes)
    • Mixed content with special characters and emojis

  2. Accurate Preview Text: The preview should only show success messages when the command will actually succeed after proper text parsing

  3. Special Character Support: The system should properly parse and handle status names containing:

    • Emojis (e.g., /status "🚀 in dev", /status ✅ ready)
    • Special characters and symbols
    • Unicode characters
    • Spaces and punctuation
    • Mixed content (text + emojis + special chars)

Technical Considerations

  • Implement quote stripping logic similar to label quick actions
  • Handle edge case where status names legitimately contain quotes (e.g., "tooo" as shown in testing)
  • Ensure proper Unicode handling for emojis and special characters in both parsing and matching
  • Potential solution: If exact match with quotes fails, strip quotes and retry matching
  • Update both the command execution logic AND preview generation to use the same parsing rules

Related Issues

Edited by Marc Saleiko