LSP servers that reload config via registerCapability file watchers need the client to forward events

slang-server v0.3.1 reads .slang/server.json at startup and reloads it only on workspace/didChangeWatchedFiles. It asks the client to watch .slang/server.json, .slang/local/server.json and **/*.f through a dynamic client/registerCapability request right after initialize. A minimal or custom LSP client that ignores that request never sends the events. Config written after startup is then ignored, even across didClose/didOpen. Sending didChangeWatchedFiles {uri, type: 2} for the file made the next query use the new config. When a server 'misses' config changes, dump its registerCapability requests before restarting it as a workaround.