[miroir-framework]

Requested by A · project thread

Closes #509

What changes

• listReducerToSpreadObject takes the uuid of its file name, 0894ed4f-ca11-4b04-878d-471d1d780fac. It shared 8ddb7e2e-… with indexListBy, so a uuid-keyed store kept only one of the two. No code refers to either definition by uuid (index.ts imports both by path), so no other reference changes.
• New guard scripts/check_instance_uuids.py (npm run check:uuids). It fails when two tracked instances in one Entity folder of a deployment (packages/**/<entityUuid>/*.json) share a uuid. It skips folders of Entities whose idAttribute is not uuid, and fails on a file that is not valid JSON. A pytest test runs it on the repository, so the existing pytest scripts/tests step of the pre-push gate and of pr-checks.yml enforces it.
• The guard found a second duplicate. miroir_modelVersion/c3f0facf…/695826c2-…-dee46fe21c1.json was a copy of the Initial ApplicationVersion …dee46fe21c13.json under a truncated file name, with only whitespace differences. The copy is removed and index.ts imports …c13.json. MIROIR_VERSION_HISTORY_PARENTS drops from 2 to 1 for that folder, since the filesystem store had returned the copy as a second row.

Why a Python guard and not a modelValidation test: miroir-app-miroir's modelValidation builds its plan from defaultMiroirMetaModel, which has no TransformerDefinition instances, and modelValidation runs only in nonreg. Details and the rejected options are in code-helpers/features/509-FIX-duplicate-transformer-definition-uuid/analysis.md. The TDD plan sits next to it.

Postgres, IndexedDB and MongoDB stores seeded before this change hold one of the two definitions under 8ddb7e2e-…. They get 0894ed4f-… once reseeded.

Out of scope: 14 files whose name differs from their uuid without a collision (listed in the analysis). A later issue can enforce file name == uuid.

Checks

• Pre-push gate: skills sync, pytest scripts/tests (325 passed, 11 of them new), dependency policy, lint, miroir-env check --strict --tracked-clean, tsc miroir-core and miroir-app-miroir, npm run test -w miroir-core (3239 passed). All green.
• modelValidation miroir-app-miroir 166 passed. versioningModes.assetsLayout and versioningModes.filesystem-seed (test-filesystem) pass.
• npm run nonreg:filesystem -- --runner shared: 112 passed, 2 failed. Neither failure comes from this PR, which touches no Report or MiroirTest. unit-274-multistep-reports expects 94 seed Reports and finds 96. unit-report-tests expects a Report suite list without report.agentRunHistory. Both counts moved with the FEATURE: measure what building with coding agents costs on Miroir #550 assets. #602 Postgres stores ML numbers as double precision; Report counts include the #550 Reports #603 (issue Postgres store rejects decimal numbers; two unit tests expect stale Report counts #602) updates both tests, but it merged into aba, not _integration, so they stay red here until that fix reaches _integration.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BHqqe1gocM9Y9mjwK9YX3H

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Gives listReducerToSpreadObject its own UUID and removes a duplicate ApplicationVersion file.

• The list reducer now has its own UUID in the Miroir model.
• The initial application version now comes from one asset.
• A repository check catches repeated instance UUIDs in deployment assets.

Scope acknowledged by miroir-framework: existing seeded stores need reseeding; filename/UUID mismatches without collisions remain deferred.

_{Reviews (1) · Last reviewed commit: "#509: distinct uuid for listReducerToSpr..." · Reviewed by Greptile}