[Enhancement] Visually differentiate Issues vs PRs in Similarity Search results

[Kavirubc]

Problem Statement

With the recent changes in PR #48 (and related issues #46, #47), Simili-Bot now indexes both Issues and Pull Requests. However, the 'Similar Threads' output table does not visually distinguish between them.

Currently, it looks like:

| Similarity | Thread | Status |
| :--- | :--- | :--- |
| 95% | [#123 Fix login bug](...) | Open |
| 82% | [#124 Refactor auth](...) | Closed |

Users cannot tell if #124 is a PR or an Issue without clicking.

Proposed Solution

1. Update Pipeline Model: Add Type string field to SimilarIssue struct in internal/core/pipeline/pipeline.go.
2. Update Similarity Step: In internal/steps/similarity.go, extract the type field from the Qdrant payload (added in PR feat: CLI PR indexing (#46) & standardized embedding content (#47) #48) and populate the struct.
3. Update Response Builder: In internal/steps/response_builder.go, prepend an icon or label to the thread link.
   • e.g., [PR] #124 ... or using icons 📝 (Vote/Issue) vs 🔀 (PR).

References

• PR feat: CLI PR indexing (#46) & standardized embedding content (#47) #48: Implemented PR indexing and type payload field.
• Issue [Feature]: Support indexing Pull Requests in CLI index command #46: CLI Support for PR Indexing.
• Issue [Feature]: Standardize indexing content to include comments for both Issues and PRs #47: Standardized Indexing Content.

Feature Scope

• Pipeline Steps
• Response Builder