Repository navigation
Conversation
schtasks /Delete used to be ignored, so a denied delete still removed the launcher files and reported the task as gone. A missing task still cleans those files. /End failing because the task is not running stays a non-error. Tests: pnpm exec vitest run tests/daemon.schtasks.test.ts (13 passed). Not run on Windows Task Scheduler. Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
The localization catalog check treats the missing-task regexes as interface copy. They match schtasks output, same as the existing taskkill diagnostic ignore. Tests: pnpm check:localization; pnpm exec vitest run tests/daemon.schtasks.test.ts (13 passed). Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
|
Codex review: needs real behavior proof before merge. What this changesThis PR preserves Windows daemon launcher files when Scheduled Task deletion fails while allowing cleanup when an English diagnostic indicates the task is absent. Example: Run summarize daemon uninstall when deleting Summarize Daemon returns ERROR: Access is denied.
Review scores
ProductKind: Bug fix · Worth it: Yes · Fix scope: Complete Merge readiness⛔ Blocked before merge - 5 items remain Keep this PR open: it addresses a current Windows uninstall bug and follows recorded owner direction, but localized absent-task handling and actionable deletion errors need correction. Priority: P2 Before merge
Findings
Provenance
Tests
Agent review detailsHow this fits togetherThe daemon CLI dispatches Windows lifecycle operations to the Scheduled Task adapter, which runs Windows service commands and manages generated launcher files. flowchart TD
A[Daemon CLI] --> B[Windows service adapter]
B --> C[Shared command runner]
C --> D[Windows Task Scheduler]
D --> E[Deletion result]
E --> F[Preserve or remove launcher files]
Technical reviewBest possible solution: Keep deletion handling in the existing Windows adapter, distinguish absence independently of English diagnostics, and provide localized uninstall recovery guidance. Do we have a high-confidence way to reproduce the issue? Current-main source directly shows that a nonzero /Delete result is ignored before launcher removal and CLI success; no target code or tests were executed. Is this the best way to solve the issue? Checking deletion before cleanup fixes the underlying ordering problem, but the absence distinction must cover localized Windows and the failure message must explain recovery. Full review comments:
Overall correctness: patch is incorrect AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against aaccb7c9c30e. Provenance checked
TestingProof path: unit tests only. SecurityNone. EvidenceAcceptance criteria:
What I checked:
Likely related people:
Preflight sourceSource unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified. LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed November 6, 2026, 4:30 PM ET / 21:30 UTC. |
summarize daemon uninstallon Windows runsschtasks /Deleteand ignores the exit code. If delete is denied, the command still deletes the launcher files and prints that the task was removed, while Task Scheduler keeps the task./Deletenow fails uninstall on a real schtasks error, and the launcher files stay. A task that is already gone (The system cannot find the file specified, or a message that the task does not exist) still cleans those files, so running uninstall again does not stop early./Endfailing because the task is not running is still ignored.This is the absence case called out when #525 was closed. That pull treated every nonzero
/Deleteas failure, including a task that was already gone.pnpm exec vitest run tests/daemon.schtasks.test.tspassed (13 tests). This was not run against Windows Task Scheduler. The absent and denied cases are the English schtasks strings.