@lmctl-ai/lmctl 0.2.8 → 0.2.9

package/dist/cli/version-util.d.ts

@@ -1,2 +1,23 @@
 /** Resolve the package.json version of lmctl-next, with a safe fallback. */
-export declare function readLmctlNextVersion(): string;
+export declare function readLmctlNextVersion(root?: string): string;
+/**
+ * Real incident, 2026-09-29 (math routing, strengthening queued#21790): a
+ * dev-linked lmctl reported `--version 0.2.1` while running code from a much
+ * newer, unreleased checkout -- package.json's version is only bumped by the
+ * release commit, so any checkout sitting between releases (or a stale one
+ * that never rebuilt) silently reports the PREVIOUS release's number while
+ * running different code. That produced real false confidence: a flag
+ * removed that same morning was about to be published as verified-current
+ * documentation.
+ *
+ * A real npm install has no `.git` directory (pack-release excludes it), so
+ * this only ever adds detail for a git checkout, and degrades safely (plain
+ * `readLmctlNextVersion()`) whenever git is unavailable, the directory isn't
+ * a repo, or any git call fails -- `--version` must never hard-depend on git
+ * being installed.
+ *
+ * `root` is a test seam (defaults to the real package root) so tests can
+ * point this at a throwaway fixture repo instead of asserting on whatever
+ * commit this repo's own checkout happens to be at when the suite runs.
+ */
+export declare function resolveLmctlVersionDisplay(root?: string): string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lmctl-ai/lmctl",
-  "version": "0.2.8",
+  "version": "0.2.9",
   "description": "A provider-agnostic control plane for teams of AI coding agents — across providers, with independent review and durable memory.",
   "type": "module",
   "homepage": "https://lmctl.com",