{"version":"2.1.260","anchor":"checkpoint-rewind-gains-a-documented-skippedlinks-telemetr","canonical_anchor":"checkpoint-rewind-gains-a-documented-skippedlinks-telemetr","heading":"Checkpoint rewind gains a documented skippedLinks telemetry\/response field for symlink-safety refusals","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/checkpoint-rewind-gains-a-documented-skippedlinks-telemetr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Checkpoint rewind gains a documented `skippedLinks` telemetry\/response field for symlink-safety refusals\n\nCheckpoint rewind now documents a field counting files skipped for symlink safety.\n\nCheckpoint rewind responses now document a `skippedLinks` field, counting tracked files that weren't restored because a symlink or hard link was found at the tracked path, a parent directory no longer resolves correctly, or the backup couldn't be safely read. This field is only populated on a real (non-`dryRun`) rewind; `dryRun` previews never set it and their counts don't reflect link-safety refusals.\n\n- Area: Sessions\n- Names: `skippedLinks`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}