PyCForge 1.1.9 — Windows acceptance checklist

The automated verification ran on Linux; these native Windows checks remain
pending. This release adds runtime imports and immutable module constants.

1. Install the wheel into your test environment:
   py -m pip install --upgrade .\pycforge-1.1.9-py3-none-any.whl
   py -m pip check
   pycforge-workspace
   Confirm Help -> About reports 1.1.9.

2. Extract the complete source ZIP. Open all four Python files in
   fixtures\runtime_modules_1_1_9. Their module IDs should be main, invoice,
   models, and settings. Make main.py the primary document with Make Primary.
   Choose Transpile -> Runtime and click Transpile. Selecting the mode alone
   must not start conversion. Save the combined generated C as invoice.c.

3. With a compatible 64-bit C11 toolchain installed separately:
   gcc -std=c11 -O1 -DPYCF_RUNTIME_MAIN invoice.c -lm -o invoice.exe
   .\invoice.exe
   Expected output:
   Fruit invoice
   01 apple       2.50
   02 pear        7.00
   03 plum        5.35
   Total: 14.85

4. From that fixture directory, check the CLI path too:
   pycforge convert main.py --runtime-values --module invoice=invoice.py --module models=models.py --module settings=settings.py --output invoice.c
   Include all companions explicitly. No automatic import discovery occurs.

5. Change SCALE in settings.py to 3.0. Existing C should become stale; converting
   again should reflect the new amounts. Change an import to a nonexistent
   module and confirm a diagnostic with the responsible filename. Restore it.

6. In Help search for "module alias", "re-export", and "initialization".
   Inspect Functions and module variables -> Runtime modules at your usual
   display scaling. Verify tables/code and the two-file worked example.

7. Check normal editor operations and Typed conversion still behave as before.
   The runtime warning remains: a conversion does not compile or execute C,
   and exact runtime ForgeLens mappings/C-IR proof checks are still unfinished.

Useful feedback: exact sources/module IDs/primary document, selected mode,
Windows/Python/C compiler versions, output or diagnostic, and screenshots if
an issue is visual. Runtime file I/O and exception recovery are future work.
No PyPI publication was performed.
