fix: doctor stale-tasks must respect scope visibility#189
Conversation
The v2.7.3 fix switched from direct file scanning to Store.all_entries_unfiltered(), but that still bypasses scope filtering. Entries with scope:private from a different agent were reported as phantom stale tasks. Now uses Store.all_entries() with the resolved agent identity, matching exactly what `palaia list` shows. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
🤖 Codex ReviewOpenAI Codex v0.117.0 (research preview)workdir: /home/dev/projects/palaia-plugin
|
Private-scoped entries from a different agent must not appear in doctor's stale-task check. Reproduces the exact user-reported scenario: agent-a writes a private task, doctor runs as agent-b → must be ok. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Every bugfix must include a regression test reproducing the exact user-reported symptom. Green test suite alone is not sufficient. Learned from v2.7.3 doctor fix that passed tests but didn't fix the actual bug. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
🤖 Codex ReviewOpenAI Codex v0.117.0 (research preview)workdir: /home/dev/projects/palaia-plugin
|
Summary
Store.all_entries_unfiltered()which still bypasses scope filteringscope: privatefrom a different agent were reported as phantom stale tasksStore.all_entries()with resolved agent identity — matches exactly whatpalaia listshowsTest plan
palaia doctorno longer reports phantom stale tasks on production instance🤖 Generated with Claude Code