feat: [docs] Add issue triaging file explaining all labels used

[ShinichiShi]

Fixes #912

Describe the changes you have made in this PR -

This PR adds the issue-labels.md file which contains a brief description of all the labels that will be used in the cv-frontend-vue repo only. This includes labels such as status, type, platform, operating system, good first issue, time based labels and PR labels.

Screenshots of the UI changes (If any) -

---

Code Understanding and AI Usage

Did you use AI assistance (ChatGPT, Claude, Copilot, etc.) to write any part of this code?

• No, I wrote all the code myself
• Yes, I used AI assistance (continue below)

If you used AI assistance:

• I have reviewed every single line of the AI-generated code
• I can explain the purpose and logic of each function/component I added
• I have tested edge cases and understand how the code handles them
• I have modified the AI output to follow this project's coding standards and conventions

Explain your implementation approach:

This PR focuses mainly to make it easier for new contributors to pick up the issues. There's addition of platform specific labels and PR labels based on priority.

---

Checklist before requesting a review

• I have added proper PR title and linked to the issue
• I have performed a self-review of my code
• I can explain the purpose of every function, class, and logic block I added
• I understand why my changes work and have tested them thoroughly
• I have considered potential edge cases and how my code handles them
• If it is a core feature, I have added thorough tests
• My code follows the project's style guidelines and conventions

---

Note: Please check Allow edits from maintainers if you would like us to assist in the PR.

Summary by CodeRabbit

• Documentation
  • Added a comprehensive issue and pull request labeling guide covering Status, Type, Platform, Operating System, Contributor-Friendly, Time-Based, and PR review/priority labels with definitions.
  • Provides step-by-step application workflow and usage guidelines (triage steps, single-concern rule, reproducibility checks, handling duplicates and stale issues).
  • Standardizes labeling and review practices to improve triage consistency and contributor clarity.

[netlify]

✅ Deploy Preview for circuitverse ready!

Name	Link
🔨 Latest commit	02e611d
🔍 Latest deploy log	https://app.netlify.com/projects/circuitverse/deploys/698b35c097d3410008813dcd
😎 Deploy Preview	https://deploy-preview-915--circuitverse.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 43 (🔴 down 6 from production) Accessibility: 73 (no change from production) Best Practices: 92 (no change from production) SEO: 82 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

A new documentation file (issue-labels.md) was added describing the repository's issue and pull-request labeling taxonomy. It enumerates labels grouped as Status, Type, Platform, Operating System, Contributor-Friendly, Time-Based, and Pull Request labels, gives names and descriptions, and documents triage workflows including reproducibility checks, duplicate handling, single-concern requirements, and PR review/priority labels.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding documentation for issue labels used in the repository.
Linked Issues check	✅ Passed	The PR successfully addresses all coding requirements from issue #912: creates issue-labels.md file documenting status, type, platform, OS, contributor-friendly, time-based, and PR-specific labels with descriptions and usage guidance.
Out of Scope Changes check	✅ Passed	All changes are within scope; the PR adds the requested issue-labels.md documentation file and removes an Android label, both aligned with issue #912 objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@issue-labels.md`:
- Around line 14-15: Table rows in issue-labels.md violate markdownlint MD060 by
lacking spaces around the pipe delimiters; update each Markdown table header and
row (e.g., the "| Label | Description |" header and the corresponding rows at
the other mentioned ranges) to include a single space after each opening pipe
and before each closing pipe (so every cell is like " | Cell content | "), and
apply this consistent spacing fix to all listed table occurrences (lines 28-29,
44-45, 55-56, 67-68, 78-79, 90-91, 97-98) so the tables pass MD060.
- Line 34: Update the description for the `ui/ux` label so the compound
adjective is hyphenated: change "User interface or user experience related
issues." to "User interface- or user experience-related issues." so "related"
clearly modifies the compound phrases associated with the `ui/ux` label.

[ShinichiShi]

@tachyons Could you please review this

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@issue-labels.md`:
- Around line 59-60: Update the OS label row for consistency by capitalizing the
Android name in the description: locate the table row containing the labels
`macos` and `android` (the second cell currently reads "Issue specific to
android environments.") and change the description to "Issue specific to Android
environments." so it matches the capitalization style used for other OS names
like Windows, Linux, and macOS.

🧹 Nitpick comments (2)

issue-labels.md (2)

40-48: Consider adding web/browser platform label.

This is a Vue frontend repository (cv-frontend-vue), yet the platform labels only include tauri and desktop. Consider adding a web or browser label for web-specific issues, as this is likely a primary platform for the application.

📝 Suggested addition

 | Label     | Description                                          |
 | --------- | ---------------------------------------------------- |
 | `tauri`   | Issues related to the Tauri-based application layer. |
 | `desktop` | Desktop-specific functionality or behavior.          |
+| `web`     | Web browser-specific functionality or behavior.      |

---

93-93: Make label description tool-agnostic.

The review-ready description specifically mentions "CodeRabbit" which couples this documentation to a specific tool. Label descriptions should be tool-agnostic to remain relevant regardless of which tools are used.

📝 Proposed fix

-| `review-ready` | Pull request is ready for review. This is added only after all the threads mentioned by CodeRabbit and reviewers have been addressed. |
+| `review-ready` | Pull request is ready for review. This is added only after all review comments and threads have been addressed. |

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix OS name capitalization for consistency.

The operating system names should be consistently capitalized:

• Line 59: "macOS" is correct in the description, matching Apple's official capitalization
• Line 60: "android" should be capitalized as "Android" to match the capitalization of other OS names (Windows, Linux, macOS)

As per static analysis hints, the macOS capitalization is already correct.

📝 Proposed fix

-| `android` | Issue specific to android environments. |
+| `android` | Issue specific to Android environments. |

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	| `macos` | Issue specific to macOS environments. |
	| `android` | Issue specific to android environments. |
	| `macos` | Issue specific to macOS environments. |
	| `android` | Issue specific to Android environments. |

🧰 Tools

🪛 LanguageTool

[uncategorized] ~59-~59: The operating system from Apple is written “macOS”.
Context: ...e specific to Linux environments. | | macos | Issue specific to macOS environmen...

(MAC_OS)

🤖 Prompt for AI Agents

In `@issue-labels.md` around lines 59 - 60, Update the OS label row for
consistency by capitalizing the Android name in the description: locate the
table row containing the labels `macos` and `android` (the second cell currently
reads "Issue specific to android environments.") and change the description to
"Issue specific to Android environments." so it matches the capitalization style
used for other OS names like Windows, Linux, and macOS.