aod-bugfixlisted

# /aod.bugfix — One-Shot Bug Fix Command ## Pre-Run Safety > Advisory (non-blocking): Before proceeding, consider stashing or committing any in-progress work (`git stash` or `git commit`). If Phase 3 fails mid-execution, partial edits can be reverted cleanly from a known-good state. `[Phase 0] Acknowledging input...` ## Phase 0: Input Acknowledgment & Context Summary Detect the input mode based on what the user provided: **If pasted content (error message, stack trace, logs, or failing test output):** First, check whether an error or symptom is identifiable in the pasted content: - **If no error message or symptom is visible** (e.g., the paste contains only code, config, or prose with no failure signal): stop and ask specifically — "I don't see an error message or failure symptom in what you pasted. Can you share the actual error, exception, or unexpected behavior you're seeing?" Do not proceed to Phase 0b until a failure signal is present. If an error or symptom is present, proceed with parsing: - **Multi-error input**: If multiple errors or exceptions appear, identify the PRIMARY failure — the first error in chronological order or the root-level exception (not cascading/downstream errors). Scope all acknowledgment and analysis to the primary failure only. In the context summary output, briefly note how many secondary errors were present and that they are considered downstream (e.g., "Note: 2 additional errors detected — treated as downstream of primary failure"). Do