PyCForge 1.3.77 — checked array division and stable PCFC11 preparation
2026-10-31

Baseline: PyCForge-1.3.76-Source.zip
SHA256 fac6ec97a710748373aee6898cc8d199697730169ef5154e30dfb97591894109
Nothing is published by this workflow. CC alone publishes releases.

PCFC11 PREPARING DIALOG
CC's Windows screenshot identified repeated setGeometry warnings on
PCFC11PreparingDialog. The worker's command paths and multiline --info-json
output were connected directly to its wrapped status label, changing minimum
layout requirements while the dialog was displayed. The cover now retains
a stable checking message. Its complete layout is polished and activated before
the initial size is chosen. The indeterminate progress bar, original PCF artwork,
copper accents, cancellation and subsequent failure/setup handling remain.
Warnings are not suppressed globally. This addresses the observed sizing trigger;
the actual Windows desktop still requires confirmation on CC's machine.

CRUCIBLE AND NUMPY
Bundled NumPy advances to 0.4.0 / crucible.array1d-f64/0.4, with 18 exports.
The new true_divide alias, np.divide, operator / and in-place /= share one checked
native division kernel. Module calls and / allocate independent results. /= keeps
array identity and all aliases; it commits only after the entire result succeeds.
Type errors, unequal lengths, zero divisors, overflow, allocation failure and work
exhaustion cannot partially update the destination. Failed temporary allocations
are released. Receiver/index/operand expressions run once in Python source order.

Arrays remain contiguous, one-dimensional, finite float64. At least one operand
must be an array; two arrays must have equal lengths. Empty division performs no
element division, so empty / 0 remains empty. Finite subnormals and signed-zero
underflow are allowed. Zero divisors raise ValueError and nonfinite results raise
OverflowError under this bounded profile. No warning/seterr compatibility, views,
general broadcasting, additional dtypes, multidimensional arrays, floor division,
remainder, out or where options are claimed. Scalar division keeps its own rules.

The four-field authoring contract, array package format, SDK public interface and
workbench format are unchanged. The engine publishes the new operation, forms,
starter fixtures, completion and exact Help. The independent vector starter
uses true_quotient. The unchanged SDK 0.6.3 handles both namespaces.

Packages using only older operations retain profiles 0.1/0.2/0.3 and their original
fingerprints. The exact prior NumPy 0.3.0 package is retained as a regression
fixture. New-engine operator support applies to existing Runtime arrays without
rewriting older declarations. A preceding engine's support must not be inferred
from an older package's admission.

QUALIFICATION
- 283 distinct recorded source test cases have passing final outcomes, with no
  remaining failed or skipped cases in that selected ledger. This includes the
  158-case regression run, memory guards, import registration, editor completion,
  compiler setup/compilation dialogs, SDK metadata, documentation contracts and
  distribution checks. Additional subtests are reported in the individual logs.
  This is a focused qualification set, not a claim that the whole historical
  repository suite was executed.
- NumPy template: 27 runnable fixtures passed GCC UBSan and PCFC11 0.2.27 O0/O1
  (81 native runs), plus 23 expected source-mapped conversion rejections.
- Seed 1377 numerical matrix: 72 array pairs across lengths 0, 1, 2, 7, 8, 17, 33,
  128 and 129; 504 division results matched NumPy 2.3.5 on each of GCC UBSan and
  PCFC11 O0/O1. This includes random finite data, signed zeros and subnormals.
- GCC AddressSanitizer/UndefinedBehaviorSanitizer and PCFC11 O0/O1 pass allocation
  fault injection, late-zero/work-budget rollback and active-GC root retention.
  ASAN_OPTIONS=detect_leaks=0 is used for this host; separate allocation counters
  verify all tracked blocks are released. No LeakSanitizer pass is claimed.
- Actual SDK 0.6.3 in a separate headless environment, without engine/Qt/NumPy:
  both 50-case NumPy and independent-vector projects scan, verify, deterministically
  package and register. Changed declarations invalidate verification and preserve
  the prior output package. All SDK product bytes remain unchanged.
- The actual installed 1.3.76 engine refuses the 0.4 package while retaining its
  Ready 0.3 registration. Rejected imports intentionally retain a diagnostic row.
  The current engine admits actual 0.1/0.2/0.3 packages. Offline SDK reference
  browsing retains the new operation choices.
- Portable Windows GC kit regenerated for 1.3.77: 40 cases / 80 checks, all passed
  with PCFC11 O0/O1 on Linux. The new case retains division aliases and nested
  results during active GC. Status DEVELOPMENT_PASS; windows_qualified is false.
- PCFC11 compiler-dialog tests: 13 passed with the actual compiler selected.
  Raw-command/JSON geometry tests pass with 9/14/20 point fonts and at 200% scale.
  The 125% offscreen loading/setup/import surfaces were rendered and inspected.
- Maintained manual: 32 Help pages, 82 Python examples (50 Runtime and 32 Typed
  native comparisons), five API examples, six C callers, three module examples
  and three README examples pass. The later NumPy version-label correction does
  not change any example.
- README changes are confined to the top version and the NumPy capability bullet.
  The exact five approved URLs, image order, banner widths and structure remain.
  SDK landscape/template export and their inventory checks pass.

CORRECTED QUALIFICATION ATTEMPTS
The first compatibility test referred to a nonexistent archive member; it now
checks the actual preceding package fingerprint. jsonschema and the Markdown
renderer extra were initially absent from the development environment and were
installed; the affected checks pass. The first compiler UI run omitted PCFC11_PATH;
all 13 skipped cases were rerun with the compiler and passed.

An initial numerical matrix embedded thousands of constants, generating a 2-MB
C function whose GCC optimization exceeded the 180-second test deadline. The
maintained matrix now generates deterministic test inputs in ordinary Runtime
loops and passes all three compiler profiles. The initial source and timeout log
are retained. This does not establish performance for giant literal-generated
functions. The SDK refusal harness initially expected a byte-identical registry;
it now checks the intended behavior: an error row may be added while the prior
working package remains enabled and Ready. Product code did not need changing.

HANDOFF AND WINDOWS REVIEW
Use the 1.3.77 wheel in the Python environment that runs PyCForge. SDK 0.6.3 needs
no update. The pinned PCFC11 0.2.27 source archive is unchanged; this work changes
Crucible and compiler integration UI, not PCFC11 parser/optimizer internals.

On Windows, open Compile and confirm that the preparation cover remains compact,
cancels normally and no longer produces the reported repeated geometry warning.
In Runtime mode try:
    *import numpy as np
    def main():
        values = np.array([8, 4], dtype="float64")
        alias = values
        values /= 2
        print(np.true_divide(values, 2).tolist(), alias.tolist())
        return 0
Expected: [2.0, 1.0] [4.0, 2.0]
The standalone fixture is fixtures/import_maturity/numpy-division.py.

Run test-windows-gc.ps1 using WINDOWS-GC-TESTING.md for the 80-check native Windows
GC review. Linux runs and offscreen Qt checks do not establish native Windows
compiler or geometry qualification. PCFC11 remains a development compiler;
this report does not claim complete C11 conformance or universal NumPy support.

Evidence: evidence/numpy_division_1_3_77; framework directive revision 0.9.
The companion release report records final build checks, byte sizes and SHA256.


FINAL INSTALLED WHEEL
All 997 application payload files match the installed final wheel byte for byte.
All 142 loaded product modules originate in that installed environment. The exact
Windows-review example passes GCC UBSan and PCFC11 O0/O1 from the installed wheel;
unsupported true_divide keywords produce source-mapped PYC4706 and no partial C.
All 553 SDK payload files match the unchanged supplied SDK 0.6.3 wheel.

BUILD-AUDIT CORRECTIONS
The first distribution directory contained an empty build-temporary directory;
it was moved out. The next source audit correctly detected a build log changing
while included in the sdist. Final source generation writes logs outside the
frozen source tree. An installed-payload check made before the final reinstall
identified the old Help version label; the final installed check above passes.
These failed checks and successful follow-ups are retained as evidence.
