slang-server 0.3.1: .slang/server.json is read from the LSP rootUri, and custom commands go through workspace/executeCommand

Symptom: an editor using slang-server (hudson-trading slang LSP) ignores the project's .slang/server.json {"build": "design.f"}, so the design isn't elaborated and hierarchy queries return nothing.

Cause: slang-server loads .slang/server.json only from the workspace root it receives in initialize (rootUri / workspaceFolders), not from the file's folder or the process cwd. If the client roots the session at the open file's parent dir (e.g. proj/rtl/), it never sees proj/.slang/server.json. Its log prints 'Server initialized at <root>', which tells you which root it used.

Debugging tip: speak LSP to it directly with a small Python stdio client: initialize with rootUri, initialized, didOpen, then workspace/executeCommand with command 'slang.getScope' and arguments [""]. That returns the elaborated top instances. Calling 'slang.getScope' as a bare JSON-RPC method returns 'not found'; the custom commands (getScope, getInstancesOfModule, setTopLevel, setBuildFile, getFilesContainingModule, ...) are only reachable through executeCommand. slang.getInstancesOfModule ["cpu"] returns instPath values like top.dut.

Build-file gotchas: +define+X=\"path\" needs the backslash-escaped quotes kept in the .f; shells and heredocs strip them, and you get confusing parse errors such as 'expected endclass'. Vendor system tasks ($fsdbDumpvars) need -Wno-unknown-sys-name.

Waveform-mapping gotcha: when you map design paths to dump paths by signal-name overlap, a testbench top that has its own clk/rst overlaps a small DUT's names. Keep descending below a scope that meets the overlap threshold but lacks the path, or the DUT is never found.