Bingbing bf61f6ba45 fix: stop restamping ApiSpec.modified on startup and git round-trips (#10625) ...

## Background

In a Git-synced project, restarting Insomnia without any change marked every design document as modified in the Git staging list. The diff of each affected YAML contained exactly one line: the embedded ApiSpec `meta.modified` timestamp.

The v5 design-doc YAML does not serialize `ApiSpec.fileName` (the v5 schema has no such field), while v5 import parses a missing `fileName` as an empty string. Any git round-trip therefore reset `fileName` to empty in the database, and the startup repair (`_applyApiSpecName`) rewrote it via `docUpdate`, which unconditionally restamped `modified: Date.now()` for every design document in one burst. RepoFileWatcher then re-exported the database to disk and git status reported all files as modified, repeating on every startup until committed.

## Changes

- Import: fall back `ApiSpec.fileName` to the file top-level name when the spec uses the `{ contents }` shape, so a round-trip never stores an empty fileName.
- Repair: skip the fileName backfill when it would write the existing value; a no-op write only restamps `modified`.
- Regression tests for both behaviors.

Fixes INS-4058

2026-10-20 02:58:17 +00:00

..

init-model

feat: Migrate collection and document workspace zod schema and type definitions- #10520 (#10582)

2026-10-15 13:45:30 +08:00

database-nedb.ts

fix: Warn when a Git Sync change cannot be discarded [INS-3830] (#10585)

2026-10-14 09:53:20 +00:00

database.test.ts

fix: stop restamping ApiSpec.modified on startup and git round-trips (#10625)

2026-10-20 02:58:17 +00:00

repair-database.ts

fix: stop restamping ApiSpec.modified on startup and git round-trips (#10625)

2026-10-20 02:58:17 +00:00