VS Code Local files.associations Setting Not Propagated to Remote‑SSH Host

The goal is to have a custom file extension, such as *.foo, recognized as JavaScript both when editing files locally in VS Code and when the same workspace is opened through the Remote‑SSH extension on a production Linux host.

Locally, adding "*.foo": "javascript" to the files.associations setting activates the correct language mode, but when connecting via Remote‑SSH the setting appears to stay on the client side and the remote editor treats the file as plain text.

Uncertainty remains whether VS Code provides a mechanism to synchronize client‑side files.associations with the remote host, or if the remote side must be configured independently, for example by installing the language extension on the SSH host or by using a remote‑specific setting.

Is there a VS Code setting that propagates files.associations to the Remote‑SSH host?

Does installing the corresponding language extension on the remote host eliminate the need for client‑side files.associations?