[P1] Audit: Related Tools recommendations lack intent explanations

[baixiangcpp]

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

Problem: tool pages show Related Tools, but the recommendations do not consistently explain why a related tool is useful. A user viewing JSON Formatter, JWT Decoder, or Image Resizer should understand the next best action, not just see a list of links.

Affected components:

• Related Tools blocks on tool pages
• Tool manifest relationship metadata
• Bottom-of-page navigation

Reproduction steps:

1. Open JSON Formatter, JWT Decoder, Hash Generator, HTTP Request Builder, and Image Resizer.
2. Review Related Tools cards.
3. Check whether each recommendation explains the task relationship.
4. Compare whether recommendations are ordered by likely next action.

Expected behavior: each related tool card should include a short reason, such as “compare two cleaned payloads” or “verify after decoding.”

Actual behavior: related links are present but often lack intent context and prioritization.

Impact: lower cross-tool usage, weaker workflow discovery, and missed opportunities to guide users through multi-step tasks.

Proposed fix:

• Add relationship metadata: next-step, alternative, verifier, converter, sanitizer, visualizer.
• Show a reason line on each related card.
• Rank related tools by workflow relevance and usage frequency.
• Add “Continue with this workflow” links when applicable.

Acceptance criteria:

• Related tools show intent explanations.
• Top recommendations match the most likely next steps.
• Clicking related tools increases multi-tool sessions.
• Relationship metadata is reusable in search and Pipeline Builder.

[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.