Tracks ought to be synced from the problem spec, unless there is a strong reason not to do so. Changes generally ought to go to the problem spec then synced to tracks. Changed generally ought to first be proposed, discussed and approved on the forum before PRs are created.
The docs immediately point out which one is the row and which is the column so I think it’s cleared up fairly quickly. Going row, column intuitively tracks with how you’d access a multi-dimensional array since first you access the row you want and then you access the element at the column index you want.
This is not a general issue for other languages. I’m calling this is Prolog specific because other languages are consistent with the instruction going (row, column).
But, only for Prolog test cases, it decides to use (column, row).
Either
(1) the instruction for Prolog should be updated
(2) the test cases for Prolog should be updated.
It’s up to the Prolog maintainer, but updating the test cases would likely be the better action here since we’re discussing a track-specific implementation detail.