Repository navigation
machine-health: keep the installed monthly wrapper current #9253
Description
/machine-health:setup schedule (#9243) copies the monthly wrapper into <StateBase>/scheduler/ with the plugin, state and report roots written in. A plugin update or a changed report_dir option leaves that copy stale: its exact allow rules no longer match the audit's commands, so later runs fail until the owner reruns schedule. Setup check reports the stale copy, but nothing refreshes it.
One smaller item on the same files:
Install-MonthlyRunwrites the wrapper andscheduled-settings.jsonin place, not through a temp file and a rename, so an interrupted install can leave a half-written copy.checkreports that state as stale.
Done when a stale copy is refreshed without a manual schedule rerun (for example, an audit run that finds it stale offers the refresh), and both files are written atomically.
🤖 Generated with Claude Code
Activity
github-actions commentedon Oct 22, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
#9253 (comment)
The decision settles the three open questions. The issue is rescoped to the wrapper copy only.
checkstep 6 offers the refresh, and it runs only on the owner's yes.Install-MonthlyRunwrites the wrapper throughWrite-StateFile. The acceptance criteria in that comment define the work.Automated triage, applied by the lanes App.
github-actions commentedon Oct 26, 2026
The triage sweep dispatched intake triage for this issue (attempt 1 of 2).
melodic-automation-lanes commentedon Oct 26, 2026
Not admitted to the issue lane: no trusted-human acceptance criteria: a listed human must put the confirmed
- [ ]criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).melodic-automation-lanes commentedon Oct 26, 2026
The latest triage verdict holds nothing: the issue is at
status: ready.melodic-automation-lanes commentedon Oct 26, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: A stale installed monthly wrapper is refreshed from the template with an owner yes, and Install-MonthlyRun writes the wrapper through a temp file and a rename.
Related work
Open questions
RECOMMENDED: Yes. Drop scheduled-settings.json and the report_dir trigger, and cover only wrapper drift from the template. Basis: plugins/machine-health/skills/setup/scripts/Install-MonthlyRun.ps1:23-28
RECOMMENDED: Have setup check step 6 offer the refresh on the owner's yes by calling Install-MonthlyRun, since the scheduled run is unattended and cannot ask. Basis: plugins/machine-health/skills/setup/SKILL.md:342-344
RECOMMENDED: No. Require an explicit owner yes, as the schedule action does. Basis: judgment
Sources read
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.kyle-sexton commentedon Oct 27, 2026
Decision recorded. The owner answered in the Refinement and Issue Triage sessions (2026-10-25), deciding the open items below on the facts:
No owner ledger (
.work/*/interview-checklist.md,.work/gh-monitor-owner-decisions/) names this issue.Questions from intake's refinement (#9253 (comment)):
Decided: Yes. Two parts of the body no longer hold on origin/main. The copy has no roots written in:
Install-MonthlyRuncopies the template unchanged (plugins/machine-health/skills/setup/scripts/Install-MonthlyRun.ps1:25), and the wrapper derives its state base from its own folder (plugins/machine-health/skills/setup/templates/monthly-run.ps1:51-56). So a changedreport_dirdoes not stale it. Andscheduled-settings.jsonis only removed, never written (Install-MonthlyRun.ps1:26-27), so it needs no atomic write. What remains: the copy goes stale when a plugin update changes the template (plugins/machine-health/skills/setup/SKILL.md:342-344), and the copy is written in place byCopy-Item(Install-MonthlyRun.ps1:25).Decided:
checkstep 6 offers it. Step 6 already detects the stale copy (SKILL.md:150-158). The scheduled audit runs unattended underclaude -p(SKILL.md:339-341) and cannot ask. The offer runs onlyInstall-MonthlyRun, not theschtaskscommandscheduleruns (SKILL.md:365).checkis declared read-only (SKILL.md:2,:93), so the declaration names this one write.Decided: No.
schedulewrites the copy "only on the owner's yes" (SKILL.md:2), and the copy is code the scheduled task runs. The refresh keeps that gate.Existing control for the atomic write:
Write-StateFilewrites a temp file in the same folder and swaps it in, so a reader sees the old file or the new one (plugins/machine-health/skills/audit/scripts/windows/lib/Write-StateFile.ps1:16-19). The fix reuses it rather than adding a second recipe.Acceptance criteria:
Install-MonthlyRunwrites the wrapper throughWrite-StateFile, notCopy-Itemin place.checkfindsWrapperCurrentfalse, it offers the refresh. On the owner's yes it runsInstall-MonthlyRunalone, thenTest-MonthlyRunCurrent, and reports the result. Without a yes it writes nothing.checkheading and the skill description inplugins/machine-health/skills/setup/SKILL.mdname that one write, done only on the owner's yes.plugins/machine-health/skills/audit/tests/windows/scheduler/Install-MonthlyRun.Tests.ps1has a case where a stale copy, afterInstall-MonthlyRun, reports current and no temp file is left in the scheduler folder.