[JFWooten4]

Decision

Remove formal public release versioning from PDF Magic Opener. Identify source checkouts by Git commit SHA rather than SemVer releases, tags, or newest-stable-version support promises.

Changes

• Replace the version-based support matrix in SECURITY.md with a current-source maintenance policy. Older source snapshots are unsupported without promising numbered releases.
• Make docs/release-versioning.md describe only technical build metadata required by macOS and WebExtension packaging; no public release numbering, version bump cadence, or GitHub Releases channel is planned.
• Adjust the development release notes, application update policy, and docs index to direct readers to trusted source checkouts and preserve browser/ClamAV safety boundaries.
• Update required CI policy tests to verify build metadata remains valid, commit-based source support, private vulnerability reporting, and uncompromised scanner protections.

No runtime, scanner, extension permission, settings, distribution workflow, or signed binary behavior changes. The existing release gate is left fail-closed.

Verification

The branch is based on verified main 6e65a9f. It contains nonempty committed changes and preserves required packaging version fields. GitHub CI should complete before merging.

[JFWooten4]

CI follow-up: The initial release-gating regression identified two documentation assertions that still expected the legacy policy language. The branch now preserves the release gate’s NOT RELEASE READY and prerelease guard wording and explicitly labels the old source-only workflow as unused, without reintroducing formal versioning or a release channel. The existing PR description is unchanged. Source-level version-field consistency and policy checks pass; GitHub Actions are running on the updated head.