When one opens a checkpoint cursor, they can either indicate the name of the checkpoint or leave the name blank so it tries to open on the latest internal WiredTiger checkpoint.

An internal WiredTiger checkpoint has the specific name "WiredTigerCheckpoint" but a suffix made of a dot and a number is appended every time there is a new internal checkpoint, i.e "WiredTigerCheckpoint.6".

What if one tries to open a checkpoint cursor and gives the name "WiredTigerCheckpoint.x", how do we want to treat that?
The current checkpoint cursor code seems to treat it as an unnamed checkpoint but does not see it as an internal checkpoint name either:

        /*
         * Test for the internal checkpoint name (WiredTigerCheckpoint). Note: must_resolve is true
         * in a subset of the cases where is_unnamed_ckpt is true.
         */
        must_resolve = WT_STRING_MATCH(WT_CHECKPOINT, checkpoint_name, strlen(checkpoint_name));
        is_unnamed_ckpt = strlen(checkpoint_name) >= strlen(WT_CHECKPOINT) &&
          WT_PREFIX_MATCH(checkpoint_name, WT_CHECKPOINT);

must_resolve is 0 and is_unnamed_ckpt is 1.

The solution to this issue would be to not allow the use of reserved names when dealing with checkpoints cursors by returning EINVAL.