Found in the review of the duplicate-provenance fix (#400 / #394); deliberately not fixed there.
Projects duplicated before #400 ships already have source: { type: "example", exampleId: ... } persisted in their project.json. Their future runs will keep reporting the original example's id to Mixpanel until the meta changes.
Scope is small (duplicates made during roughly one month by a small user count), so no migration ships with #400. If it matters, a one-shot cleanup could rewrite source to { type: "duplicate" } for projects whose meta says example-sourced but whose dirName does not match the example id — or simply on next open of such a project.
Found in the review of the duplicate-provenance fix (#400 / #394); deliberately not fixed there.
Projects duplicated before #400 ships already have
source: { type: "example", exampleId: ... }persisted in their project.json. Their future runs will keep reporting the original example's id to Mixpanel until the meta changes.Scope is small (duplicates made during roughly one month by a small user count), so no migration ships with #400. If it matters, a one-shot cleanup could rewrite
sourceto{ type: "duplicate" }for projects whose meta says example-sourced but whose dirName does not match the example id — or simply on next open of such a project.