Resequence v1.4.2 release prep to the final main commit

[Reedtrullz]

The signed-release-tag gate requires the tag commit to be a release-prep commit whose diff vs its exact first parent is only the four release files (manifest, bundle version, changelog, release-status) with the version advancing. PR #27's prep merged before the hardening PR, so main's tip cannot satisfy that gate.

This PR reverts the v1.4.2 prep back to the v1.4.1 candidate state (Info.plist 1.4.1 build 9, manifest candidate v1.4.1). A follow-up prep PR (merged last) will re-advance to v1.4.2 build 10 as a valid tag target. No source or tooling changes; only the four release files.

Verification

• The revert is a pure inverse of PR Prepare v1.4.2 release and record v1.4.1 retirement #27's four-file diff (CHANGELOG conflict resolved by removing the 1.4.2 section; it returns in the final prep PR).
• git diff 78440b4..HEAD --stat: 4 files, 11 insertions, 29 deletions.
• Manifest continuity, metadata, and release-fact gates pass locally.

Non-claims

• No tag, push, or release mutation. This is a temporary internal state; the final main content after the follow-up prep is identical to today's intended 1.4.2 release state.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Reedtrullz]

Superseded: the manifest continuity gate forbids the candidate moving backward, so v1.4.2 cannot be resequenced; the release advances to v1.4.3 instead.