Invio v1.0.0.1.50.1

Invio v1.0.0.1.50.1 — Phase 1–4 Release-Readiness Certification Correction

Parent baseline

• Official parent: Invio v1.0.0.1.50.
• Parent Git commit: b87b412413f8788656c89b3b97a487d855d10d5f.
• Owner-uploaded Final Baseline SHA-256: 80825b8c2c780f5ecf3510e797c76f6cd5a018c14cde6924c32c6746c2f8bde5.

Confirmed acceptance evidence

GitHub Actions run 32109507918 executed the exact parent commit and completed successfully. Linux tests passed. Native Windows executed 642/642 tests PASS, including the Phase-4 Dynamic Tags V1 suite and current schema-v7 migration contracts. Wheel/P14 validation, native PySide6/keyring/resource smoke, Nuitka OneDir startup, protected-credential and Windows-native-TLS smokes, WiX MSI build/install/run/uninstall, P14 release-payload audit, and artifact upload all passed.

Corrections in this hotfix

• Synchronize current documentation/status from “candidate / CI pending” to the now-verified v1.0.0.1.50 acceptance state.
• Remove the tracked trailing whitespace from PATCH_MANIFEST_v1.0.0.1.50.md.
• Advance release identity only to application/wheel 1.0.0.1.50.1, PE 1.0.1.5001, MSI 1.1.5001, future tag v1.0.0.1.50.1.
• Add release-readiness verification/freeze records and current release contract coverage.

Frozen behavior

No production behavior is changed. Phase-1 native TLS trust and fail-closed certificate verification, Phase-2 provider fatal-limit circuit breaker, Phase-3 timeout/retry/delay/rate controls, Phase-4 Dynamic Tags V1, schema v7, provider/Odoo contracts, Task state machine, WorkerManager/QThread architecture, delivery ledger, CredentialStore, OAuth/Easy Onboarding, ProviderManager/IVX, application pages and unrelated UI/UX remain unchanged.

The Git tag is not created by this source correction. Exact v1.0.0.1.50.1 post-push non-tag CI remains the final gate before owner tag/release publication.