ruleslisted

# found-issues — agent rules <!-- loc-override: single auto-loaded ruleset; splitting changes per-session injection --> **Issues found and not tracked are issues lost.** When you notice a defect outside your current task scope, log it — never dismiss it as "pre-existing" or "not my code." The user logs nothing; you maintain `docs/found-issues.md` on their behalf — via the commands below, never direct Write/Edit. ## Logging `/found-issues:log <path:line> — <symptom> (suggested: <fix>)` — `--critical` for urgent items; an abstract topic may replace `path:line`. - **Log:** demonstrable bugs; off-task errors/warnings in test/build/log output; nameable race conditions; security defects; dead code (zero call sites); misleading docs; broken contracts. - **Don't log:** style nits; "could be cleaner"; known deprecations; existing TODOs; things you fixed in-task; third-party bugs; speculation without a concrete symptom; unmeasured perf hypotheticals; duplicates (the command dedups on path:line). - When in doubt, log — false positives get cleaned at sync; false negatives are silent. ## Annotation after PR / commit A hook auto-runs annotation after `gh pr create` and `git commit`: entries whose cited line the diff modifies are annotated automatically and reported in one line. Your job is ONLY the judgment cases the hook surfaces — a candidate list means the CLI could not decide. Compare each candidate's symptom against what the PR/commit actually changes, then run the printed `fou