[P2] Audit: Copy, download, and share success states are not standardized

[baixiangcpp]

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

Problem: copy, download, export, and share actions appear across most tools, but success, disabled, and error states are not fully standardized. Users should always know what was copied, downloaded, exported, or shared.

Affected components:

• Copy buttons
• Download buttons
• Export JSON
• Share URL
• External-request download actions
• Pipeline Builder actions

Reproduction steps:

1. Open several tools.
2. Trigger copy actions with empty output, valid output, and invalid output.
3. Trigger download/export actions where available.
4. Compare toast wording, disabled states, focus behavior, and clipboard fallbacks.

Expected behavior: all actions should use consistent status copy, toasts, disabled states, and error recovery.

Actual behavior: feedback works in many places but varies by tool.

Impact: users may not know whether an action succeeded, especially in mobile or keyboard flows.

Proposed fix:

• Create shared action result states: idle, disabled, pending, success, failed.
• Standardize toast copy and duration.
• Show what was copied/downloaded.
• Add clipboard API fallback handling.
• Ensure failure states are accessible.

Acceptance criteria:

• Copy/download/share actions behave consistently across priority tools.
• Empty output disables actions or explains why unavailable.
• Success and failure messages are accessible.
• Regression tests cover clipboard and download behavior.

[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 shared ToolActionBar, ordering, disabled reasons, and representative JSON/action-bar tests, but this older audit issue is not fully satisfied: copy/download/share success, pending, failure, and fallback behavior is still implemented ad hoc across many tools, and regression coverage does not yet cover priority tools broadly. Keep this open until shared action result states and accessible success/failure messaging are consistently applied and tested for copy, download/export, share, and external-request actions.