@lmctl-ai/lmctl 0.1.95 → 0.1.96
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.
- package/CHANGELOG.md +13 -0
- package/dist/cli/index.js +491 -487
- package/dist/cli/schema.sql +1 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,19 @@
|
|
|
2
2
|
|
|
3
3
|
All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
|
|
4
4
|
|
|
5
|
+
## 0.1.96 — 2026-07-10
|
|
6
|
+
|
|
7
|
+
- **Fixed: 0.1.95 silently stopped recording `team_chat_log`.** The chat-log INSERT omitted the
|
|
8
|
+
`origin` column, so on any existing database (where `origin` is `NOT NULL`) every insert failed
|
|
9
|
+
with `NOT NULL constraint failed: team_chat_log.origin` and the row was dropped — chats still
|
|
10
|
+
worked, but the audit trail stopped. Found by dogfooding the published artifact.
|
|
11
|
+
- **Fixed: fresh 0.1.95 databases got a `team_chat_log` without an `origin` column at all.** The v46
|
|
12
|
+
migration hand-duplicated the table shape and drifted from `schema.sql`, so new installs never
|
|
13
|
+
recorded operator-vs-agent origin. Fresh and migrated databases now produce an identical table, and
|
|
14
|
+
a pre-46 database gains `origin` (existing rows backfilled to `unknown`) with its rows preserved.
|
|
15
|
+
- Regression tests now assert that a fresh database's `team_chat_log` column set matches `schema.sql`
|
|
16
|
+
exactly, and that a migrated database also has `origin`.
|
|
17
|
+
|
|
5
18
|
## 0.1.95 — 2026-07-10
|
|
6
19
|
|
|
7
20
|
- **Removed `I_am=` (and `--from`) entirely.** A member's identity now resolves **only** from
|