[P3] Audit: Feature request voting is missing

[baixiangcpp]

Imported from the byteflow.tools deep audit on 2026-06-22.

Problem: the project has many possible next tools and UX improvements, but there is no visible way for users to vote on requests. This makes roadmap prioritization harder and reduces community involvement.

Affected areas:

• Contact page
• GitHub Issues
• Roadmap documentation
• Tool request flow

Reproduction steps:

1. Open Contact and GitHub issue pages.
2. Look for a tool request or feature voting flow.
3. Check whether users can upvote existing ideas.
4. Check whether requests are grouped by category or roadmap stage.

Expected behavior: users should be able to request tools, vote on ideas, and see what is planned.

Actual behavior: feedback exists through GitHub, but structured voting is not visible.

Impact: roadmap decisions rely on less structured feedback and may miss high-demand features.

Proposed fix:

• Add issue templates for tool requests and UX requests.
• Create a public roadmap or discussion board.
• Use reactions or labels to track demand.
• Link request flow from All Tools, empty search results, and Contact page.

Acceptance criteria:

• Users can submit a structured tool request.
• Existing requests can be voted on or reacted to.
• Roadmap status is visible.
• Empty search results offer a request CTA.

[baixiangcpp]

Closed as completed by the canonical BF audit backlog work. This older non-BF audit issue duplicates work now merged through PRs #209-#219, with the BF issues closed and guard/test coverage in place. The remaining non-duplicate follow-up is #7, which stays open because the upstream Next/PostCSS advisory is not fixed yet.

[baixiangcpp]

Reopening after acceptance review on 2026-06-24. The merged work adds a feature request issue template and public roadmap, but this older audit issue is not fully satisfied: I did not find an empty-search request CTA or a visible flow explaining that existing requests can be voted on/reacted to. Acceptance requires structured requests, vote/reaction support, visible roadmap status, and empty search results offering a request CTA. Keep open until those entry points are implemented and covered by tests.