[P3] Audit: Changelog is missing or not visible enough

[baixiangcpp]

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

Problem: byteflow.tools appears to be evolving quickly, but users do not have an obvious changelog that explains new tools, behavior changes, privacy changes, PWA updates, and breaking changes.

Affected areas:

• Footer navigation
• About page
• GitHub README
• Home page
• Tool pages for newly launched tools

Reproduction steps:

1. Open the home page, About page, Contact page, Pricing page, and footer.
2. Look for a changelog or release notes link.
3. Check GitHub releases or commits for user-facing release notes.

Expected behavior: users should be able to see what changed recently and which new tools were added.

Actual behavior: changelog visibility is low or missing.

Impact: less trust in maintenance, missed re-engagement opportunities, and unclear product velocity.

Proposed fix:

• Add /en/changelog.
• Link it from footer, About, and GitHub README.
• Include date, new tools, changed tools, privacy/security updates, and PWA updates.
• Add RSS or JSON feed later if useful.

Acceptance criteria:

• Changelog page exists and is linked from footer.
• Recent releases have user-facing notes.
• Tool additions link to new tool pages.
• Privacy/security relevant changes are clearly labeled.

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