Publishing reviewed course changes in one transaction

Give the proposed course its own records#

CourseRevisionWorkflowService finds or creates an editable copy of an approved course. Creation locks the course inside a transaction and checks again for an existing revision before creating separate course and content records. Edits can then continue without changing the approved lessons.

The administrator controller chooses approve or reject; the service performs the writes. On publication, it locks the course and revision, verifies their relationship, copies the explicit field list, synchronizes assignments and rebuilds chapters, lessons and announcements. Rejection keeps the proposed content out of the approved course.

The service removes the consumed revision before returning the updated course. Learner notifications are invoked after the publication transaction returns.

Atomic publication still changes lesson identity#

Tests check that editing leaves the approved course unchanged, approval transfers content and removes the draft, and rejection preserves the approved content and review decision. Notification fakes check which messages should be queued, not whether they were delivered.

The current publication path deletes and recreates chapter and lesson rows. A transaction keeps those writes together, but it doesn't preserve references to the old IDs. The inspected tests don't establish that learner progress survives those replacements; that needs separate relationship handling and migration coverage.