Re-opened after a phantom-completion audit. A verify-first judge previously closed the original issue as ALREADY_IMPLEMENTED with zero code change; an independent adversarial re-audit against current main confirmed the work is still missing.
Audit finding (files: worker.py)
worker.py: Independently confirmed the defect is still present. Issue #89 (auto-close genuinely unimplementable issues) is a distinct feature from #84 (auto-close already-resolved issues), per docs/philosophy.md lines 44 vs 47 and line 32 ("already resolved OR genuinely unimplementable"). The cited code at worker.py:1300 is only the #84 RESOLVED path: it closes with --reason completed and stage auto_closed_resolved. The empty-diff judgment prompt (worker.py:1280-1286) offers exactly two words — RESOLVED (change already present) or RETRY (still needs doing). There is no UNIMPLEMENTABLE outcome. A genuinely infeasible/out-of-scope issue is neither "already present" nor should be retried, so the judge returns RETRY, the else branch (lines 1313-1318) re-queues via mark_blocked stage=empty_diff_detected, and the job loops to MAX_RETRIES -> max_retry_exceeded / gave_up rather than being auto-closed with an explanation. A repo-wide grep found no not_planned, UNIMPLEMENTABLE, auto_closed_unimplementable, or any feasibility close path; the only other auto-close is the unrelated stale-discussion timeout in scheduler.py. The #91 pre-implementation preamble (worker.py:892-901) merely asks the implementer to summarize why but never closes the issue. Severity medium: not a crash, but a missing autonomy feature that forces human intervention (gave_up) exactly where philosophy.md says the bot must self-close, degrading the autonomy score.
Note
Some original citations were fabricated (line numbers that do not exist in the file) — that is itself evidence the close was not based on real code. Please verify against current main.
Filed by cross-repo phantom-completion audit (from claude-bot-go operator). Reported as an issue for the maintainers; not auto-implemented. Checked for duplicates before filing.
Re-opened after a phantom-completion audit. A verify-first judge previously closed the original issue as ALREADY_IMPLEMENTED with zero code change; an independent adversarial re-audit against current
mainconfirmed the work is still missing.Audit finding (files: worker.py)
worker.py: Independently confirmed the defect is still present. Issue #89 (auto-close genuinely unimplementable issues) is a distinct feature from #84 (auto-close already-resolved issues), per docs/philosophy.md lines 44 vs 47 and line 32 ("already resolved OR genuinely unimplementable"). The cited code at worker.py:1300 is only the #84 RESOLVED path: it closes with --reason completed and stage auto_closed_resolved. The empty-diff judgment prompt (worker.py:1280-1286) offers exactly two words — RESOLVED (change already present) or RETRY (still needs doing). There is no UNIMPLEMENTABLE outcome. A genuinely infeasible/out-of-scope issue is neither "already present" nor should be retried, so the judge returns RETRY, the else branch (lines 1313-1318) re-queues via mark_blocked stage=empty_diff_detected, and the job loops to MAX_RETRIES -> max_retry_exceeded / gave_up rather than being auto-closed with an explanation. A repo-wide grep found no not_planned, UNIMPLEMENTABLE, auto_closed_unimplementable, or any feasibility close path; the only other auto-close is the unrelated stale-discussion timeout in scheduler.py. The #91 pre-implementation preamble (worker.py:892-901) merely asks the implementer to summarize why but never closes the issue. Severity medium: not a crash, but a missing autonomy feature that forces human intervention (gave_up) exactly where philosophy.md says the bot must self-close, degrading the autonomy score.
Note
Some original citations were fabricated (line numbers that do not exist in the file) — that is itself evidence the close was not based on real code. Please verify against current
main.Filed by cross-repo phantom-completion audit (from claude-bot-go operator). Reported as an issue for the maintainers; not auto-implemented. Checked for duplicates before filing.