@lmctl-ai/lmctl 0.1.340 → 0.1.342

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +15 -0
  2. package/dist/cli/index.js +520 -992
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -4,6 +4,21 @@ All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
4
4
 
5
5
  ## Unreleased
6
6
 
7
+ - **The published package no longer bundles the `serve` daemon, job queue, or
8
+ workflow engine.** `@lmctl-ai/lmctl` was designed to ship prompt
9
+ self-orchestration only — no daemon, no queue — but every version published
10
+ to date (0.1.0 through 0.1.341) actually contained the full daemon/queue/
11
+ engine code in `dist/cli/index.js`; the `serve` command's `--no-daemon` flag
12
+ was a runtime opt-out, not a build-time exclusion. This is a packaging-scope
13
+ defect, not a reachability one: the daemon binds to loopback by default and
14
+ requires an explicit auth token for any non-loopback bind or for its HTTP
15
+ API even on loopback, so nothing shipped that a normal install exposed on a
16
+ network by default. Starting with this release, the public bundle has the
17
+ `serve` dispatch's target module graph removed at build time; the CLI's own
18
+ `serve` command is gone from this package (an internal build used for our
19
+ own daemon deployment keeps it). No prior version has been unpublished or
20
+ deprecated — this entry exists so the history says what changed rather than
21
+ quietly becoming correct.
7
22
  - **A live `lmctl chat` dispatch no longer orphans the receiver's own background
8
23
  work — and its duration is now subtree-bound, not turn-bound.** Previously the
9
24
  provider transport closed the agent's stdin the instant its turn produced