[P2] Audit: Tool buttons and action naming are inconsistent across pages

[baixiangcpp]

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

Problem: tool actions use inconsistent labels and ordering across pages. Examples include Try Example, Sample, Reset, Clear, Clear All, Format, Minify, Run, Preview, Copy, Copy Output, Download, Export JSON, Share URL, and Send to. Users should learn one interaction pattern and reuse it across tools.

Affected components:

• Tool action bars
• Output panel copy/download controls
• Pipeline Builder action controls
• External-request tool actions

Reproduction steps:

1. Open JSON Formatter, Base64 Encode/Decode, Regex Tester, Image Resizer, YouTube Thumbnail Grabber, and Pipeline Builder.
2. Compare button order, labels, disabled states, and success feedback.
3. Check mobile wrapping and keyboard order.

Expected behavior: action names and button order should be standardized by action type.

Actual behavior: actions are understandable individually, but the vocabulary and ordering differ across tools.

Impact: inconsistent learning model, higher cognitive load, and more QA surface area.

Proposed fix:

• Define a global action convention: Sample, Reset, Clear, Run/Generate, Copy, Download/Export, Share.
• Use the same order and disabled-state rules across tools.
• Standardize success toasts and error states.
• Add a shared ToolActionBar component.

Acceptance criteria:

• Priority tools follow the same action order and naming.
• Copy/download/share states are consistent.
• Keyboard tab order follows visual order.
• Regression tests verify disabled/enabled states.

[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 ToolActionBar ordering and disabled-state guards, but this older audit issue is not fully satisfied because copy/download/share states are still inconsistent across priority tools; canonical/related issue #166 is reopened for the same acceptance gap. Keep this open until priority tools consistently follow the shared action naming/order, keyboard order, disabled/enabled behavior, and copy/download/share success/failure states with regression coverage.