fix(cli): pass non-nil context through namespace tool dispatch

[chiplay]

Problem

In the shipped Go CLI (@subtextdev/subtext-cli@1.0.0), every tool invocation across every namespace fails:

$ subtext doc list
error: fetching tool: net/http: nil Context
$ subtext live view-list --help
error: net/http: nil Context

Only version, auth whoami, and namespace-level --help work. The CLI cannot call a single MCP tool — its core purpose is non-functional.

Root cause

Namespace commands (live/comment/doc/artifact) use DisableFlagParsing and delegate by calling callCmd.RunE(callCmd, …) directly (namespaces.go), never through cobra's Execute. So callCmd's context is never set. runCall then passes cmd.Context() — nil — into c.GetTool/c.CallTool → http.NewRequestWithContext(nil, …) → net/http: nil Context.

auth whoami and namespace listing survived only because they call ListTools(context.Background()) explicitly (help.go).

Fix

• namespaces.go: propagate the namespace command's context to callCmd before delegating.
• call.go: guard runCall with a context.Background() fallback and use it at all three call sites, so the HTTP request builders never receive a nil context (defense-in-depth; also makes runCall correct when called directly).

Test

Added integration_test.go — drives the real namespace dispatcher (namespaceRunE → callCmd) against a stub httptest MCP server, exercising the cmd.Context()→HTTP path the stubbed unit tests never reached. Verified it fails with the exact net/http: nil Context error on unpatched code and passes with the fix.

Verification

go build ./... + go test ./... clean. Locally-built binary verified against the production na1 endpoint:

• doc list returns real proof docs ✅
• per-tool --help fetches schemas ✅
• live connect → screenshot → artifact upload → comment add → disconnect full round-trip ✅
• version / auth whoami / namespace --help unaffected ✅

Warrants a v1.0.1 patch release once merged.

🤖 Generated with Claude Code

---

Note

Low Risk
Small, localized CLI dispatch fix with a regression test; no auth or server changes.

Overview
Fixes broken MCP tool calls for namespace commands (doc, live, comment, artifact). Those paths delegate to internal callCmd without going through Cobra Execute, so callCmd had a nil context and every GetTool / CallTool failed with net/http: nil Context.

namespaceRunE now copies the namespace command’s context onto callCmd before delegating. runCall also normalizes context (uses context.Background() when still nil) and routes help, schema fetch, and tool invocation through that ctx.

Adds TestNamespaceDispatchCallsTool, an httptest integration test that runs namespaceRunE → callCmd and asserts a full tools/list + tools/call round trip—covering the path unit tests did not hit.

^{Reviewed by Cursor Bugbot for commit 6084902. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chiplay]

@jurassix I tried using the CLI 1.0.0 and hit this issue. Can you take a look next week and see if this is the right fix?