@trazum/cli 1.60.1 → 1.60.2

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@trazum/cli",
3
- "version": "1.60.1",
3
+ "version": "1.60.2",
4
4
  "description": "Trazum CLI: find where your LLM bill goes, price every finding per month, and enforce token budgets in CI.",
5
5
  "license": "MIT",
6
6
  "author": "David Mu\u00f1oz Rey",
@@ -37,7 +37,7 @@
37
37
  "prepublishOnly": "npm run build && npm test"
38
38
  },
39
39
  "dependencies": {
40
- "@trazum/core": "1.60.1"
40
+ "@trazum/core": "1.60.2"
41
41
  },
42
42
  "devDependencies": {
43
43
  "@types/node": "^26.2.0",
package/src/index.ts CHANGED
@@ -6810,14 +6810,19 @@ async function commandProfile(
6810
6810
  JSON.stringify(
6811
6811
  {
6812
6812
  /**
6813
- * The contract version, documented in docs/json-output.md and
6814
- * enforced by json-contract.test.js. It changes only when a
6815
- * field's meaning changes or one is removed — new findings arrive
6816
- * as new keys, so a consumer that ignores unknown ones keeps
6817
- * working. Without it, every dashboard built on this output has to
6818
- * guess whether a missing key means "old Trazum" or "no data".
6813
+ * `schemaVersion` arrives inside `report` now, and that is the point.
6814
+ *
6815
+ * It used to be stamped here, which made the profile the one contract
6816
+ * of the ten whose version existed only if you went through this
6817
+ * command. `docs/format.md` says every document carries it and
6818
+ * `conform` rejects one that does not, so a connector author using
6819
+ * `@trazum/core` produced a profile this tool refuses.
6820
+ *
6821
+ * The contract is documented in docs/json-output.md and enforced by
6822
+ * json-contract.test.js. It changes only when a field's meaning
6823
+ * changes or one is removed — new findings arrive as new keys, so a
6824
+ * consumer that ignores unknown ones keeps working.
6819
6825
  */
6820
- schemaVersion: 1,
6821
6826
  ...report,
6822
6827
  cache: cacheEconomics(report.total),
6823
6828
  cacheByLabel: report.byLabel.map((r) => ({