lmcp: 1.0.0~rc1 -> 1.1.0

Tracks upstream lmcp v1.1.0 (commit 7e62f71). Closes 3 upstream
issues: #11 (progress + cancellation), #18 (windows MSI sync), #20
(concurrent handler dispatch).

Arch:
  pkgver=1.1.0 (no pre-release suffix this time).
  _tag back-translation kept so future rc bumps just need pkgver=X.Y.Z_rcN.

Debian:
  PKGVER=1.1.0 (no ~ suffix).
  Changelog entry summarises the three closed issues + the zero-
  handler-source-changes invariant.

New tarball sha256:
  d758a9504389528cb8940ea81bc8cf47afad8c01166aef3484ac4f5752445532

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

arch/lmcp/PKGBUILD

@@ -3,18 +3,18 @@
 # Source of truth: git.reauktion.de/marfrit/lmcp
 
 pkgname=lmcp
-pkgver=1.0.0_rc1
+pkgver=1.1.0
 pkgrel=1
 pkgdesc="Lightweight MCP (Model Context Protocol) server in pure Lua"
 arch=('any')
 url="https://git.reauktion.de/marfrit/lmcp"
 license=('MIT')
 depends=('lua' 'lua-socket')
-# Arch pkgver disallows '-'; encode v1.0.0-rc1 upstream tag as 1.0.0_rc1.
+# The _tag back-translation handles both clean releases (no '_') and
-# Translate back for the source URL.
+# pre-release pkgvers (e.g. 1.2.0_rc1 → v1.2.0-rc1).
 _tag="v${pkgver//_/-}"
 source=("${pkgname}-${pkgver}.tar.gz::https://git.reauktion.de/marfrit/lmcp/archive/${_tag}.tar.gz")
-sha256sums=('81f9222264371735c196664382460261ef60a259348766bbd6fd2f49ea9d1e7e')
+sha256sums=('d758a9504389528cb8940ea81bc8cf47afad8c01166aef3484ac4f5752445532')
 
 package() {
     cd "${pkgname}"

debian/lmcp/build-deb.sh

@@ -7,13 +7,10 @@
 # package (Architecture: all, depends on lua + lua-socket).
 set -euo pipefail
 
-# Debian-conventional pre-release notation: 1.0.0~rc1 sorts BEFORE 1.0.0.
+PKGVER=1.1.0
-# Upstream tag is v1.0.0-rc1 (with dash); UPSTREAM_TAG drives the source URL,
+UPSTREAM_TAG=v1.1.0
-# PKGVER feeds the Debian package version field.
-PKGVER=1.0.0~rc1
-UPSTREAM_TAG=v1.0.0-rc1
 PKGREL=1
-LMCP_TARBALL_SHA256=81f9222264371735c196664382460261ef60a259348766bbd6fd2f49ea9d1e7e
+LMCP_TARBALL_SHA256=d758a9504389528cb8940ea81bc8cf47afad8c01166aef3484ac4f5752445532
 HERE=$(dirname "$(readlink -f "$0")")
 
 # Reproducible build: pin all file mtimes + ar member timestamps to a fixed

debian/lmcp/debian/changelog

@@ -1,3 +1,27 @@
+lmcp (1.1.0-1) bookworm trixie; urgency=medium
+
+  * Concurrent handler dispatch (closes #20): tool handlers run in
+    cooperative coroutines. server.lua:run()'s sleep_ms yields to
+    the event loop instead of blocking. Slow shell commands no
+    longer serialise other requests — fast ping during a slow
+    `sleep N` returns in ~10ms (was ~N seconds).
+  * Progress + cancellation notifications (closes #11): tool
+    handler ctx gains progress(p, total?, message?) and cancelled().
+    Client→server notifications/cancelled flips a flag the running
+    handler sees within ~420ms (poll interval capped when ctx
+    present). Cancelled requests get a JSON-RPC -32800 error
+    response (spec wording is "SHOULD NOT respond" but the practical
+    UX wins; see upstream issue for the FD-inheritance trade-off).
+  * Windows MSI build sync (closes #18): windows/sync.sh script
+    refreshes windows/pkg/{lmcp,server,json}.lua from root before
+    WiX is invoked. Closes the drift trap that left the MSI ~6
+    months behind master in April 2026.
+  * Zero handler source-code changes; all existing tools (shell,
+    fetch, web_search, hub remote_*) benefit from concurrency and
+    auto-cancellation transparently via the run() helper.
+
+ -- Markus Fritsche <mfritsche@reauktion.de>  Sun, 17 May 2026 19:45:00 +0000
+
 lmcp (1.0.0~rc1-1) bookworm trixie; urgency=medium
 
   * Full MCP 2025-06-18 surface (release candidate). Closes 14