Invio v1.0.0.1.48.3
Invio v1.0.0.1.48.3
Scope
End-to-End CI/CD & Release Pipeline Forensic Audit and Stabilization over the owner-frozen Invio_v1.0.0.1.48.02_CL_FIx_Baseline.zip baseline.
GitHub failure evidence
GitHub Actions run 31516505105 checked out commit 5ff60fbcc82c0bfbdae7e0aa62a9912beb360069. Both test and windows-build reached the full regression audit. The Linux Qt dependency step succeeded and the four real PySide6 QApplication / QMessageBox.exec() / QTimer popup lifecycle tests passed on both operating systems. Both jobs then failed with the same repository-contract result: 443 tests executed, with 17 errors and 4 failures, all under tests/test_repository_contracts.py.
Root cause
project/ is intentionally private and Git-ignored. The previous v1.48.02 CI correction partially unignored /project/ plus four project/research/ROOT_CAUSE_VERIFICATION_*.md files. A public Actions checkout therefore contained a partial project/ directory. Existing historical repository-contract tests deliberately use if project_root.is_dir(): to run private-record assertions only in a full private baseline. Materializing a partial tree made those tests enter the private branch even though most required planning/specification/research files were absent, causing the 21 failures.
This is a regression of the public/private test boundary already established in v1.0.0.1.26; it is not an application runtime defect.
Correction
- restore
/project/to fully private/Git-ignored with no public-file exceptions; - keep the existing historical repository tests conditional on complete private-baseline presence;
- change only the four newer v1.47.0/v1.48.0/v1.48.01/v1.48.02 private-record reads to the same conditional pattern;
- retain the existing compatibility test name while asserting that no
project/unignore exception is present; - preserve the Linux Qt offscreen dependency installation and real PySide6 interaction tests;
- preserve the existing wheel, Nuitka OneDir, compiled keyring, WiX MSI, MSI lifecycle smoke, checksum, artifact upload and exact-tag release workflow.
Version mapping
- Application:
1.0.0.1.48.3 - Tag:
v1.0.0.1.48.3 - PE:
1.0.1.4803 - MSI:
1.1.4803 - Python wheel:
1.0.0.1.48.3
Frozen behavior
No UI layout/color/popup semantic, runtime, Task state-machine, WorkerManager, provider, storage/schema, customer/invoice, Settings, dependency or business-logic change is included.
A new post-push GitHub Actions run remains required to certify the Windows Nuitka/MSI/artifact stages remotely; this local candidate does not fabricate that remote result.