fix: Fix test name mismatch in isResolveThreadCommand

[continue-staging]

Summary

Fixes a test name mismatch issue where the test name contradicted its assertion in the isResolveThreadCommand utility function.

Changes

• Fixed the implementation: Updated the regex pattern to use word boundaries (\b) to properly distinguish between resolveReviewThread and unresolveReviewThread
• Fixed the test: Updated the test assertion to expect false for unresolveReviewThread, which now matches the test name "should not match unresolveReviewThread"
• Updated comments: Clarified that the function now correctly excludes unresolveReviewThread due to word boundary matching

Issue Addressed

The original issue was that the test was named "should not match unresolveReviewThread" but was asserting toBe(true), creating confusion about the intended behavior. The implementation was also using simple substring matching which incorrectly matched unresolveReviewThread because it contains resolveReviewThread.

Testing

• All existing tests continue to pass
• The specific test now correctly validates that unresolveReviewThread returns false
• The function still correctly matches resolveReviewThread commands

---

This task was co-authored by nate and Continue.

---

Summary by cubic

Fix resolve thread command detection to avoid matching unresolveReviewThread and align the test with its name. This prevents false positives when parsing gh api graphql commands.

• Bug Fixes
  • Use word boundaries in the regex to match resolveReviewThread only.
  • Update test to expect false for unresolveReviewThread; resolveReviewThread still matches.

^{Written for commit 199d451. Summary will update on new commits.}

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[continue-staging]

I have read the CLA Document and I hereby sign the CLA

[cubic-dev-ai]

No issues found across 4 files