PCFC11 0.2.31 — Bash test and feedback

1. Extract PCFC11-0.2.31-source.zip into a new folder.
2. Use Bash on Linux x86-64, or MSYS2 UCRT64 / Git Bash on Windows x64.
   Have 64-bit Python 3.11+ and GCC available. Windows requires native Windows
   Python and MinGW-w64 UCRT64 GCC, not MSYS/Cygwin Python or a POSIX compiler.
3. From the extracted PCFC11-0.2.31 directory run:

   bash test-pcfc11.sh

   If necessary:

   bash test-pcfc11.sh --cc 'C:/msys64/ucrt64/bin/gcc.exe'
   PCFC11_TEST_PYTHON='C:/Python313/python.exe' bash test-pcfc11.sh

   Use your actual executable paths. Git Bash alone does not provide GCC/Python.
4. Allow several minutes for the 49-program PyCForge compatibility phase.
   The script also tests 146 initializer cases and 130 bit-field layouts, repeated includes, headers, language rules, ABI, optimization, robustness,
   Unicode file I/O and benchmarks. No PyCForge installation is needed.
5. Return the ZIP printed after "Feedback archive:", even if it says FAIL.
   If no ZIP is created, return the printed setup-*.txt file. Include your
   terminal choice and any Windows executable blocking or manual action.

Each phase has a 600-second limit; --timeout 1200 increases it. Independent
phases continue after failures. Normal Ctrl+C saves completed results; forced
termination may prevent ZIP creation. Exit status: 0 pass, 1 fail, 130 interrupted.
The script installs/uploads nothing. Logs can include local paths.

PowerShell alternative:

   python tools/test_windows.py

Version 0.2.30 adds shared CFG topology, reachability and immediate dominators
for integer analyses, plus independent graph oracles and failure checks.
The condition-path suite and all earlier gates remain. The standard run has
40 Linux / 39 native Windows phases. Native Windows 0.2.30 execution is pending;
Linux instruction models do not qualify Windows PE/UCRT, SEH or guard pages.

Direct statement labels/goto now participate in the bounded integer CFG.
Labeled branches/loops survive constant pruning. See docs/CFG_LABELS.md.

The 0.2.31 driver check also exercises explicit strict floating-point flags.
