Titus de0bf09005 keeper ruling: stable per-vault world identity for the folder bridge ... Export minted a FRESH world id every run (faithful to folder.js, wrong for this context: azgaar conversions ARE new worlds each time; a vault world is persistent). Consequences: every re-export lands in Atlas as a brand-new world, and re-importing a re-export trips the never-merge guard against the same world's own earlier import. Fix: shared vault/world-id-marker.ts (adapter-only dotfile I/O, documented) — export reads-or-mints-and-persists the id; import records the imported folder's id as before. Re-exports are now identity-stable. Gate: tsc clean, build clean, npm test 34/34 (orchestrator hands). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-16 14:11:38 +02:00
..
element-file.ts	Phase B: frontmatter flip (span -> YAML frontmatter)	2026-07-16 13:43:56 +02:00
element-transform.ts	R9: writer-minted migration fixtures + entity-decode fix	2026-07-16 13:49:32 +02:00
folder-format.ts	Phase C: OnlyWorlds folder bridge (export/import commands)	2026-07-16 14:03:07 +02:00
world-id-marker.ts	keeper ruling: stable per-vault world identity for the folder bridge	2026-07-16 14:11:38 +02:00
world-key.ts	fix wrong-world writes + false-success rename toast (2.2.1)	2026-07-12 14:52:40 +02:00