This section is generated by Optimize-CodexWorkspace.ps1.
Detected stack: Python, PowerShell
python -m compileall .Invoke-ScriptAnalyzer -Path . -Recurse
- Keep changes scoped to the requested task.
- Inspect existing patterns before introducing new dependencies.
- Run the relevant validation commands before committing.
- Never commit credentials, local environment files, or generated secrets.
For every PR description, merge proposal, push summary, or release validation note, use this structure:
Explain the concrete bug, gap, or maintenance issue. Include the root cause when known.
Explain the technical change and why this approach was chosen.
State whether runtime, product, user, maintainer, or developer behavior changes. If there is no behavior change, say so explicitly.
- Before: failing run, error message, limitation, or previous behavior
- Tests: targeted tests and results
- Checks: CI, lint, smoke tests, or manual validation
- Autoreview: clean, findings addressed, or not run
Keep the Evidence section factual. Prefer concrete commands, run links, failure messages, and pass/fail results over vague statements.