fix: pull writes canonical model files and detects changes reliably

[angeloashmore]

Resolves:

Description

prismic pull rewrote model files that had no changes. It also did not rewrite files whose key order was different from the format that it writes.

This PR corrects both faults. Model comparison now sorts keys at every depth before it compares. Field order stays the same. Pull rewrites local files that have a non-canonical key order. prismic sync uses the same comparison as pull. push and status continue to ignore key order. As a result, they push nothing and report nothing when only the key order is different.

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 ¹

1. Open a project with committed model files that Slice Machine wrote.
2. Run prismic pull. The command rewrites the files.
3. Run prismic pull again. The command prints "Already up to date." and leaves no dirty files.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes core model diffing and canonicalization used by pull, sync, and disk writes—incorrect equality could cause missed updates or unnecessary rewrites, but scope is CLI sync logic with new integration tests.

Overview
Fixes pull rewriting model files on every run and missing non-canonical key order on disk. Comparison now canonicalizes the remote model and compares it to the local JSON (as read from files), so pull only updates when content differs and rewrites locals into the canonical on-disk shape. prismic sync uses the same equality rules for slices and custom types.

canonicalizeCustomType / canonicalizeSlice are tightened: sortKeys recurses through nested objects and arrays; nested Group fields and Slices zone choices (including legacy Slice non-repeat / repeat) are canonicalized explicitly without treating slice choice order as sortable metadata.

Tests cover a forced pull that asserts sorted key layout (groups, thumbnails, legacy slice choices), a second pull reporting up to date, status/push staying quiet when only key order differs, and sync reporting slice-only changes.

^{Reviewed by Cursor Bugbot for commit d592dae. Bugbot is set up for automated code reviews on this repo. Configure here.}

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit d592dae. Configure here.}

[cursor]

Sync spurious change notifications

Medium Severity

prismic sync now treats models as unchanged when only remote JSON key order differs, but the watch loop still keys off a raw JSON.stringify hash. When that hash flips with no insert/update/delete work, it still runs generateTypes() and logs Changes detected in with an empty suffix.

Additional Locations (1)

• src/commands/sync.ts#L72-L74

 

^{Reviewed by Cursor Bugbot for commit d592dae. Configure here.}