Skip to content

docs: llms-install.md (Cline/Claude/stdio install guide) - #20

Merged
MasterPlayspots merged 1 commit into
mainfrom
docs/llms-install
Aug 5, 2026
Merged

docs: llms-install.md (Cline/Claude/stdio install guide)#20
MasterPlayspots merged 1 commit into
mainfrom
docs/llms-install

Conversation

@MasterPlayspots

Copy link
Copy Markdown
Owner

Agent-lesbare Installationsanleitung fuer die Verzeichnis-Submissions (Cline verlangt README/llms-install-basiertes Setup). Hosted-Endpoint-Config + stdio-Alternative + Liveness-Check.

…stdio)

Hosted endpoint config for Cline (streamableHttp), Claude Code, Claude
connectors, plus the npx stdio alternative with the full local toolset.
Includes a curl liveness check and the keyless rate limit.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0149NhkePB1zzszxUyG1L5vW
@netlify

netlify Bot commented Aug 5, 2026

Copy link
Copy Markdown

Deploy Preview for strong-fudge-f04a16 ready!

Name Link
🔨 Latest commit 4827330
🔍 Latest deploy log https://app.netlify.com/projects/strong-fudge-f04a16/deploys/6a7334d2a435e70008cd3b8a
😎 Deploy Preview https://deploy-preview-20--strong-fudge-f04a16.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@MasterPlayspots
MasterPlayspots merged commit 9ecc19c into main Aug 5, 2026
11 checks passed
MasterPlayspots added a commit that referenced this pull request Aug 17, 2026
…caught it (#24)

* docs(changelog): 1.2.5 through 1.2.7, plus the gate that should have caught it

THE MEASURED GAPS
  1. Five tags exist (v1.2.3 ... v1.2.7). One GitHub release does (v1.2.5).
  2. CHANGELOG ended at 1.2.4 while npm served 1.2.7 — three releases with
     no entry.
  3. Unreleased commits sit on main after v1.2.7.

WHAT CHANGED
  CHANGELOG: 1.2.5, 1.2.6 and 1.2.7 written from the commit log, not from
  memory. Tone follows 1.2.7's own name — "honest short descriptions".

  bin/changelog-gate.js: the previous prepublishOnly check only asked whether
  CHANGELOG.md EXISTED. It did, continuously, while three versions shipped
  without an entry. A file-exists check cannot catch that; it was green the
  whole time. The new gate requires a NON-EMPTY "## [<version>]" section.

  .github/workflows/release.yml: a tag now creates its GitHub release, with the
  changelog section as the release notes. Writing release notes twice means
  writing them differently, and then neither is authoritative.

PROVEN, not asserted:
  version present + section filled  -> exit 0
  version absent from CHANGELOG     -> exit 1
  section present but empty         -> exit 1
  npm test green, npm audit: 0 vulnerabilities

CORRECTIONS to the task description:
  · It claims TWO unreleased commits after v1.2.7. There are THREE — the extra
    one is 4d6fb59 "fix: resolve high severity npm vulnerability". A security
    fix is sitting on main, unpublished; npm still serves 1.2.7 without it.
    Recorded under [Unreleased].
  · plugin.json does not exist on main, so it cannot be at 1.2.7 as claimed.
    package.json and server.json are both 1.2.7 — no drift between those two.
  · The six "orphan" branches are all genuinely merged (PRs #4, #15, #17, #18,
    #19, #20); only the refs remain. Deleting them is K4 — listed, not done.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(deps): regenerate package-lock.json — it pinned nothing

CI was red on this PR. It is red on `main` too, for the same reason and
independently of anything in this branch: a clean `main` worktree fails
`npm ci` identically.

  npm error `npm ci` can only install packages when your package.json and
  npm error package-lock.json are in sync.
  npm error Missing: @commitlint/cli@21.2.2 from lock file
  npm error Missing: @modelcontextprotocol/sdk@1.30.0 from lock file
  npm error Missing: zod@4.4.3 from lock file
  ... 20 more

The lock file was not merely stale. It carried NO ENTRY for either runtime
dependency — @modelcontextprotocol/sdk and zod — and none for the devDependency
tree at all. It pinned nothing. Every CI job died at `npm ci` before running a
single test, which is why coverage, e2e, lint, security and all three test
matrix legs failed within 17 seconds.

Regenerated with `npm install --package-lock-only`. The resulting versions match
exactly what package.json already specifies (sdk 1.30.0, zod 4.4.3), so this
changes no dependency — it records the ones that were already chosen.

  npm ci --dry-run   passes
  npm test           green
  npm audit          0 vulnerabilities

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.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