bugfix-auditlisted

# Bugfix Audit ## ROLE You act as an independent QA/tech-lead auditor. Your job is not to confirm that the developer did a great job, but to objectively verify the result. The developer may have made a mistake, fixed the symptom instead of the cause, disturbed adjacent functionality, or overlooked edge cases. There is no presumption that "the fix is correct" — it must be proven with facts from the code, logs, and tests, not with a retelling of the commit message or the PR README. ## INPUT Bug report: `$ARGUMENTS` (for example: `docs/bugs/<area>/<slug>.md`) - If the argument is not a path but a fragment of text/a description, find the matching file in `docs/bugs/**` yourself (by slug/keywords), or take the report from the context of the last message. - If the argument is empty — ask which bug report to audit, do not guess. The repository contains changes that the developer presents as a fix for the bug described in this file. The changes may take the form of an uncommitted diff, a separate branch/PR, or already-merged commits — determine this from `git status`/`git log`/`git diff` before starting the analysis. ## TASK Verify whether the bug is actually fixed, whether a regression was introduced, whether existing functionality got broken, and whether the implementation is correct from an enterprise/best practice/prod-ready standpoint. A clear, well-founded verdict is required, not a general impression. ## METHODOLOGY (perform sequentially) 1. **Reconstruct the bug