{"version":"2.1.283","anchor":"publish-journal-lane-loss-and-degraded-anchor-rounds-handled","canonical_anchor":"publish-journal-lane-loss-and-degraded-anchor-rounds-handled","heading":"Publishing reports some skipped rounds and lost connections differently","tier":"internal","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/publish-journal-lane-loss-and-degraded-anchor-rounds-handled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Publishing reports some skipped rounds and lost connections differently\n\nA publishing feature now records rounds skipped over a weakened sync point as skipped rather than upload-only\n\n**Unclear.** It is not clear which Claude Code feature these publishing journals belong to.\n\n**What**\n\nA publishing feature that keeps a journal of its rounds reports some outcomes differently:\n\n- a round skipped because its sync point was degraded is now recorded as skipped, not as upload-only\n\n- a conflict check can now report a lost connection\n\n- an unavailable connection keeps its cause when it is reported\n\n**Why**\n\nThis changes how these publishing outcomes are labelled when they are put off.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}