2026-10-14 · CPH Assistant Access
CPH Assistant Access allows an authorized image workflow to replace the featured image on an already published WordPress article, while retaining the article's publication state and existing controls.
What changed
- Remove the published-status refusal from the dedicated attach-images workflow for a changed landscape image.
- Preserve scoped authentication, revision checks, operation receipts, local attachment validation, and the workflow lock.
- Keep draft publication holds, scheduled-post restrictions, and general article editing restrictions unchanged.
- Update the agent guide to distinguish image repair from article publication and document uploading replacement media before attaching it.
Verification
- The workflow regression suite passed 826 assertions, including published-image replacement, unchanged retries, revision conflicts, operation receipts, and preserved article state.
- Settings tests, PHP syntax checks, and patch whitespace checks passed.
- An independent source review found no blocking defect in the focused workflow change. Live rollout and rendered image verification remain pending at publication of these notes.
Rollout
Pending controlled rollout. These notes precede distribution; they do not establish installation or a successful live image replacement. A dated rollout receipt will be appended after verification.
Updating
- This maintenance overlay updates only the Assistant Access entry point and image workflow files. Existing publishing-policy and settings components remain in place.
- Back up the two affected files, verify the existing baseline, then verify the deployed hashes and capabilities. Retain the backup for a targeted rollback.
- Clients must use the dedicated attach-images route with the current article revision and an intentional client request ID. Upload new media without a published article parent before attaching it.
- Developed by Matthew X Murphy, MatthewxMurphy.com; software portfolio at BuiltNotBegged.com. Release owner: CreatorPublishingHub.com.
Scope and limitations
- This change does not generate or replace existing undersized images automatically and does not republish or reshare articles.
- Scheduled articles remain outside this focused repair. General post editing and media-parent restrictions remain unchanged.
- Changing an image changes the evidence revision; prior reviews are retained as history but must not be represented as a review of the replacement image.
- External WordPress writers can still race with an assistant operation. Featured-image and companion-image writes are not a single database transaction; clients must reconcile uncertain results using saved operation receipts.
Rollout receipt — October 14, 2026 (America/Chicago)
Installed and verified on Creator Publishing Hub, Creator Newsdesk, The Factology Daily, The Daily Smirk, Love Lies Abroad, and Credit Repair Choices. Each site loaded Assistant Access 2026.10.14.001 and returned successful authenticated capability, workflow and guide responses.
Only the two documented Assistant Access files changed. Other checked runtime files, publisher versions and protected settings were preserved, including the existing owner publishing policies. Exact file backups and private deployment receipts were retained.
Live image-swap verification remains pending. No replacement was attached: the bounded candidate review found no artwork that passed the current image requirements. Installation and API contract verification do not establish a successful changed-image operation. Existing undersized-image and missing-image backfills remain open.
The archive retains the original pre-rollout notes and manifest as its immutable build record; this appended receipt records later runtime verification. Archive SHA-256: bbd9b4a83886b69428dd658535974b9172fa4bbee6f246d3bc4ac0205f918a30.
Verification follow-up and superseding release
The first live image association test succeeded, but exposed a legacy thumbnail hook that wrote social queue metadata. The original image was restored and only the two test-created legacy records were removed. This was a failed preservation check, not a fully verified repair. The callback itself did not send an external request; queue metadata does not prove delivery.
Version 2026.10.14.003 supersedes this build with both the scoped legacy-hook guard and target-article SEO refresh. The latest receipt records the successful live preservation and rendered image checks. Earlier notes, source and artifacts remain retained.
Join the conversation
Load Facebook comments to read and reply using your Facebook account.