System-Maintenance — Kickoff (2026-07-21)

Kicked off the System-Maintenance ongoing project (KB-native, Core/IT/Projects/System-Maintenance/) — computer/network maintenance across all machines. Full state lives in that project’s STATUS.md/LESSONS.md; this is the closure summary of the kickoff task.

What was done

Scaffolding + consolidation:

• Created DASHBOARD/STATUS/ROADMAP/UPGRADES/LESSONS/Tasks/ structure, registered in Ongoing-Projects.md + Core/IT/JOB_DESCRIPTION.md
• Consolidated Slow Computer.md + HD Purging.md into the new project (migrated-then-deleted, verified against working-tree content first)
• Drafted System-Inventory.md from confirmed facts, TODOs filled in by Talbot (Win 10.0.19045, laptop = backup-only, NAS = WD My Cloud ~1.5TB)

diskcheck monitor — root-caused, fixed, verified:

• Real task name is DiskSpaceCheck (not diskcheck), was firing weekly but every run failed (ERROR_FILE_NOT_FOUND) — bare uv path + RunLevel: Highest broke PATH resolution for the elevated Task Scheduler action
• Fixed: full path (C:\Users\Admin\.local\bin\uv.exe) + RunLevel: Limited
• Verified via actual Start-ScheduledTask trigger, not just “edit accepted” — LastTaskResult: 0, fresh log entry
• General gotcha + first-fix-attempt paste-order failure promoted to GlobalDevRules.md §3.9 and SMTM_System.md’s paste-failure-modes section

C: drive space — resolved:

• 7.9GB → 52GB free: Temp, .gemini, .windsurf/.codeium/.trae, C:\xfer\bak, kopia cache relocation (~12GB, spun off to my_backup-kopia-cache-relocation), plus Talbot’s own additional app purge
• Chrome cache checked (~200MB) — not worth clearing, closed
• Recurring maintenance automated: MonthlyDriveCleanup scheduled task (weekly, RunLevel: Limited), script at D:\FSS\Software\Utils\Windows\cleanup-c-drive.ps1 (relocated there after first being written to the wrong place — see lesson below)
• WSL vhdx found at 52.99GB on C: (~9GB reclaimable) — one-time wsl --set-sparse true fix handed to Talbot (can’t run from inside an active WSL session)
• .wslconfig memory cap: deliberately not applied — conflicts with a prior documented decision to leave WSL uncapped for dev work; Talbot confirmed “leave as is”

Windows 11 decision:

• Windows 10 already past mainstream EOL (Oct 2025); PC Health Check confirms Win11 unsupported (CPU: Ryzen 7 1700, pre-dates the supported list)
• Recommendation written in Windows11-Upgrade-Decision.md: enroll in free Consumer ESU as the bridge, defer any hardware decision to a future AI-workstation build (which resolves the CPU issue as a side effect) — Talbot agreed

Lessons promoted

• Windows Task Scheduler + elevation breaks PATH resolution for bare exe names → GlobalDevRules.md §3.9 + project LESSONS.md
• Multi-line pasted PowerShell can execute out of order (3rd paste-failure mode) → SMTM_System.md
• New utility scripts have fixed homes by platform (Windows → D:\FSS\Software\Utils\Windows\, Python → PythonUtils\, WSL → ~/utils/) → ai-config/AGENTS.md Dev Standards (new section), after a first draft of the cleanup script was mistakenly written to C:\Scripts\

Spun off

• my_backup-kopia-cache-relocation (Core/IT/Tasks/) — kopia cache relocation, completed within this same session (~12GB freed)

Open, not closed

• WSL vhdx one-time compaction (wsl --shutdown + --set-sparse true) — Talbot to run outside any active WSL session
• Windows 10 Consumer ESU enrollment — Talbot to do when convenient
• Azure Data Studio / DbSchema uninstall — confirmed safe if unused, Talbot’s call via Settings → Apps
• Future AI-workstation build — no urgency by Talbot’s own framing, new task when it becomes real

Full task history (all 6 Claude/Talbot Response rounds): Core/IT/Projects/System-Maintenance/Tasks/archive/2026-07/System-Maintenance-Project.md