fix: report default paths in VersionError message because they can can cause VersionError

[vkarpov15]

Summary

I ran into a VersionError: No matching document found for id "xyz" version 1 modifiedPaths "lastPaidAt, totalRevenue" error - that shouldn't happen because lastPaidAt and totalRevenue are both primitives, shouldn't trigger versioning.

The root cause was an array default was triggering versioning: an array value wasn't set in the db. Paths that are in default status can trigger versioning, but VersionError doesn't currently list those paths.

Examples

[Copilot]

Pull Request Overview

This PR fixes an issue where default paths were not being reported in a VersionError even though they could trigger version conflicts.

• Updated the error generation logic in lib/model.js to include default state paths from activePaths.
• Added a test in test/document.test.js to verify that a VersionError correctly reports the default path when using push() on an array.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
test/document.test.js	Added a test case that triggers a VersionError by modifying array values to verify the fix.
lib/model.js	Updated error generation in save methods to concatenate default paths with modified paths.

Comments suppressed due to low confidence (1)

lib/model.js:464

• Consider adding a comment to explain why default state paths are concatenated with modifiedPaths, so future maintainers understand this intentional behavior.

this.$__.modifiedPaths = this.modifiedPaths().concat(Object.keys(this.$__.activePaths.getStatePaths('default')));

[hasezoey]

LGTM