Use the public issue forms for support and corrections. Report suspected vulnerabilities only through private vulnerability reporting.
What to include
- Chronologix version and build number;
- macOS version and Apple silicon model family;
- the source and capability label shown for the affected item;
- the exact user-facing error or result state;
- whether retry or Check Again changed the result;
- an aggregate diagnostic export only after reviewing its complete preview.
What not to include
Do not send passwords, API keys, notarization credentials, authentication cookies, signed private URLs, raw receipt contents, a complete application inventory, home-directory paths, or unrelated logs.
Common boundaries
Update All is unavailable
The current view has no fresh row with an approved in-app executor. Confirmed newer versions may still show Options; Check Again refreshes evidence without changing installed software.
An installed app does not appear in Available updates
The app may be current, unknown, stale, or not checked by an enabled source. Review its source status or check again. A confirmed newer version appears as Update or Options; inventory alone does not.
Options does not offer Force Install
Force is not a universal safe operation. When no verified in-app executor exists, Chronologix keeps the newer version visible with evidence review and Check Again; it does not open another app, updater, Store page, Settings surface, browser, or Terminal. A future update or reinstall action must earn its own source-specific verification and recovery contract.
A direct update is blocked
Read the plan’s Guard result. The app may be open, the destination may not be writable, evidence may have changed, space may be insufficient, or recovery state may need attention. Nothing should be downloaded or replaced while the Guard is blocked.
Correction requests
Coverage and competitor corrections need the affected row, the claimed value, a current official source, and the date observed. Submit them through the public issue forms.