shouldCascadeToPostiz (postiz-cascade-policy.ts)

Policy for when a PATCH /posts/:id edit may cascade to the third-party publisher (Postiz): delete the existing external post(s) and re-publish. The hard rule: NEVER cascade a post that has already been published. Its content is live on the platform — re-publishing would duplicate

// Policy for when a PATCH /posts/:id edit may cascade to the third-party
// publisher (Postiz): delete the existing external post(s) and re-publish.
//
// The hard rule: NEVER cascade a post that has already been published. Its
// content is live on the platform — re-publishing would duplicate it and a
// delete can't unpublish it. This is what bit us when a background media
// cleanup (orphan-ref healing) re-touched 3-week-old, already-published
// Mother's Day posts and they got re-recorded/re-attempted on Postiz.
//
// Posts that have NOT been published yet (draft / scheduled) DO still cascade,
// so legitimate corrections still propagate — e.g. a scheduled post missing
// an image gets fixed and re-queued on Postiz before it goes out.

export type CascadeDecision = { cascade: boolean;

... (truncated -- full source via MCP)