..
This is the expected behavior when error features are created using Arcade-based validation attribute rules.
The lifecycle management of error features is limited to those created using Data Reviewer-based validation attribute rules. Unlike the ArcMap workflow, when an error condition has been resolved the error feature's Phase and Status values are automatically updated when the feature is re-evaluated.
Correct.
The ability to track errors after they have been corrected is only available when using Data Reviewer-based validation attribute rules. Error features created when using Arcade-based validation attribute rules are automatically removed once the error condition is resolved.
That said, I have had Data Reviewer customers indicate that they would like to have all errors (regardless of whether they were created based on an Arcade script or a Data Reviewer check) follow the same life cycle process.
If this is something you'd be interested in seeing in a future release, I would ask that you take a moment and create an idea for this in the Data Reviewer Ideas board.