{"version":"2.1.292","anchor":"tengu-immutable-tide-check-now-skips-a-not-run-reason","canonical_anchor":"tengu-immutable-tide-check-now-skips-a-not-run-reason","heading":"A server-controlled check now also fails when a step did not run","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/tengu-immutable-tide-check-now-skips-a-not-run-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### A server-controlled check now also fails when a step did not run\n\nA check that runs only when a server value is set now also returns false for a result whose reason is that it did not run\n\n**Unclear.** It is not clear what Claude Code does differently when this check returns true or false.\n\n**What**\n\nClaude Code has a check that runs only when a server-provided value is above zero. Before, it returned false for a result that ended with a non-zero exit or with no exit status. It now also returns false for a result whose reason is that it did not run at all.\n\nWhen the server sends no value, the setting falls back to 0, so the check stays off unless it is switched on remotely.\n\n**Why**\n\nThe change is narrow and only affects accounts that have a server value set for this check.\n\n- Flag `tengu_immutable_tide`: Not enough to say (read for one account on one subscription tier against v2.1.292; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}