When updating an article and setting its status to “None” under Configure Category Settings during publish, the system behaves correctly. However, when the same article is forked and republished, the status is unexpectedly changed to “Updated” after the publish event—even though the UI indicates “None” prior to publishing.

Expectation -

-> When an article is forked, the new version should inherit the previous status by default.

-> The publish modal should display the current (inherited) status rather than defaulting to “None.”

-> The system should respect the user’s selection during publish and not override it post-publish.

-> Status should only change if the user explicitly selects a different option.