PyCForge 1.1.8 — Windows acceptance

This candidate adds conversions to Runtime mode. Native Windows checks below
remain pending; the recorded automated results are from Linux.

1. Install the supplied wheel into your test virtual environment:
   py -m pip install --upgrade .\pycforge-1.1.8-py3-none-any.whl
   py -m pip check
   pycforge-workspace

2. Open Help -> About and confirm 1.1.8. Confirm the previous editor, gutter
   navigator, search, folding, completion, and Ting features still behave normally.

3. Paste this program, select Transpile -> Runtime, and click Transpile:

   def main() -> int:
       values = [-3, 2, -1]
       values.extend([4])
       values.insert(0, 5)
       values.remove(2)
       values.sort(key=abs)
       print(values, values.pop())
       print(sum(values), min(values), max(values))
       print(round(2.675, 2), f"price={12.345:08.2f}")
       print("{name!r}: {amount:.2f}".format(name="café", amount=3.5))
       print(list(enumerate(zip("ab", [10, 20]), start=1)))
       return 0

4. Confirm generated C appears, and Save Generated C works. The runtime warning
   still explains its mapping/validation limits. A successful conversion alone
   does not execute the result.

5. With a compatible 64-bit C11 compiler installed separately, compile and run
   the saved file. For GCC:
   gcc -std=c11 -O1 -DPYCF_RUNTIME_MAIN generated.c -lm -o generated.exe
   .\generated.exe
   Compare the output with calling main() in Python 3.12.

6. In Help, search for "enumerate", "sorted", "precision", and "extend".
   Read Runtime conversion, Runtime strings, and Mutable lists pages at your
   normal Windows scaling. Check code alignment and horizontal scrolling.

7. Try an error, such as [].pop(), in the generated program. Expect a checked
   runtime error and nonzero exit, not a crash. Exceptions cannot be caught by
   converted Python in this release.

Useful feedback: Windows version, Python version, C compiler/version, display
scaling, the exact source, selected mode, diagnostic/output, and a screenshot
when the issue is visual. PyPI publication is a separate action.
