Remove techmanual.ai product references

[techmanual-ai]

Summary

LabLink stands on its own, but the docs presented it as an accessory to a separate product — including a whole README section, an env var LabLink never read, and a config field named after the service.

This removes that framing and renames the one piece of schema carrying the branding, without breaking existing configs.

The config field

techmanual_document_ids → document_ids. The field always did the same thing — carry opaque pointers into an external documentation index that LabLink never resolves — so the rename just stops it naming one particular index.

Backward compatible via the legacy-key path config.py already had. All four spellings verified end to end:

document_ids             -> [7, 8]
techmanual_document_ids  -> [1291, 1323]
techmanual_document_id   -> [142]
document_id              -> [99]
(absent)                 -> []

Changed

• README: "Using with techmanual.ai (optional)" → "Pointing the agent at documentation (optional)", now vendor-neutral
• README: non-goals wording, VISA config field list, env var table
• lablink/mcp_server.py: the agent-facing server instructions and connect() docstring — these are what the model reads at runtime, so they mattered most
• docs/ARCHITECTURE.md §7.3, §7.4, §7.5, env var table
• docs/agent_docs/: development conventions and the onboarding blurb
• examples/configs/visa_scope.toml, examples/.env.example
• lablink/base.py, config.py, cli.py, interfaces/visa/{config,driver}.py
• Tests renamed to reflect that they now cover legacy keys, plus a new test for the current one

Removed

TMAI_API_KEY from the documented environment variables. LabLink never read it — it belonged to a separate tool and only appeared in the docs.

Deliberately out of scope

• The techmanual-ai GitHub org. It appears in repository URLs, CI badges, the clone command, the LICENSE copyright line, and the io.github.techmanual-ai/lablink-mcp registry identity in server.json. Changing it means moving the repo; worth deciding before the MCP registry publish makes that name sticky.
• The historical [0.1.0] CHANGELOG entry, which records what actually shipped in that release.

Testing

350 passed, including a new test_document_ids alongside the renamed legacy-key tests.

🤖 Generated with Claude Code