Define editorial safety acceptance criteria for publishing workflows

[khoinguyenpham04]

This Roadmap discussion mirrors #1683: Define editorial safety acceptance criteria for publishing workflows.

Use this discussion to upvote the roadmap item and discuss priority, use cases, and product feedback. Keep implementation tracking, reproduction details, and PR-specific feedback on the source issue.

• Source issue: #1683
• Status: Open
• Labels: None
• Original author: ascorbic

Original Issue

Goal

Define and verify the core editorial safety contract for 1.0. Editors and agents should be able to trust the publish path with real content.

Scope

Cover draft, publish, unpublish, schedule, unschedule, discard draft, restore, trash, and permanent-delete flows.

Acceptance criteria

• Each status transition has documented expected behavior.
• Permission requirements are explicit for each transition.
• Manual save, autosave, and publish do not race each other.
• Revisions are created or updated predictably.
• Existing tests cover the critical transition paths.