Under the hood
The error message shown when a file_path points to an unservable file type now shares common wording
What
When you give an artifact tool a file_path whose content type isn't recognized or servable, the error message is now built from a shared message helper instead of its own separate text.
Why
This is an internal cleanup so the unservable-file error stays consistent wherever file_path is used, rather than drifting between separately maintained copies.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't say whether the actual wording shown to users changed, only that it now routes through a shared builder.