Unclear Which waiting step treats 'not found' as finished is not known, so it is unclear what a user might notice.
What
When Claude Code asks for a skill file and the server answers "not found" (HTTP 404), the result now includes the error message the server sent back. Before, it only reported that the file was not found.
Separately, a check used while Claude Code repeatedly polls a server, asking again and again until something is ready, now counts a "not found" answer as finished.
Why
Waiting on something that does not exist now stops instead of retrying.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which waiting step treats 'not found' as finished is not known, so it is unclear what a user might notice.