PyCForge 1.3.75 — compiler icon and entry guidance
2026-10-31

Scope: use the original SDK code-bracket mark for PCFC11 controls and display
the reason when executable compilation lacks an eligible entry. This is a
maintenance handoff. Nothing was published; CC alone publishes PyCForge.

Source baseline: PyCForge-1.3.74-PCFC11-Setup-Source.zip
SHA256: 57fc2dd3f3d92edfcc1459caa1e0c952b202da5091b70eaca9dfca6fa3274ed5

The exact 256px SDK 0.6.2 PNG is retained in the icon catalogue. SHA256:
b2e538b4c751a95dcd32d9eed45e01d34f8fd52b5a2ef91f7aac6897a1778a4e
Eight smaller sizes are smooth resamples; there is no regenerated artwork.
The new pcf-original resource is distinct from the existing eagle brand-mark.
PCFC11 toolbar/menu actions, buttons and window icons use pcf-original. General
application branding and copper styling are retained.

Compilation now displays Entry function required with an actionable explanation
when Executable output has no eligible entry. Object output remains available
for callable functions. Source freshness is explained separately. Existing build
result/log text is preserved when input requirements subsequently change.

Completed checks before packaging, Linux x86-64 with Qt offscreen:
- UI/action/icon/startup/setup selection: 45 passed, 729 subtests passed.
- Other compiler profiles, Windows GC runner and source custody: 22 passed,
  2 subtests passed.
- Missing-entry transition test passed again after the status wording change.
- Documentation: 32 pages, 82 Python examples; 50 Runtime and 32 Typed native
  comparisons, 5 API examples, 6 C callers, 3 module and 3 README examples.
- README heading updated, four approved images and no extra links preserved.
- SDK landscape metadata regenerated; public contract and conversion resources
  remain unchanged apart from engine release identity.
- Rendered toolbar, PCFC11 setup/program dialogs, missing-entry explanation and
  import dialog inspected. All nine icon sizes and resources validate.
- All 151 converter/runtime files, bundled PCFC11 source, managed compiler
  service/storage and GCC/PCFC11 build service are unchanged from 1.3.74.

Windows evidence supplied by CC on 2026-10-31 for 1.3.74:
PCFC11 built successfully; source compilation succeeded; startup recognized the
managed build and allowed direct access to its compile dialog. This is a
user-reported workflow pass, not an independently inspected full Windows matrix.
Output kind of the final reported compilation was not specified. Earlier UI
review confirmed that choosing Object file enabled compilation without an entry.
No new native Windows results archive was supplied with this message.

The existing Windows GC kit is carried forward for 1.3.75. GC code is unchanged;
this icon/feedback update does not claim another 78-case native Windows or Linux
run. Prior GC evidence retains its original release/platform context.

Next direction recorded from CC: continue Crucible engine and import maturity.
NumPy is a registered conversion expansion with documented finite 1D float64
Runtime limits. This maintenance update adds no new NumPy operations.

The companion release report records final archive identities, strict package
gates and installed-wheel checks.
