pycforge 1.3.44__tar.gz → 1.3.45__tar.gz

{pycforge-1.3.44 → pycforge-1.3.45}/MANIFEST.in

@@ -97,6 +97,8 @@ include PyCForge-1.3.41-Verification.txt
 include PyCForge-1.3.42-Verification.txt
 include PyCForge-1.3.43-Verification.txt
 include PyCForge-1.3.44-Verification.txt
+include PyCForge-1.3.45-Verification.txt
+include PyCForge-README-Guidelines.txt
 
 # Distribute only images needed by the application, never review screenshots
 # or design masters. Keep these exclusions after all graft/include directives.

{pycforge-1.3.44/pycforge.egg-info → pycforge-1.3.45}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pycforge
-Version: 1.3.44
+Version: 1.3.45
 Summary: Deterministic bounded Python-to-C source transpiler
 License-Expression: GPL-3.0-only
 Project-URL: Homepage, https://pypi.org/project/pycforge/
@@ -30,7 +30,7 @@ Dynamic: license-file
 
 <img src="https://res.cloudinary.com/vppzdwxg/image/upload/v1792314783/exec-76eda399-3547-4803-9896-4d57a7dd45cf.png" alt="PyCForge" width="320">
 
-# PyCForge v1.3.44
+# PyCForge v1.3.45
 
 PyCForge is a Python-to-C source transpiler and PySide6 desktop IDE. Edit Python, convert supported programs into readable C11, inspect the generated code, and compile with an optional native C toolchain—all from one workspace. A command-line interface and Python API bring the same conversion capabilities to scripts and other development tools.
 

pycforge-1.3.45/PyCForge-1.3.45-Verification.txt

@@ -0,0 +1,77 @@
+PyCForge 1.3.45 — Module saving and project restoration
+Prepared 2026-10-19 for CC's own PyPI upload.
+
+CORRECTIONS
+- Saving a newly added module as ofr_42.py replaces the default module_N /
+  module_N.py identity with ofr_42 / ofr_42.py throughout the Source Bundle.
+  Filename-derived identities follow Save As; custom logical aliases remain.
+  Imports are not rewritten. Identity changes invalidate previous generated C.
+- New modules in an open project default to its working folder instead of an
+  unrelated previously used directory. Save As for an outside module also
+  suggests the project's working folder. The original file is preserved.
+- Matching placeholder identities retained by older projects are repaired by
+  another save. Duplicate identities and linked-path collisions are rejected
+  before file replacement. Cancelled and failed saves retain prior metadata;
+  newer source edits remain dirty after an asynchronous save.
+- A save completed before the first background revision was ready could
+  encounter a missing-revision exception. Pending revisions now remain
+  unauthenticated until the index is ready, while file saves complete normally.
+- Startup keeps a successfully read project archive and its checkpoint history
+  connected when a restored module is outside the working folder. The report
+  identifies the actual filename, required folder and Save Python As action.
+  Correcting the location and saving retains the original checkpoints and the
+  archive's external-change protection. Missing/corrupt-file notices remain.
+
+EXISTING AFFECTED FILES
+For an already affected ofr_42.py, install 1.3.45, select its tab, and use
+Save Python As to save it inside the project's working folder. Then Save
+Project and restart. The original outside file is not deleted. A legitimate
+startup notice can remain until this one-time location correction is made.
+
+README AND VERSION
+The README differs from the approved 1.3.44 README only in the heading:
+# PyCForge v1.3.44 -> # PyCForge v1.3.45
+Its prose, structure, conversion table, historical bug entries, four image
+URLs, banner widths, screenshot labels, and Crucible placement are unchanged.
+The README renderer check passes with exactly four images and no additional
+navigation links. The release version is 1.3.45; historical evidence keeps its
+original labels. The README guideline is included in the source archive.
+Two installed HTML Help pages explain the corrected save/recovery workflow.
+All converter implementation files are byte-identical to the 1.3.44 baseline.
+Runtime dependencies and the one-wheel installation remain unchanged.
+
+VALIDATION
+219 distinct tests and 477 subtests passed in completed isolated test groups:
+- 25 new identity, save, project and startup/recovery regressions.
+- 31 existing Save All / asynchronous-save / exit cases.
+- 62 existing project archive, project UI, checkpoint and restore cases.
+- 21 startup recovery and fresh-process normal-startup cases.
+- 14 controller tests with 4 subtests.
+- 15 workspace UI tests.
+- 51 release, documentation, C-export and revision tests with 473 subtests.
+The final history-connection change was verified by rerunning its affected
+35 project and module-workflow tests; repeated cases are not counted twice.
+
+The initial combined workflow run also completed successfully: 167 tests and
+4 subtests passed. Independent isolated runs verified the same cases again;
+repeated cases are not counted twice. Logs are retained under
+evidence/module_save_1_3_45.
+
+Separate-process create/restart probes pass both when the Python file is saved
+before updating the project bundle and after the bundle is updated. They check
+ofr_42 / ofr_42.py, both restored files, active selection, project association,
+and the absence of a startup report. The probe is included in tests/fixtures.
+
+Verification used Linux, Python 3.12 and Qt offscreen. A native Windows or
+macOS run was not performed. The full repository suite was not run, and no
+PyPI upload was performed. Finished-package checks and SHA256 values are
+appended to the accompanying handoff report after building the archives.
+
+WINDOWS CHECK
+1. Open a project, add a module, and save it as ofr_42.py in the suggested
+   working folder. Confirm the Source Bundle ID and LOGICAL fields match.
+2. Save Project, close PyCForge, and reopen. Confirm the module is present and
+   no startup report appears for this valid saved module.
+3. For a module already saved outside the working folder, use Save Python As
+   to correct its location, Save Project, and confirm existing checkpoints
+   remain available after restart.

pycforge-1.3.45/PyCForge-README-Guidelines.txt

@@ -0,0 +1,98 @@
+PyCForge README and Release Handoff Guidelines
+Established by CC, 2026-10-19
+
+Activation: Prepared for use after PyCForge v1.3.44 is published.
+Scope: All future PyCForge README edits and release handoffs.
+Baseline: The corrected README in the verified v1.3.44 wheel and source archive.
+
+1. Purpose and structure
+
+Keep the README a concise, professional introduction to PyCForge's working
+features, installation, usage, supported conversion scope and practical limits.
+Preserve the approved section order, feature emphasis, examples and contact
+information. Make focused updates when documented capabilities or usage change.
+Do not redesign, reorganize or broadly rewrite it without CC's instruction.
+PyCForge is distributed through PyPI; it is not a GitHub project. Do not introduce
+repository links, GitHub workflows or instructions that assume GitHub hosting.
+
+2. Content boundaries
+
+Do not place development cycle status, phase or milestone reports, internal
+roadmaps, pending-work lists, test-run counts or release-engineering logs in
+the README. Keep those in separate maintenance and verification documents.
+Practical supported limits and accurately described engineering methods are
+appropriate when they help users understand the product. Do not make unsupported
+maturity, correctness, compliance or feature claims.
+
+Keep the Conversion bug tracker. Record confirmed issues, concise corrections
+and the actual version containing each fix. Do not change historical fix versions
+when advancing the package version. The tracker is product information, not a
+development progress report.
+
+Maintain HTML Help as the detailed usage and coding reference. Keep its examples,
+limits and diagnostics current during conversion work. Do not use HTML Help for
+routine development cycle status.
+
+3. Exactly four links
+
+The README must contain exactly four external URLs, each used once as an image:
+
+1) PyCForge banner at the top, display width 320:
+https://res.cloudinary.com/vppzdwxg/image/upload/v1792314783/exec-76eda399-3547-4803-9896-4d57a7dd45cf.png
+
+2) Existing workspace screenshot, retaining its accurate v1.3.39 label:
+https://res.cloudinary.com/vppzdwxg/image/upload/v1792313873/pycforge-1.3.39-main.png
+
+3) Existing Ting screenshot, retaining its accurate v1.3.39 label:
+https://res.cloudinary.com/vppzdwxg/image/upload/v1792313993/pycforge-1.3.39-ting-evidence.png
+
+4) Crucible banner directly below the Conversion bug tracker table, before
+the engine description and contact line, display width 640:
+https://res.cloudinary.com/vppzdwxg/image/upload/v1792420349/exec-7284d6da-a28b-4732-8980-a015c99067c6.png
+
+Retain Crucible's subtitle: a py to c conversion engine.
+Add no other image, navigation, badge, GitHub, documentation, mailto or relative
+file links. Keep the contact email as plain code text. Renderer-generated heading
+anchors are not authored navigation links. Change an approved asset only when
+CC requests or authorizes that change.
+
+4. Version and artifact checks
+
+The README heading must match the release version in pyproject.toml, the imported
+package, wheel METADATA, source PKG-INFO and both distribution filenames.
+Installed workspace, startup, About and Help footer versions must also agree.
+Historical screenshot labels and bug-fix versions retain their true identities.
+
+Before handing off a release:
+- Review the README diff against the approved baseline for scope and prose.
+- Run the README renderer check and confirm the exact four images and placement.
+- Inspect the finished wheel's METADATA and the source archive's README.md and
+  PKG-INFO. Their README bodies must match the approved source README byte for byte.
+- Run strict twine and public distribution checks on the exact final pair.
+- Record each final filename, byte size and SHA256; include those hashes in the
+  accompanying verification report and identify the final download pair clearly.
+
+5. Release handoff
+
+Keep one authoritative wheel/source pair for each release handoff. Preserve
+review builds separately. If an unpublished version is rebuilt, explicitly state
+that the new pair supersedes earlier downloads with the same filenames, provide
+the new hashes, and make the current pair easy to distinguish.
+
+CC performs the PyPI upload. Once a version is published, corrections require
+an appropriately authorized new release version; do not suggest replacing or
+deleting published files to reuse their names. A same-version instruction does
+not authorize silently advancing the version.
+
+When verifying publication, obtain current PyPI release metadata and compare
+the published filenames and SHA256 values with the final handoff. Check the
+published description separately. Investigate a mismatch using actual metadata
+and archive contents before attributing it to caching or user error.
+
+6. Ongoing maintenance
+
+Consult this guideline before changing README.md or preparing release files.
+Carry it into the next source-maintenance workspace and include it with future
+source releases; do not rebuild the approved v1.3.44 upload files to add it.
+Keep the README/distribution verification tools aligned with these requirements.
+CC's later explicit instructions govern changes to this guideline.

{pycforge-1.3.44 → pycforge-1.3.45}/README.md

@@ -1,6 +1,6 @@
 <img src="https://res.cloudinary.com/vppzdwxg/image/upload/v1792314783/exec-76eda399-3547-4803-9896-4d57a7dd45cf.png" alt="PyCForge" width="320">
 
-# PyCForge v1.3.44
+# PyCForge v1.3.45
 
 PyCForge is a Python-to-C source transpiler and PySide6 desktop IDE. Edit Python, convert supported programs into readable C11, inspect the generated code, and compile with an optional native C toolchain—all from one workspace. A command-line interface and Python API bring the same conversion capabilities to scripts and other development tools.
 

pycforge-1.3.45/evidence/module_save_1_3_45/application_changes.json

@@ -0,0 +1,16 @@
+{
+  "base": "1.3.44",
+  "release": "1.3.45",
+  "changed_files": [
+    "pycforge/_version.py",
+    "pycforge/ide/controller.py",
+    "pycforge/ide/controller_io.py",
+    "pycforge/ide/project_model.py",
+    "pycforge/ide/qt_project.py",
+    "pycforge/ide/qt_python_save.py",
+    "pycforge/ide/resources/help/projects.html",
+    "pycforge/ide/resources/help/workspace.html"
+  ],
+  "converter_unchanged": true,
+  "readme_only_version_heading": true
+}