PyCForge 1.3.73 — PCFC11 source integration
Prepared 2026-10-31; unpublished review build. CC controls publication.

Scope
-----
The single platform-independent wheel and source distribution contain the exact
PCFC11 0.2.27 source archive, verified extraction, provenance and licenses.
No compiler installer, native binary, bundled GCC toolchain, automatic compiler
build, toolchain download or persistent environment modification was added.
The dedicated Compile button is immediately beside Transpile. Other compiler
families use their separate dialog. Both reuse the existing build service.
README and the searchable offline manual describe prerequisites, source builds,
configuration, smoke tests, standalone tests, troubleshooting and manual updates.

Source custody
--------------
PyCForge base: PyCForge-1.3.72-Windows-GC-Source.zip
SHA-256: c5c5831fc76febb14ac90a6b2c1938fdaf61f17aac6a9a04e39dd775a6948b04
Compiler: PCFC11-0.2.27-source.zip; 5,885,847 bytes
SHA-256: 075fbed6e0acdaf3dad40332a4b47c0268c72f6212c5a5c0939e894054776f68
The compiler archive is byte-for-byte unchanged, including its tests, notices
and historical integration plan. The current manual-build decision supersedes
that archive's historical installer proposals. All prior PyCForge source files
remain present. All 151 converter files match the 1.3.72 baseline byte-for-byte.
Runtime semantics, active GC opt-in, SDK contracts and conversion imports did
not change. SDK landscape metadata was regenerated for engine 1.3.73.

Completed Linux checks
----------------------
* Source CLI extracts all compiler files byte-for-byte and verifies provenance;
  existing empty/populated destinations are refused, corrupted source is refused,
  Unicode/space paths work, and extraction does not produce a compiler binary.
* Built extracted PCFC11 with Python 3.12 and native GCC 13.3 on Linux x86-64.
* Native build regressions cover O0/O1, entry exit status, supplied modules,
  object output, Unicode file I/O, stale/canceled/failed output preservation,
  compiler/source path protection, missing tools and process-tree cancellation.
* Dedicated Qt route checks cover toolbar order and icon/text, source freshness,
  manual Help navigation, independent other-compiler settings, no overlapping
  build operations, and waiting for the dedicated build when closing the IDE.
  Generic compiler profiles, custom binary/output pickers, action contracts,
  resource lifecycle, startup, icons, Help and SDK regression checks also ran.
* Explicit backend selection supplies its directory only to child PATH and
  protects that backend against output replacement. Missing backend failures
  are reported before compiling. The older test expecting an assembly-stage
  failure was updated for this intentional earlier validation and passed.
* Exact icon inventories were updated for the new Compile icon: 57 icons at
  nine resolutions, 513 PNG assets. The final icon suite passed 5 tests and
  615 subtests. Workspace, compiler dialog and Help were visually inspected.
* Fresh current GC fixtures: 78/78 passed using the newly built bundled PCFC11,
  39 cases at O0 and O1. Runner result is DEVELOPMENT_PASS because this run was
  on Linux. It does not qualify the new integration on Windows.
* Documentation verification passed: 32 Help pages in five categories, 82 Python
  examples, 50 Runtime and 32 Typed native comparisons, five API examples, six
  C callers, three module examples and three README examples.
* README rendering preserves the four approved image URLs, no additional
  navigation links, correct banner sizes, concise structure and release version.
* Installed wheel checks: product metadata, startup/About/workspace versions and
  every Help footer show 1.3.73; the source extraction command works outside the
  source checkout. Typed supplied-module and Runtime programs built and ran
  through the installed CLI at O0 and O1 from a path containing spaces/Unicode.
* Final distribution checks: exact wheel/source payload parity, expected package
  data, licenses, metadata and RECORD; strict Twine metadata/README checks.
  The wheel remains py3-none-any. The Windows-friendly source ZIP contains the
  same complete file payload as the source tarball.

Tests were selected for the changed build, UI, documentation, package and GC-kit
surfaces. This is not a claim that the entire historical PyCForge suite or the
unchanged compiler's complete standalone language suite was rerun. Initial
diagnostic/icon inventory assertion failures were corrected; no unresolved
failure remains in the selected checks. Unsupported host/toolchain cases retain
their existing explicit skips.

Native Windows follow-up
------------------------
No native Windows desktop, PowerShell or Windows toolchain was available in
this environment. The prior 1.3.72 78-pass Windows GC result remains evidence
for that checkpoint, not a Windows qualification of this integration.

1. Use Python 3.11–3.13 and the complete MSYS2 UCRT64 GCC toolchain.
2. Extract the supplied source ZIP. From its pycforge-1.3.73 folder, follow
   README / Help: Build PCFC11 from source. Alternatively, select an existing
   complete PCFC11 0.2.27 build with its adjacent include directory.
3. Set Compiler to pcfc11.exe and Assembler / linker to the full UCRT64 gcc.exe
   path. Test a Typed and Runtime program at O0 and O1, including a path with
   spaces/non-ASCII characters. Run the outputs explicitly and keep Copy Report.
4. Check that editing source disables Compile, a failed/canceled build preserves
   old output, and closing the IDE during compilation waits for cancellation.
   Check Other C Compilers keeps its own selected family/settings.
5. From the PyCForge source root, run the existing test-windows-gc.ps1 with
   -CompilerPath pointing to that pcfc11.exe and -ToolchainBin pointing to the
   UCRT64 bin folder. WINDOWS-GC-TESTING.md contains the exact PowerShell commands.
   Return the generated results ZIP. The kit now binds the 1.3.73 source hashes.
6. Compiler testing remains bash test-pcfc11.sh from the extracted compiler root,
   or native PowerShell: py tools\test_windows.py --cc C:\msys64\ucrt64\bin\gcc.exe
   Keep the complete test-results ZIP, including failures.

Qualification limits
--------------------
PCFC11 0.2.27 remains an x86-64 Linux/Windows compiler with documented language
and ABI limits; integration is not a claim of complete ISO C11 support, broad
Python import support, or final GC qualification. Compilation never implicitly
runs the generated program. Existing output is published only after a successful
build whose source is still current.
