Skip to content

Link Loom preset to its installation quickstart - #1814

Open
zlareb1 wants to merge 1 commit into
HelpCode-ai:mainfrom
zlareb1:docs/loom-tested-quickstart
Open

zlareb1 wants to merge 1 commit into
HelpCode-ai:mainfrom
zlareb1:docs/loom-tested-quickstart

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Link the existing Loom preset to its published installation quickstart before connector setup. The quickstart defaults to a loopback-only single-user server, so the instructions explain that authenticated access and the appropriate HTTPS network route are separate prerequisites.

I work on Loom. Codex assisted with this documentation change; I reviewed the source and validation evidence.

Changes

  • Point docsUrl at the canonical quickstart and add the same install-first guidance to the preset instructions and connector guide.
  • Keep the endpoint, bearer-token handling, namespace guidance, tool snapshot and live-connection-unverified disclosure unchanged.
  • Regenerate the required documentation output.

Type

  • Documentation

Testing

From the repository root, using Node22:

  • Focused import of the current validateAdapter: before/after Loom preset each have zero errors and warnings. Assertions confirm only documentation fields changed and security/runtime fields remain identical.
  • node scripts/regenerate-catalog.mjs — no registration change.
  • node scripts/generate-llms-txt.mjs and --check — pass.
  • Published quickstart documentation returns HTTP200. Existing Loom1.3.0 released-stack and outside-installer CI jobs passed; this is not a live AnythingMCP bridge test.
  • Full backend catalog/Jest suite — not run locally; upstream CI remains required.
  • Live AnythingMCP-to-Loom connection — not run. The existing verification warning remains.

No live AnythingMCP bridge or production inference qualification is claimed. No external account or paid provider is used. The quickstart's development model is distinguished from production inference.

Checklist

  • My code follows the existing code style
  • I have tested the changed metadata and generated documentation locally
  • I have updated documentation
  • All existing tests pass (npm test)
  • This PR has a descriptive title

Related Issues

Follow-up to #1789. This updates the existing preset; it does not add another connector.

Explain the loopback default and authenticated HTTPS prerequisites before connector setup. Retain the existing token scope and live-connection verification limits. Follow-up to HelpCode-ai#1789.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant