fix: only push and pull models with meaningful changes

[angeloashmore]

Resolves:

Description

The Prismic API sometimes returns model properties in a different order than the local files. That is not a real change, but pull, push, and status treated it as one. Users saw models to sync when nothing had really changed.

These commands now act only on real changes, like a new field, a reordered field, or a changed value. A difference in property order alone is ignored.

These two are treated as the same model. Only the property order changed:

{
  "id": "page",
  "label": "Page",
  "repeatable": true,
  "json": { "Main": { "title": { "type": "Text" } } }
}
{
  "label": "Page",
  "repeatable": true,
  "json": { "Main": { "title": { "type": "Text" } } },
  "id": "page"
}

Reordering fields is a real change, so it still syncs:

{
  "id": "page",
  "label": "Page",
  "repeatable": true,
  "json": {
    "Main": {
      "title": { "type": "Text" },
      "body": { "type": "Text" }
    }
  }
}
{
  "id": "page",
  "label": "Page",
  "repeatable": true,
  "json": {
    "Main": {
      "body": { "type": "Text" },
      "title": { "type": "Text" }
    }
  }
}

Local files also stay stable. A pull writes properties in a consistent order, so later pulls only show real edits.

Checklist

• A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

How to QA

prismic pull
# In a custom type's index.json, reorder some metadata keys by hand.
# Keep the values and the field order the same.
prismic status
# Expect: "Already up to date."