PyCForge 1.1.10 — Windows acceptance checklist

Automated validation ran on Linux. Native Windows checks below remain pending.
This package adds connected UTF-8 file workflows in Runtime conversion.

1. Install and launch from the same Python environment:
   py -m pip install --upgrade .\pycforge-1.1.10-py3-none-any.whl
   py -m pip check
   pycforge-workspace
   Confirm Help -> About reports 1.1.10.

2. Open Help with F1. Search for "file processing workflow".
   Check the new guide, operation table, Unicode/newline example, and complete
   report. All 21 pages should load. Check a narrow window: prose and tables
   should wrap, and code should remain legible and selectable. The Help pages
   should describe usage and limits without development-cycle status.

3. Extract the complete ZIP and use fixtures\runtime_files_1_1_10 as a test
   working directory. It contains main.py, text_files.py, pricing.py, prices.txt,
   and expected-report.txt. Open the three Python files in the workspace with
   module IDs main, text_files, and pricing. Make main.py primary. Select
   Transpile -> Runtime, then click Transpile; selecting the mode alone does
   not start conversion. Save the combined C as report.c in this directory.

4. From that directory, with a compatible 64-bit C11 toolchain:
   gcc -std=c11 -O1 -DPYCF_RUNTIME_MAIN report.c -lm -o report.exe
   .\report.exe

   Expected terminal output:
   Wrote 77 characters to report.txt

   Compare report.txt with expected-report.txt. Both should contain exactly:
   Fruit prices
   01 apple    2.50
   02 pear     7.00
   03 plum     5.35
   Total: 14.85

   There is a final LF newline. The writer uses newline="", so bytes should
   match even on Windows. Python comparison:
   py -c "from pathlib import Path; assert Path('report.txt').read_bytes() == Path('expected-report.txt').read_bytes(); print('File bytes match')"

5. Repeat from the installed CLI:
   pycforge convert main.py --runtime-values --module text_files=text_files.py --module pricing=pricing.py --output report.c
   Conversion must not read prices.txt or create report.txt; only executing
   the generated program does that. A missing prices.txt when report.exe runs
   should report text_files.py line 2 and exit with an error.

6. Copy the Unicode example from Help into its own source document and
   convert in Runtime mode. Check the documented character counts and line
   output. Also test a filename such as café-🙂.txt. With newline="", written
   LF stays LF; with newline omitted, Windows output uses CRLF. Reads with
   newline omitted normalize CR, CRLF, and LF. File bytes are the useful check
   if the terminal font does not display a glyph.

7. Confirm the earlier runtime module, collection, formatting, and typed
   examples still convert; editor completion, navigator Copy, Undo, and the
   six Ting reviews remain available. No new installation dependency is added.

If a check fails, send the source files, selected mode, diagnostics, compiler
command/version, complete stdout/stderr, and the resulting file bytes or a
screenshot of a layout problem. No PyPI publication was performed.
