2026-01-30 - Harden debug resources and folder-size ops tooling

Timeline

• (Context) Beginner friction was clustering around debugging and terminal confidence
• (Action) Expanded _resources with common-errors-and-patterns.md, debugging-decay-explained.md, and glossary.md
• (Action) Continued doc-reader setup by updating runner scripts, .gitignore, and run.bat
• (Action) Added folder-size wrappers (Get-FolderSizes.ps1, run_powershell_script.bat, and Send-To launch hooks)
• (Observation) Better diagnostics language and helper wrappers reduced first-run friction
• (Open Thread) Add a short START_HERE.md bridge that introduces doc_reader earlier

Context

• Support docs and helper scripts were prioritized because they remove recurring beginner blockers
• Ops utility upgrades were done in parallel to speed daily navigation and storage checks

Actions

• Updated _resources/common-errors-and-patterns.md.
• Updated _resources/debugging-decay-explained.md.
• Updated _resources/glossary.md.
• Updated doc-reader runner files and launch wrappers.
• Implemented Get-FolderSizes.ps1 for folder-size inspection.
• Implemented run_powershell_script.bat for one-click execution.

Observations

• Drag/drop and Send-To wrappers are high value for day-to-day operations
• Troubleshooting docs work best when they name failure signatures explicitly and pair each with a fix

Open Threads

• Decide whether to ship folder-size utility as course tooling or keep it ops-side only
• Validate doc_reader setup on clean machines without local assumptions

Boundary Reminder: Seeds. No maintenance. No roadmap.