jawwad-aliandClaude Opus 5 275663b463 fix(scripts): stop check-prerequisites text mode crashing on a legacy code page ...

_check_file/_check_dir hard-code U+2713/U+2717 and print() them to
sys.stdout. On Windows sys.stdout falls back to the ANSI code page whenever
stdout is not a console — which is every time an agent or a workflow step
captures the output — and U+2713 is unencodable in cp1252:

  stdout encoding: cp1252
  UnicodeEncodeError: 'charmap' codec can't encode character '✓'

So text mode aborted right after printing "AVAILABLE_DOCS:", losing every
per-document line.

Fall back to ASCII when stdout cannot encode the glyph. "[OK]"/"[FAIL]" is
the rendering these markers already have in-tree: Test-FileExists in
scripts/powershell/common.ps1 emits exactly those, and
normalize_status_text in tests/parity_helpers.py maps the glyphs onto them,
so the twins already treat the two forms as equivalent.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-31 12:52:37 +05:00

..

check_prerequisites.py

fix(scripts): stop check-prerequisites text mode crashing on a legacy code page

2026-07-31 12:52:37 +05:00

common.py

feat(scripts): port create-new-feature, setup-plan and setup-tasks to Python (#3386)

2026-07-21 11:40:15 -05:00

create_new_feature.py

fix: auto-correct conflicting feature prefixes (#1829)

2026-07-24 09:13:53 -05:00

setup_plan.py

feat(scripts): port create-new-feature, setup-plan and setup-tasks to Python (#3386)

2026-07-21 11:40:15 -05:00

setup_tasks.py

feat(scripts): port create-new-feature, setup-plan and setup-tasks to Python (#3386)

2026-07-21 11:40:15 -05:00