luxin-cli 0.2.5 → 0.2.6

package/CHANGELOG.md

@@ -6,6 +6,23 @@ provenance; this file is the human- and agent-readable release map.
 
 ## Unreleased
 
+## 0.2.6 - 2026-08-09
+
+- Release (trust): `create --guide` now says when it cannot price the request it
+  is planning, instead of presenting the model's default-shape quote as the
+  planned debit. `selection.planned_debit_source` reports which of the two you
+  got, and the unpriceable case carries a warning pointing at the dry-run.
+- This closes a gap that was invisible rather than wrong: the hosted API
+  published per-aspect-ratio create debits only when they differed from the
+  quote, so an absent field could mean either "the quote already is the debit"
+  or "this server is older than your CLI". The npm package and the hosted API
+  deploy independently, so that second case is permanent, not a one-off, and it
+  under-quoted silently during any deploy gap or rollback. The API now publishes
+  the debit for every create-capable model (107 of 107 live rows), so absence
+  means exactly one thing, and the CLI now treats it that way.
+- Carries the correction to the 0.2.5 note below: the "known issue" that shipped
+  in the 0.2.5 tarball describes behaviour that does not exist.
+
 ## 0.2.5 - 2026-08-09
 
 - Release (correctness): `edit --guide` selects a model again. It gated on
@@ -19,12 +36,15 @@ provenance; this file is the human- and agent-readable release map.
   `selection.suggested_aspect_ratio` read the same unpublished block and
   returned null on every real video call unless the brief happened to name a
   ratio.
-- Known issue (#2259): `create --guide` can quote a different credit figure than
-  the `--dry-run` it hands you, because it prices the model's catalog default
-  shape rather than the ratio the command actually sends. Measured against the
-  live API: 4 vs 5 with no ratio stated, 4 vs 3 at 16:9. The dry-run figure is
-  the authoritative one; budget from it, not from the guide. Unchanged from
-  0.2.4; the fix landed server-side but not in this package.
+- Correction (added after 0.2.5 shipped): the 0.2.5 tarball carries a "known
+  issue" note claiming `create --guide` can quote a different credit figure than
+  the `--dry-run` it hands you. **That note is wrong and the behaviour it
+  describes does not exist.** It was written from a measurement taken during a
+  deploy-skew window, minutes after the fix merged and before the hosted API had
+  deployed its half. Measured after both halves landed, the guide and the dry-run
+  agree: 5 and 5 with no ratio stated, 3 and 3 at 16:9. #2259 is fixed and
+  closed. Budgeting from the dry-run figure remains sound advice, but it is not a
+  workaround for anything.
 
 ## 0.2.4 - 2026-08-09
 

package/bin/luxin.mjs

@@ -15,7 +15,7 @@ import { Readable } from "node:stream";
 import { pipeline } from "node:stream/promises";
 import os from "node:os";
 
-const VERSION = "0.2.5";
+const VERSION = "0.2.6";
 const PACKAGE_NAME = "luxin";
 const DEFAULT_API_BASE_URL = "https://api.luxin.sh";
 const DEFAULT_DOCS_BASE_URL = "https://luxin.sh";
@@ -2007,6 +2007,16 @@ async function createGuide(args, options = {}) {
           defaultedModelParameters.modelParameters,
           pricingContext,
         );
+  // The quote is not the debit, and against a server that does not publish
+  // debits this CLI cannot compute one -- it has no pricing engine, by design.
+  // Say that plainly instead of letting the caller budget against a number the
+  // product does not charge (#2259, #2272).
+  const plannedDebitUnavailable =
+    selected !== null &&
+    createGuideModelSupportsCreate(selected) &&
+    !createGuideSelectedModelRequiresInputImage(selected) &&
+    !createGuideCanPriceModelParameters(selected) &&
+    !createGuideRegistryPublishesCreditDebit(selected);
   const estimatedCredits = pricing?.credits_required ?? null;
   // The guide publishes what the caller will be charged, never our provider
   // cost. `economics.estimated_usd_per_image` is the hosted charge per image.
@@ -2406,6 +2416,9 @@ async function createGuide(args, options = {}) {
       pricing_source: pricing?.pricing_source ?? null,
       model_parameter_defaults_applied:
         defaultedModelParameters.defaultsApplied,
+      planned_debit_source: plannedDebitUnavailable
+        ? "create_credit_debit_unavailable"
+        : "registry_create_credit_debit",
     },
     blocker,
     guide_warning: guideWarning,
@@ -2443,11 +2456,20 @@ async function createGuide(args, options = {}) {
   for (const field of compactOmittedFields) {
     delete guideData[field];
   }
-  return createGuideSuccess(command, quota?.envelope.actor ?? null, guideData);
+  return createGuideSuccess(
+    command,
+    quota?.envelope.actor ?? null,
+    guideData,
+    plannedDebitUnavailable
+      ? [
+          "create_credit_debit_unavailable: this hosted API does not publish per-aspect-ratio create debits, so the credits above are the model's default-shape quote and may not be what create debits. Run the dry_run command in escape_hatches for the exact figure before budgeting.",
+        ]
+      : [],
+  );
 }
 
-function createGuideSuccess(command, actor, data) {
-  const result = success(command, data);
+function createGuideSuccess(command, actor, data, warnings = []) {
+  const result = success(command, data, warnings);
   result.envelope.actor = actor;
   return result;
 }
@@ -2968,6 +2990,26 @@ function createGuidePricingForModel(model, modelParameters, context = {}) {
 // this CLI has no pricing engine to recompute it -- so the registry publishes
 // the answer and this reads it. Absent field means the quote already is the
 // debit.
+// Does this registry response publish create debits at all?
+//
+// The hosted API and this CLI ship independently, so a client can always be
+// talking to a server older than itself. `create_credit_debit_by_aspect_ratio`
+// is published for EVERY create-capable model precisely so that absence has one
+// meaning -- "this server cannot tell me the debit" -- rather than being
+// confusable with "the debit happens to equal the quote". When it is absent the
+// honest answer is to say so and point at the dry-run, not to present the
+// model's default-shape quote as the planned debit (#2259, #2272).
+function createGuideRegistryPublishesCreditDebit(model) {
+  return (
+    isRecord(model?.economics?.create_credit_debit_by_aspect_ratio) ||
+    isRecord(model?.create_credit_debit_by_aspect_ratio)
+  );
+}
+
+function createGuideModelSupportsCreate(model) {
+  return Array.isArray(model?.supports) && model.supports.includes("create");
+}
+
 function createGuideAspectRatioCreditPricing(model, context) {
   // Both shapes: `GET /v1/models` serves the COMPACT summary, which flattens
   // economics onto the row, and only `?details=true` (or a fixture built from

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luxin-cli",
-  "version": "0.2.5",
+  "version": "0.2.6",
   "description": "Image generation, image editing, video, audio, and image-to-3D for agents, with no API key to obtain first. The agent signs itself up, starts on free preview credits, and gets hosted media URLs, recoverable jobs, and cost receipts.",
   "type": "module",
   "private": false,