PyCForge 1.3.10 — Startup recovery verification

Startup and recovery behavior
- Settings access checks Qt status as well as exceptions. A damaged or inaccessible settings store uses session-only preferences and is not reset.
- Invalid presentation, editor, and compiler settings use valid defaults. A presentation schema problem does not discard the saved open-file list.
- Saved files are restored after the workspace appears. Reads run outside the GUI thread; each automatic read has a ten-second deadline. Late reads cannot publish after their deadline.
- Missing, unreadable, invalid UTF-8, NUL-containing, non-regular, and oversized inputs are skipped. Unavailable file paths are retained for a later launch. Readable incomplete Python remains editable.
- Recovery does not write to Python source files. Unsaved editor buffers are not persistent backups; save work before closing.
- A Startup report presents recoverable problems after loading. It has a warning icon, white read-only text box with dark text, selectable details, Copy report, and Close. It remains a separate non-modal window and can update as file restoration completes.
- Both desktop entry points support --safe-mode. This uses defaults and an empty workspace without reading or updating saved settings.
- Fixed numerical kernels compile in memory with checked nopython execution. Old disk caches are neither loaded nor deleted. Warmup therefore occurs on each launch.
- Required resource or dependency failures still prevent launch. The launcher can present a basic error dialog independently of PyCForge icons; console diagnostics remain available when Qt itself cannot be imported.

Validation on Linux, Python 3.12, Qt offscreen, GCC 13.3
- Startup, settings, session, geometry, editor settings, compiler UI, file I/O, numerical kernels, and package contracts: 89 passed, 40 subtests passed.
- Dedicated startup fault-injection and full application event-loop checks: 15 passed. This includes real malformed INI preservation, read-only report and clipboard, missing/access-denied files, malformed values, delayed read rejection, safe start, fallback error dialog, and unusable numeric cache.
- Ting integrity and startup recovery rerun: 32 passed, 33 subtests passed.
- Completion, single inheritance, compiler profiles, and Ting regression run: 68 passed, 12 skipped, 56 subtests passed, with one initial custody-hash assertion. The documented cache-policy adaptation and its actual file hash were added to the vendor provenance; the targeted integrity rerun above passed. Skips concern compilers unavailable in this environment.
- HTML Help: all 21 pages opened and validated; 55 Python examples, 5 API examples, 3 C callers, 2 module examples, and 3 README examples passed. Layouts were rendered for inspection; generated screenshots are excluded from the package.
- Offline conversion corpus: 37 cases, 29 matching Python/native observations and 8 expected unsupported cases, with no unexpected results or observed network attempts. The final run records 335 application source hashes.
- Startup report appearance inspected with the requested warning icon and white text area.
- README preserved byte-for-byte. Existing professional Help structure retained; startup instructions updated in place.

Distribution
- Includes the current wheel and source distribution, original README images, all 495 application icons, licenses, and source evidence.
- Installed-wheel checks and distribution hashes are recorded with the evidence files.
- No native Windows run and no PyPI publication were performed. Windows platform/plugin or OS-level failures that terminate the Python process cannot be recovered by Python exception handling.
- The full historical test suite was not rerun.
