{"version":"2.1.260","anchor":"new-remote-controlled-acquire-timeout-setting-for-a-lockque","canonical_anchor":"new-remote-controlled-acquire-timeout-setting-for-a-lockque","heading":"New remote-controlled acquire-timeout setting for a lock\/queue primitive","tier":"internal","area":"Feature Gates","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-remote-controlled-acquire-timeout-setting-for-a-lockque","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New remote-controlled acquire-timeout setting for a lock\/queue primitive\n\nA lock primitive's timeout can now be remotely tuned, though no server value is set yet.\n\nA lock\/queue primitive's acquire-timeout handling was replaced by `Wbt()`, which reads a remote numeric setting `tengu_cobalt_plinth_sill` and, if it's a finite number of 0 or more, uses `Math.min(Math.floor(e), L7)` as the timeout. The prior strict input-validator for `opts.acquireTimeoutMs` is gone. `tengu_cobalt_plinth_sill` defaults to null, so absent a server-pushed value, the code falls back to the existing constant `jvn`, leaving the new remote-tunable branch present but unexercised by default.\n\n- Flag `tengu_cobalt_plinth_sill`: Not enough to say (read for one account on one subscription tier against v2.1.260; this account: no value returned, anonymous baseline: no value returned, compiled default: no gate table built for this version) 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: Feature Gates\n- Names: `tengu_cobalt_plinth_sill`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}