dsh-git

LIMITATIONS

Known limitations

- Graph data is persisted with the DSH profile. Ledgers saved by the previous `localStorage` version are not migrated. When an affected Session is viewed, its graph is re-imported from the Session log, but branch names and old merge parents stored only in the browser are lost. - The ledger does not push changes across tabs. Two tabs open on the same scope each hold an in-memory copy, and the last write wins; `domain/changed` broadcasts only within the Host process. - Project graph PA data is reloaded from the Host on every request. Merge Sessions created by the current version store provenance in their logs; older merge Sessions still depend on the ledger for exact multi-parent metadata. If the ledger is missing, the project graph shows only the provable primary lineage rather than guessing missing merge parents. - Turns created before the plugin was installed are imported when their Sessions are viewed. DSH forks not created by dsh-git cannot be deduplicated into a shared PA identity. - Only selected completed turns are written into the merge Session seed. Unselected ancestor turns are not inherited implicitly. - Core trajectory events are copied, while source-plugin-specific log-only events are excluded from the merge seed.