t/integration/coverage.t fails with Test2-Plugin-Cover-0.000028

[ppisar]

After upgrading Test2-Plugin-Cover from 0.000027 to 0.000028 t/integration/coverage.t fails like this:

$ perl -It/integration/coverage/lib t/integration/coverage.t
# Seeded srand with seed '20260720' from local date.
ok 1 - yath test -It/integration/coverage/lib t/integration/coverage --ext=tx --cover-wr[...]GnWUJ.json -v {
    ok 1 - Exit Value Check
    1..1
}
not ok 2 - Got predicted coverage data
# Failed test 'Got predicted coverage data'
# at t/integration/coverage.t line 73.
# +---------------------------------------------------+----------------------+----+--------+
# | PATH                                              | GOT                  | OP | CHECK  |
# +---------------------------------------------------+----------------------+----+--------+
# | {files}{Cx.pm}{c}{t/integration/coverage/a.tx}[0] | HASH(0x556a7fcdf0b8) | eq | *      |
# | {files}{Cx.pm}{c}{t/integration/coverage/a.tx}[1] | *                    |    | <HASH> |
# +---------------------------------------------------+----------------------+----+--------+

[ppisar]

The line number is 1 higher because I add a shebang to the test files.

There is already the same report on cpantesters https://www.cpantesters.org/cpan/report/332a1ad4-81d0-11f1-9142-db1ab00b9280:

[  FAIL  ]  job  8  + Got predicted coverage data
[  DEBUG ]  job  8    t/integration/coverage.t line 72
(  DIAG  )  job  8    +-----------------------------+-----------------------------+----+--------+
(  DIAG  )  job  8    | PATH                        | GOT                         | OP | CHECK  |
(  DIAG  )  job  8    +-----------------------------+-----------------------------+----+--------+
(  DIAG  )  job  8    | {files}{Cx.pm}{c}{t/integra | HASH(0x55c5c678c070)        | eq | *      |
(  DIAG  )  job  8    | tion/coverage/a.tx}[0]      |                             |    |        |
(  DIAG  )  job  8    |                             |                             |    |        |
(  DIAG  )  job  8    | {files}{Cx.pm}{c}{t/integra | *                           |    | <HASH> |
(  DIAG  )  job  8    | tion/coverage/a.tx}[1]      |                             |    |        |
(  DIAG  )  job  8    +-----------------------------+-----------------------------+----+--------+

[ppisar]

It can be reduced to "yath test --cover-write=/tmp/log.json -I t/integration/coverage/lib t/integration/coverage/a.tx" command.
Old Test2-Plugin-Cover returns:

    "Cx.pm": {
      "*": {
        "t/integration/coverage/a.tx": [
          "*"
        ]
      },
      "c": {
        "t/integration/coverage/a.tx": [
          "*",
          {
            "subtest": "c"
          }
        ]
      }
    }

New Test2-Plugin-Cover changes order of the elements in "Cx.pm"/"c"/"t/integration/coverage/a.tx" array:

    "Cx.pm": {
      "*": {
        "t/integration/coverage/a.tx": [
          "*"
        ]
      },
      "c": {
        "t/integration/coverage/a.tx": [
          {
            "subtest": "c"
          },
          "*"
        ]
      }
    },

Is the order significant? I don't think so. But for the sake of tests something should sort it.