@lmctl-ai/lmctl 0.2.3 → 0.2.5

package/dist/providers/config/model-selection-lint.d.ts

@@ -36,8 +36,10 @@ export declare function modelSelectionWarnings(members: MemberConfig[], opts?: {
  *   - unresolved     -> silent (deliberate non-binding in lmprice's alias
  *     table, not lint's claim to second-guess)
  *   - no-catalog / catalog unavailable -> skip silently
- * The returned warnings wire into lint/seed's standard warnings array, so
- * `lint --strict` promotes them exactly like every other warning.
+ * The returned warnings wire into lint/seed's standard warnings array
+ * (operator ruling, 2026-09-29: lint has exactly two outcomes, ok/warning --
+ * never an error, and the `--strict` flag that used to promote warnings to
+ * a failing exit code has been removed entirely).
  */
 export declare function catalogModelWarnings(members: MemberConfig[], opts?: {
     snapshot?: CatalogSnapshot;

package/durable-memory/model_selection.md

@@ -10,15 +10,20 @@ For `.lmctl` teamfile compatibility mode:
   This REPLACED the static tested-model lists that used to live in this
   document (2026-09-24) — hand-copied lists contradicted the catalog.
 
-**Best-effort contract (operator, 2026-09-25): lint is advisory and is NOT
-claimed to be 100% up to date.** Checks can lag provider reality in BOTH
-directions — a model lint warns about may have just been added upstream, and
-a model lint accepts may have just been retired. Every model check is a
-warning, never an error (`lint --strict` is the operator's explicit
-promotion, not the default). The runtime stance for anything unrecognized
-or out of date is always: "not recognized — could still be valid; no cost
-information," never a failure. Cost is equally best-effort (n/a with a
-reason, never a guessed price).
+**Best-effort contract (operator, 2026-09-25, hardened 2026-09-29): lint is
+advisory and is NOT claimed to be 100% up to date.** Checks can lag provider
+reality in BOTH directions — a model lint warns about may have just been
+added upstream, and a model lint accepts may have just been retired. Every
+model check is a warning, never an error, full stop: lint has exactly two
+outcomes (ok / warning) and always exits 0 on warnings-only. There used to be
+a `--strict` flag that could promote warnings to a failing exit code; the
+operator removed it entirely (2026-09-29: "no need to give users the choice
+with no obvious value") — lmctl decides the scoping, not the caller. Exit 1
+is reserved for genuine validation errors (a malformed teamfile, an
+unparseable member line), never for a warning. The runtime stance for
+anything unrecognized or out of date is always: "not recognized — could
+still be valid; no cost information," never a failure. Cost is equally
+best-effort (n/a with a reason, never a guessed price).
 - `codex` and `agy` model validation queries each provider's own live
   catalog command (`codex debug models`, `agy models`) instead of a
   hand-copied list — see their `## Codex` / `## Antigravity` sections

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lmctl-ai/lmctl",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "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",