Unclear Which feature shows these messages to users is not known.
What
When a cloud session refuses to run a capture because of how a checkout's git configuration is set up, the reason is now worded: "a cloud session could change a file that git reads this checkout's configuration from, so that capture would run under whatever is put there". Before, it spoke of the git configuration including a file a session can write.
A separate message about trimmed entries in the search path now reports the number of entries that were actually trimmed.
Why
Only the wording and a count changed. What is refused stays the same, but the messages are easier to act on and the count is now correct.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which feature shows these messages to users is not known.