2026-10-03 · Creator Publishing Hub publishing plugin, Taylor Assistant Access
The operation journal automatically archives older finished operations when its active storage fills, so ready image attachments can continue while their original receipts and safe retry behavior remain available.
What changed
- When the active journal reaches its 500-operation limit, archive up to 100 of the oldest terminal operations before accepting new work. Keep pending and uncertain operations in the active journal.
- Retain archived operation receipts without expiry and consult them for status lookup and idempotent replay. Reusing a request identifier returns its saved outcome instead of uploading an image, changing an article or publishing twice.
- Preserve payload-conflict checks, revision checks, publication holds, existing article-image protections and the separate Story workflow.
- Keep the publishing plugin and Taylor extension on one calendar release across the six managed publishing sites.
Verification
- All 805 checks across the eight assistant regression suites passed, along with the settings suite and PHP syntax checks for all nine assistant runtime files. Coverage includes archived receipt lookup and replay, changed-payload and credential conflicts, retained unresolved operations, malformed archives, interrupted archive writes and repeated archival cycles.
- Before source edits, all 11 installed publishing and assistant runtime files on each of the six managed sites matched the previous release source exactly. All six sites reported publishing and assistant version 2026.10.2.02.
- Live Creator Newsdesk recovery archived 100 finished receipts and reduced the active journal from 500 to 401 after a new successful unchanged image-association request. All 500 original receipts remained byte-for-byte intact across active storage and archive; the article and media records were unchanged.
- Archived receipt lookup returned HTTP 200, and a conflicting payload using an archived request identifier returned HTTP 409 without creating a new receipt. Archived entries are not autoloaded.
- All six sites passed deployed file checks, retained their protected settings, returned HTTP 200 homepages and publicly reported matching publishing, assistant and source version 2026.10.3.03. The immutable public update package matched its recorded SHA-256 checksum.
Rollout
Complete across Creator Newsdesk, Creator Publishing Hub, The Factology Daily, Credit Repair Choices, The Daily Smirk and Love Lies Abroad. Publishing and Taylor Assistant Access are aligned at 2026.10.3.03. Newsdesk journal recovery is verified; completion of the waiting image batch remains a separate workflow result.
Updating
- The publishing plugin and Taylor Assistant Access must be updated together through the managed deployment. Taylor Assistant Access is a must-use extension and is not installed by updating the normal publishing plugin alone.
- Back up the affected runtime files and database before rollout, then verify installed versions, file checksums, protected settings and public capability responses. Preserve current content and all active and archived operation receipts.
- Journal maintenance runs when a new operation reaches the active limit. Existing terminal receipts remain accessible from the archive; no manual deletion of the operation journal is required.
Scope and limitations
- Pending or uncertain operations are never archived automatically. If they occupy the journal and too few terminal entries can be archived, new work remains blocked for explicit reconciliation.
- Receipt archiving preserves history and idempotency; it is not authorization to duplicate uploads, republish articles, clear publication holds or bypass editorial and legal checks.
- This release does not establish that every ready image has been attached or every article has been published. Live attachment results require separate operation, article and media readback.
- Archives remain stored in the site database and contribute to its storage use. Database backups must preserve them.
- Once the archive-aware operation runtime is installed, retain it during rollback because live requests may already have archived receipts. Downgrading that runtime requires paused mutations and a verified receipt migration; restoring older code alone can lose historical retry protection.