PyCForge 1.3.74 — source verification record
2026-10-31

Scope: fixed managed PCFC11 build/discovery, explicit Qt setup, copper UI,
README/offline Help. Bundled PCFC11 remains 0.2.27. This is a candidate handoff;
CC alone publishes PyCForge. No publication was performed.

Baseline: PyCForge-1.3.73-PCFC11-Source.zip
SHA256 d564430052da186da042ac54aabbc122e911f8919f8305c21c4674077ce894b8
Bundled compiler source SHA256:
075fbed6e0acdaf3dad40332a4b47c0268c72f6212c5a5c0939e894054776f68
The compiler archive and converter/runtime implementation are unchanged.

Completed source qualification on Linux x86-64, Python 3.12, GCC 13.3,
PySide6 offscreen:
- Primary regression selection: 135 passed, 337 subtests passed.
- Follow-up source/build/SDK/startup/managed selection: 44 passed,
  8 subtests passed; overlaps the primary selection.
- Special-file startup rejection: 1 passed (also in follow-up selection).
- Native guided Qt build, responsive event loop, saved paths and subsequent
  program compile/run: passed, including spaces and Unicode in source paths.
- Same-timestamp binary changes refused before execution; header/tool changes,
  identity/probe failure, busy locks, canceled/failed builds, promotion rollback,
  interrupted-promotion recovery and output preservation: passed.
- Optional compiler check failure permits startup; safe start defers probe.
- Real compiler/source/tool checks and native O0/O1 smoke programs passed.
- GC runner with PCFC11: 78 passed, 0 failed, DEVELOPMENT_PASS on Linux.
  This is not native Windows qualification.
- Documentation: 32 Help pages, 82 Python examples, 50 Runtime and 32 Typed
  native comparisons, 5 API examples, 6 C callers, 3 module and 3 README examples.
- README: four exact approved images, no extra links, current release heading.
- Qt visual inspection: copper Compile/original icon, setup, program compiler
  and import-control dialogs; readable fields, logs and disabled controls.

An initial GUI-test timeout came from QTest.qWait starving the Python worker.
The wait helper now pumps events and releases the GIL; the actual guided build
and subsequent program build pass. No compiler timeout was weakened.

Fixed location: per-user local application data, not site-packages. Version,
source hash prefix and target identify the slot. The GUI never offers an output
folder for the compiler itself. Python/GCC paths and timeout are explicit setup
inputs. Startup never builds or downloads tools. Local receipt/hash checks are
not publisher signatures or proof against replacement of the entire local state.

Native Windows x64/UCRT64 GUI setup, DLL/process-job handling, restart discovery
and path behavior remain to be run on Windows. The existing PowerShell GC kit is
updated for 1.3.74 and documents using the managed compiler. Prior Windows GC
results do not qualify this new GUI workflow. macOS/ARM64 PCFC11 is unsupported;
other compiler profiles remain available.

The companion release checks report records final distribution filenames,
sizes, SHA256 values, strict package gates and fresh-install qualification.
