Repository navigation
v0.9.43
Documentation-truth and hygiene release after an end-to-end product evaluation. Tool behaviour is unchanged except where a tool's own text or output framing was wrong.
Changed (npm package)
novada_proxysays what it returns. Its description, thenovada_discovercatalog line, the CLI help and thenovada-agentskill now state that the tool returns a proxy config template — username shown as<PROXY_USER>, password as***— and never prints credentials. (The output was already masked; the text claimed otherwise.)novada_setupnever names a tool the session cannot call. On the hosted surface it no longer listsnovada_browseror the Browser-WS add-on.novadaSetup()takes an optional visible-tool set as a third argument, the same mechanismnovada_discoveralready used.novada_discoverreports 9 hosted-hidden tools (includingnovada_browser), derived from one exported list (HOSTED_HIDDEN_TOOLS) that a test keeps equal to the hosted server'sHOSTED_HIDDENset.- Developer-API 401 errors point at
https://dashboard.novada.com/api-key/instead of an internal host that the redactor turned into[novada-internal-host]. - The shipped
novada-proxyskill refers tonovada_proxywithtype=…instead of six tool names that no longer exist. - Smaller tarball: sourcemaps are no longer published (
!build/**/*.map), 439 → 225 files. The deadbenchmarknpm script (no directory,tsxnever a dependency) is removed. - Removed
scripts/verify-c1-live.mjs(one-off probe with a hard-coded macOS path; tracked despite the repo's own.gitignorerule, unreferenced).
Added
- Official MCP Registry publishing via GitHub Actions OIDC. A manually triggered, secretless workflow validates and publishes
server.jsonunder the repository-ownedio.github.NovadaLabs/*namespace with onlycontents: readandid-token: writepermissions. - Root
LICENSE(MIT) so GitHub detects the license. - Tests: hosted-surface
novada_setupvisibility, hosted-hidden list parity, 401 message wording,novada_extract format=jsonoutput parses as JSON.
Fixed (hosted server — mcp.novada.com, not part of the npm package)
- JSON results are no longer corrupted by the
gateway:footer. When a tool result is JSON (format=json), the footer is returned as a second content block instead of being appended to the JSON text (api/_footer.ts, 7 tests). - Nightly canary no longer reports the canary account's own expired plan as a production failure. A truthful
PRODUCT_UNAVAILABLErefusal with ledger evidence is classifiedXFAIL: CANARY_ACCOUNT_PLAN(issue #18) inscripts/contract/contract-test.py; every other error still fails. vendor/package.jsonversion drift.deploy-hosted.shandsync-to-hosted.mjsnow keep the vendor shim's version equal to the npm package (it had reported 0.9.3 since June; the vendoredconfig.jsreads it at runtime). Vendor re-synced in this release.
Docs
- README rewritten (164 → 81 lines): outcome line, what the server is good at, example prompts, hosted quickstart, an honest comparison with Firecrawl, Tavily and Bright Data. Removed claims that did not match the code: the
confirm:truewrite-gate (writes use a two-step approval token), "6 categories", "4.9× more compact", and browser automation on the hosted surface.npm-package/README.mdlinks are absolute so they work on npmjs.com. docs/TOOLS.mdandARCHITECTURE.mdcorrected (14 working platforms / ~76 operations, hosted browser exclusion, approval-token wording);CLAUDE.mdlists the real top-level directories;HANDOFF.md/PROJECT_STATE.mdmarked historical;CONTRIBUTING.mdcarries the release checklist (the pre-monorepopromote-to-public.shis no longer referenced).
Full evaluation that drove this release: see PR #27.