lib-boundary-resolver.sh and the provider-adapter-author BOM fixtures carried literal U+FEFF characters, which apm install reports as "files contain hidden characters". Both sites feed the text to Python, which interprets the '' escape identically, so behaviour is unchanged: the resolver's strip_bom and all five validate-adapter BOM cases pass. No core package bump: the fixture writes the same bytes, so the edit is not substantive under the apm-workflow version policy. Refs #94 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi