Reporting worktree dirtiness and unpushed commits to the remote bridge stays off.
tengu_ccr_handoff_metadata compiles in false.
tengu_ccr_handoff_metadata On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.248: on
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The remote bridge can report worktree state (dirty flags, unpushed commit count, submodules, LFS) alongside the current branch list, but only when the tengu_ccr_handoff_metadata gate is on, and its compiled fallback is false.
[remote-bridge] worktree_state \u2192
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.