v2.0.1: Central admin changelog workflow

Central changelog workflow

WordPress now serves published changelogs and provides a read-only viewer. Editing, drafts, release stages, history, and AI access live in the PythonAndVBA admin dashboard.

• Search published products, preview releases, and copy shortcodes or public API URLs.
• Remove WordPress editing, deletion, and outbound changelog-to-GitHub sync. Stale write requests receive an explicit error.
• Preserve existing product IDs, stored content, public JSON responses, and shortcode rendering.
• Show missing publishing-bridge and unadopted-product warnings.
• Keep WordPress notices outside the responsive header.

The authenticated changelog-snippets mu-plugin remains required for publishing from the dashboard. No data migration runs during this update. GitHub plugin software updates remain enabled.

Validation: 30 offline plugin checks, separate publishing-protocol tests, and live API/WordPress browser checks.

v1.2.1 — fix the Repository file field

Fixed

• The per-product Repository file field was rendered and read by the server, but never submitted, so typing a file name there had no effect and the product kept pushing to a file named after itself.

v1.2.0 — GitHub sync

Added

• GitHub sync (optional, off by default). Saving a changelog can also commit it to a GitHub repository, so release notes live in version control as well as in WordPress. Settings under Changelog → GitHub sync: repository, branch, directory, token and an optional file header whose {id} and {name} are replaced.
• Per-product Repository file field, plus Match products to existing files to wire up an already-populated repository by reading the ID out of each file's header.
• Prefer define('SCL_GITHUB_TOKEN', '...') in wp-config.php so the token never reaches the database, and therefore never a backup or a staging clone.

Fixed

• Changelog text is now stored exactly as typed. The save ran it through wp_kses_post(), which quietly damaged content: a bare < became < and rendered as the literal text <, and anything tag-shaped was deleted outright, so an entry describing <think> tags silently lost the word and read "hide tags". A changelog is plain text and everything that reads it escapes on output, so nothing was being protected.
• Backslashes survive a save. update_post_meta() unslashes, so a release note mentioning a Windows path or a regex escape used to lose them.
• Line endings are normalised, so a Windows browser's CRLF no longer makes an unchanged changelog look edited.