PyCForge SDK 0.6.3 — engine-produced package identity
2026-10-31

Baseline: pycforge_sdk-0.6.2.tar.gz. Preserve all baseline source paths, approved
README banner, provenance hashes and historical records. Nothing was published.

The SDK now reports package_format from the actual engine-produced archive,
before replacing the output file. Conversion semantics and admission remain in
the selected engine. This supports new reviewed families without SDK library-name
switches. PyCForge 1.3.76 supplies expanded NumPy operations, JSON/independent
records starters, four-field forms, exact limits and offline Help. The SDK GUI
and its copied visual payload are unchanged.

Qualification used installed wheels in separate environments. All 130 headless
and 28 desktop cases pass after the recorded follow-ups. Historical capability
browsing uses actual engine 1.3.60; legacy project migration uses 1.3.61; preceding
engine/package checks use 1.3.75. The headless SDK has no engine, NumPy or Qt.
The engine has no SDK installed. Module-origin records confirm installed use.

Array and independent vector, JSON and independent records projects verify their
native fixtures, build byte-identical packages, register through the engine, and
refuse stale Help/evidence without replacing previous outputs. Engine-only
compatible additions render without SDK edits; incompatible workbench metadata
preserves the validated cache. Offline browsing cannot approve native execution.

The unchanged 0.6.2 SDK can discover/verify/build/register the new value family,
but its build result reports scalar-package/0.2 despite a correct value archive.
0.6.3 fixes the report. Reverify existing projects after this SDK update.

Native qualification: Linux x86-64, GCC. Desktop: Linux Qt offscreen. Native
Windows testing is not claimed; the SDK's native verification profile remains
Linux/GNU. Desktop editing/discovery is separate from native fixture execution.

The final distribution audit checks metadata/README consistency, wheel RECORD,
all baseline source paths, shared visual hashes and both installed SDK payloads.
Archive sizes and hashes are in the companion release report.

Pre-upload README review, 2026-10-31: removed one blank line that separated the
structured-value row from the capabilities table. The approved banner, prose,
examples and version are unchanged. The rendered table now has all three families.
The rebuilt 0.6.3 wheel/source pair supersedes the earlier pair; updated hashes
are in the companion release report. No SDK runtime or GUI code changed.
