refactor: use buttons and links components in account menu

[essenmitsosse]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 13, 2026 0:49am

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 13, 2026 0:49am
npmx-lunaria	Ignored		Feb 13, 2026 0:49am

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates icon references and refactors component usage across multiple Vue files. The Bluesky icon is changed from the simple-icons set to the carbon logo set in AppHeader.vue and CallToAction.vue. The Filter/Panel.vue component's radio button selection mechanism is refactored to use TagRadioButton components with v-model binding instead of manual button markup and click handlers. Multiple components (AccountMenu.client.vue, AuthModal.client.vue, ConnectorModal.vue) replace native HTML button and anchor elements with ButtonBase and LinkBase components, introducing a new classicon prop to ButtonBase for icon handling.

Possibly related PRs

• fix(ui): invalid html button markup #1274: Modifies AccountMenu.client.vue markup to replace native button elements with alternative component wrappers
• fix: connector modal legibility #863: Updates ConnectorModal.vue contributor link and button markup, overlapping with anchor-to-LinkBase and button refactoring changes
• feat: polish colors and indents #1042: Modifies the TagRadioButton component's focus styling, directly related to the TagRadioButton usage introduced in Filter/Panel.vue

Suggested reviewers

• danielroe
• alexdln

🚥 Pre-merge checks | ✅ 1 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description provided by the author, making it impossible to assess alignment between stated intent and actual changes.	Add a clear pull request description explaining the refactoring objectives, such as why ButtonBase and LinkBase components are being adopted and any expected benefits or migration notes.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ 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

---

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

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

app/components/Header/AccountMenu.client.vue (1)

86-86: Consider using colon syntax for UnoCSS icons.

The icon classes use dash-separated syntax (e.g., i-carbon-terminal, i-carbon-chevron-down). For performance optimisation with UnoCSS preset-icons, prefer the colon syntax (e.g., i-carbon:terminal, i-carbon:chevron-down). This helps UnoCSS resolve the collection directly.

Based on learnings: "In Vue components, use colon syntax for UnoCSS preset-icons (e.g., i-carbon:checkmark instead of i-carbon-checkmark)."

Also applies to: 104-104, 115-116, 164-164, 206-206, 232-237, 258-258

[essenmitsosse]

Sorry the Panel.vue part wasn't supposed to be in the PR. Reverted it.