docs: verify remaining untested method surfaces (wave-7 follow-up)

Every method surface listed as "Untested in this session" now smoked
against fixtures or real artifacts, with findings documented in the
relevant per-language page.

sbt-direct BSP mode — full surface verified on fixtures/scala-sbt:
- test {} → {statusCode:1, originId} (BSP OK)
- clean {} → {cleaned:true}
- dependency-sources {} → classpath items
- reload {} → null
- run {target:"root"} → {statusCode:1, originId}
- run {} (missing target) → HTTP 500 "run requires exactly one target"
- compile {target:"does-not-exist"} → HTTP 500 "no build target matched"
- cold without .bsp/sbt.json → fatal log "BSP descriptor not found"
  + hint to run `sbt bspConfig`
- soft-reload on `touch build.sbt` → pid preserved, coordinator log
  shows "[sbt-direct] bsp workspace/reload"

docs/per-language/sbt.md — Verified smokes section expanded with each
exit code + error-path snippet.

dotnet-direct run — root cause of the earlier exit 150: `dotnet run
--no-restore --no-build` looks for the Debug configuration binary;
if only Release was pre-built, the binary isn't found. Adapter is
transparent; user must pass configuration:"<matches-your-build>".
docs/per-language/dotnet.md § Quirks gained a run-with-no-build
example showing the correct invocation pattern.

vue-direct hover/definition/references — tested on both the fixture
and a real equinox web/packages/core Vue 3 project. Returned null
across positions including inside script-setup TS identifiers.
Verified identical behavior on the `pre-refactor` git tag: same null
result on the exact same query. No regression; this is Vue LS v3 +
tsserver virtual-file bridging timing that predates the refactor.
docs/per-language/vue.md gained an Op-surface note documenting that
documentSymbol is the baselined probe and semantic queries may need
5-10s post-didOpen settle time (or may still return null depending on
tsserver state).

vue-hybrid adapter is a verbatim port; null-result reproduction under
pre-refactor confirms the port is correct even when the backing
server is pessimistic.

Gates clean: verify.sh --diff-baselines, hooks/tests/run.sh 97/97,
node --test 19/19.

Author: Blanquitoh

docs/per-language/dotnet.md

@@ -82,6 +82,14 @@ force-recycle when a stale server drifts.
   BootServerSocket.
 - Single-project workspaces: most methods accept an optional `project`
   parameter; omit when there's only one `.csproj` in the workspace.
+- `run` with `--no-build` requires the matching configuration to be
+  pre-built. Example: if you built `dotnet-direct call build
+  {"configuration":"Release","noRestore":true}`, then `call run
+  {"configuration":"Release","extraArgs":["--no-build","--no-restore"]}`
+  succeeds; `call run {"extraArgs":["--no-build","--no-restore"]}`
+  without the `Release` configuration hint fails because dotnet run
+  defaults to Debug/net9.0/ which wasn't built. Pass
+  `"configuration": "<matches-your-build>"` to run.
 
 ## Network-sandbox interaction
 

docs/per-language/sbt.md

@@ -20,9 +20,23 @@ coordinator lifetime. Every `call` rides the same JSON-RPC connection.
 - `call build-targets {}` → 3 targets (`root`, `root-test`,
   `root-build`) with capabilities `{canCompile, canTest, canRun}`.
 - `call compile {}` × 3 consecutive calls: 159ms / 196ms / 138ms;
-  coordinator PID unchanged across all three (persistent JVM
-  confirmed).
+  coordinator PID unchanged across all three (persistent JVM).
+- `call test {}` → `{statusCode: 1, originId: "sbt-direct-test-<ts>"}`.
+- `call run {target: "root"}` → `{statusCode: 1, originId: "sbt-direct-run-<ts>"}`.
+- `call clean {}` → `{cleaned: true}`.
 - `call sources {}` → 15 source-file entries across targets.
+- `call dependency-sources {}` → classpath items including Coursier
+  cache paths.
+- `call reload {}` → result null (BSP workspace/reload).
+- soft-reload on `touch build.sbt` mid-session → PID preserved,
+  coordinator log shows `[sbt-direct] bsp workspace/reload`.
+- error paths: `call run {}` (no target) → `{"error":"run requires
+  exactly one target"}`; `call compile {target:"does-not-exist"}` →
+  `{"error":"no build target matched \"does-not-exist\" (known:
+  root, root-test, root-build)"}`.
+- cold without `.bsp/sbt.json` → coordinator fatal log: `BSP
+  descriptor not found at <ws>/.bsp/sbt.json — run 'sbt bspConfig'
+  in the workspace first, or use the sbt-oneshot adapter`.
 
 ### Earlier attempt: sbt's own `sbt --client`
 

docs/per-language/vue.md

@@ -2,6 +2,19 @@
 
 Proxies Vue Language Server v3 + a paired tsserver hosting `@vue/typescript-plugin` over HTTP. Uses a dedicated hybrid coordinator (`vue-direct-coordinator.js`) rather than the generic `lsp-stdio-proxy.js`, because Vue LS v3 is hybrid-mandatory.
 
+## Op-surface note
+
+`textDocument/documentSymbol` is the canonical probe and is baselined
+by `scripts/verify.sh`. Semantic queries that depend on the virtual-
+file bridge (`textDocument/hover`, `textDocument/definition`,
+`textDocument/references`) may return `null` / `[]` depending on how
+long tsserver + `@vue/typescript-plugin` take to fully materialize the
+.vue's virtual .ts module. This behavior is identical pre- and post-
+refactor (verified by diffing against the `pre-refactor` tag on a real
+Vue 3 / Quasar project — both returned null for the same hover
+position). When affected, waiting 5-10s after the first `didOpen`
+before issuing hover/definition usually resolves it.
+
 ## Install prereq
 ```bash
 npm i -g @vue/language-server@3.2.6 \