{"version":"2.1.281","anchor":"link-chain-metadata-now-written-as-well-as-read","canonical_anchor":"link-chain-metadata-now-written-as-well-as-read","heading":"Directory-sync git worker holds back on a pending prior-life note and records a chain of links","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/link-chain-metadata-now-written-as-well-as-read","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Directory-sync git worker holds back on a pending prior-life note and records a chain of links\n\nThe git directory sync used by remote sessions now withholds publishing when a prior-life note is pending and writes a chain of links\n\n**Unclear.** The finding does not say what these links or chains are, or where they show up.\n\n**What**\n\nFor remote sessions, Claude Code keeps a git directory in sync through a background worker. Its behaviour changes in several ways:\n\n- When a prior-life note is pending and installs lag behind the recreation turn, the worker now publishes nothing and records the outcome `withheld_prior_note`. After a successful publish it clears the note.\n\n- Published journals now use the real turn index instead of `0`.\n\n- The state now declares `writesLinks: true`. Before, it only declared `readsLinks`. It also includes a `chain` of links when there are any, and the schema gains `writesLinks`, `chain` and `chained`.\n\n- A related merge function now carries `chain` through.\n\n- When further parents are not held, the parent check now returns `further_parent_unheld` instead of `parents_mismatch`.\n\nNothing has been read about the `tengu_dir_sync_git_worker_standing` gate, so its state is unknown.\n\n**Why**\n\nThis is internal plumbing for how remote sessions sync git directories. There is nothing for you to set or change, and the link history is now saved as well as read.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}