{"version":"2.1.260","anchor":"notsent-now-distinguishes-a-rule-rejection-from-a-git-re","canonical_anchor":"notsent-now-distinguishes-a-rule-rejection-from-a-git-re","heading":"notSent() now distinguishes a 'rule' rejection from a git-read failure","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/notsent-now-distinguishes-a-rule-rejection-from-a-git-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### notSent() now distinguishes a 'rule' rejection from a git-read failure\n\nDirectory sync now explains separately whether changes weren't sent due to a rule or a git read failure.\n\nThe directory-sync `notSent` reporter now takes a second parameter distinguishing a `\"rule\"` rejection from a git-read failure. For rule violations it explains that Claude's changes from this turn were not sent because of `o`, and that they go out with the first turn after that is fixed; a git-read failure produces separate explanatory text.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}