fix(scripts): type windows taskkill helper#95527
Conversation
|
Codex review: needs maintainer review before merge. Reviewed June 21, 2026, 6:05 AM ET / 10:05 UTC. Summary PR surface: Other +6. Total +6 across 1 file. Reproducibility: yes. from source inspection: current main has TypeScript files importing Review metrics: 1 noteworthy metric.
Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Risk before merge
Maintainer options:
Next step before merge
Security Review detailsBest possible solution: Land the colocated declaration after required checks, keeping it synchronized with the helper's runtime exports. Do we have a high-confidence way to reproduce the issue? Yes from source inspection: current main has TypeScript files importing Is this the best way to solve the issue? Yes. A colocated AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against 6ddbcbd460e9. Label changesLabel justifications:
Evidence reviewedPR surface: Other +6. Total +6 across 1 file. View PR surface stats
What I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
98dde31 to
270402c
Compare
|
Addressed the stale review: rebased onto current main, updated the declaration to cover all current windows-taskkill.mjs exports, and refreshed the proof fields. @clawsweeper re-review |
|
🦞🧹 I asked ClawSweeper to review this item again. |
Summary
scripts/lib/windows-taskkill.mjs.resolveWindowsTaskkillPath,resolveWindowsSystem32Path, andresolveWindowsPowerShellPath.scripts/control-ui-i18n.ts.What Problem This Solves
Current main imports
./lib/windows-taskkill.mjsfrom TypeScript, but the JavaScript helper did not have a colocated declaration file. The CI type shard reported:After main moved the helper to re-export Windows path helpers, the declaration also needs to describe those exports so TypeScript consumers see the real module surface.
Linked context
Real behavior proof (required for external PRs)
scripts/lib/windows-taskkill.mjs; after the latest main changes, the declaration also needed to cover the helper module's three exported functions.F:\openclaw\worktrees\openclaw-windows-taskkill-types, rebased onto currentorigin/main.pnpm exec tsgo --ignoreConfig --noEmit --target ES2023 --lib ES2023 --module NodeNext --moduleResolution NodeNext --types node --skipLibCheck .artifacts\windows-taskkill-types-probe.tsresolveWindowsTaskkillPath,resolveWindowsSystem32Path, andresolveWindowsPowerShellPathfrom../scripts/lib/windows-taskkill.mjs, assigned each result tostring, and the command exited 0 with no TypeScript diagnostics.pnpm tsgo:core:testshard in this branch because a prior full local run stalled after passing the original TS7016 point; this PR uses the focused type probe for the changed declaration surface.scripts/control-ui-i18n.tsimporting./lib/windows-taskkill.mjs.Evidence
Before this patch, current main reports TS7016 for the
windows-taskkill.mjsimport inscripts/control-ui-i18n.ts.After this patch, the focused TypeScript probe covering all three exports exits 0 with no diagnostics.
Tests and validation
pnpm exec tsgo --ignoreConfig --noEmit --target ES2023 --lib ES2023 --module NodeNext --moduleResolution NodeNext --types node --skipLibCheck .artifacts\windows-taskkill-types-probe.tsgit diff --checkRisk checklist
windows-taskkill.mjsruntime export surface.Current review state
Ready for ClawSweeper re-review and maintainer review.