fix(newos4): send num_ctx to Ollama, and make one auto-connect failure read as one line

Two things I had flagged as "worth your attention" and one leftover nit.

- num_ctx was never sent. Ollama's server-side default context is 2k-4k depending on the build, so
  a system prompt + 20 messages + up to 24k chars of tool results could be truncated server-side,
  which is exactly the "it forgot what it just read" class of report. Every Ollama request now
  carries options.num_ctx (default 16384, overridable via webx11_ollama_numctx, floor 512); the
  OpenAI-compatible branch is untouched because num_ctx is not one of its parameters.
- Automatic connect prints one outcome instead of one line per endpoint tried (7 -> 3 on a dead
  endpoint). Interactive `ollamaconnect` keeps the per-endpoint detail.
- write_file's failure message no longer echoes a trailing slash.

Verification:
- test-ollama-numctx.js (7 asserts): generate and chat payloads carry num_ctx=16384, a stored
  override is used, junk/too-small values fall back, and the /v1/chat/completions branch does not
  receive it. RED on HEAD: TypeError reading 'num_ctx' of undefined. Suite 20/20.
- Live v4.6.117, capturing the real request: {"num_ctx":16384} on /api/generate with
  model gemma4:31b-cloud, reply "OK".
- Live v4.6.118, dead endpoint (127.0.0.1:9, fallback disabled): automatic -> 3 lines
  ("connecting on first use…", "Connecting to dead…", "Auto-connect failed — …"); manual
  connect() -> 4 lines including "endpoint http://127.0.0.1:9 failed", so the suppression is
  conditional, not blanket.

1 files changed, 1 insertions, 1 deletions

diff --git a/modules/core/module-loader.js b/modules/core/module-loader.js
index b74987e..c383f23 100644
--- a/modules/core/module-loader.js
+++ b/modules/core/module-loader.js
@@ -4,7 +4,7 @@
     // Core module bundle loaded synchronously in main.html.
     // This loader only handles version cache-busting, splash, terminal init, and optional ext modules.
 
-    const LATEST_VER = 'v4.6.116';
+    const LATEST_VER = 'v4.6.118';
     const CACHE = '?v=' + LATEST_VER;
     // Exposed so ext modules can register their own URL with the same cache-busting version
     // instead of an unversioned path the browser may already have cached (shell.js did).