Unclear The extra step returns its input unchanged, so it's unclear what purpose it serves or whether it has any visible effect.
What
The internal code path that measures how long git worktree detection takes (worktrees let you check out multiple branches of a repo at once) now runs one extra step before reporting the tengu_worktree_detection timing telemetry. This step reads the length of a list of results and then passes the list along unchanged.
Why
The step doesn't appear to alter the data, so this looks like an internal adjustment to how the timing is measured or logged rather than a change to worktree detection itself. It's not clear yet what purpose the extra step serves.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The extra step returns its input unchanged, so it's unclear what purpose it serves or whether it has any visible effect.