@trazum/cli 1.8.0 → 1.9.0
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/README.md +29 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -9,11 +9,6 @@ every dependency would be someone else's code reading them too.
|
|
|
9
9
|
Part of [Trazum](https://github.com/Davmunrey/Trazum). For the library, see
|
|
10
10
|
[`@trazum/core`](https://www.npmjs.com/package/@trazum/core).
|
|
11
11
|
|
|
12
|
-
> [!NOTE]
|
|
13
|
-
> **Not published yet.** The command below will not work today — there is no tag
|
|
14
|
-
> and `npm view` returns 404. Run it from source meanwhile:
|
|
15
|
-
> [github.com/Davmunrey/Trazum](https://github.com/Davmunrey/Trazum#getting-started).
|
|
16
|
-
|
|
17
12
|
```bash
|
|
18
13
|
npm install -g @trazum/cli
|
|
19
14
|
```
|
|
@@ -82,6 +77,34 @@ most misleading thing this tool could tell you.
|
|
|
82
77
|
step summary or a pull request comment. There is also a
|
|
83
78
|
[packaged GitHub Action](https://github.com/Davmunrey/Trazum#cli).
|
|
84
79
|
|
|
80
|
+
## The ceiling is not the problem
|
|
81
|
+
|
|
82
|
+
A budget says nothing while a prompt climbs from 800 tokens to 1,900 under a
|
|
83
|
+
limit of 2,000, and that climb is what actually happens to a repository — nobody
|
|
84
|
+
adds a thousand tokens in one commit. A baseline records where you are now:
|
|
85
|
+
|
|
86
|
+
```bash
|
|
87
|
+
trazum baseline prompts/ # writes trazum.baseline.json — commit it
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
```json
|
|
91
|
+
{ "baseline": { "path": "trazum.baseline.json", "maxGrowthTokens": 500 } }
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
`trazum check` then gates on drift away from that record as well as on the
|
|
95
|
+
ceiling, and exits 1 when either fails. One of `maxGrowthTokens` or
|
|
96
|
+
`maxGrowthPct` is required, because a baseline with no threshold gates nothing.
|
|
97
|
+
`--no-baseline` skips it for a run.
|
|
98
|
+
|
|
99
|
+
**The gate is in tokens, not dollars.** Prices move on somebody else's schedule
|
|
100
|
+
and a price change is not a regression in your prompts. The file still records
|
|
101
|
+
the money it was written under and the report compares it — but only while the
|
|
102
|
+
scenario and the pricing date still match, and it says why not when they do not.
|
|
103
|
+
|
|
104
|
+
**Added files count**, or the gate would be defeated by adding a prompt rather
|
|
105
|
+
than editing one. And re-recording is how you accept growth: it is a commit, in
|
|
106
|
+
a diff, where a decision to spend five hundred more tokens belongs.
|
|
107
|
+
|
|
85
108
|
## Did this edit make it worse?
|
|
86
109
|
|
|
87
110
|
```bash
|
|
@@ -103,6 +126,7 @@ gets removed from the pipeline rather than fixed.
|
|
|
103
126
|
"usage": { "model": "claude-opus-5", "callsPerMonth": 50000 },
|
|
104
127
|
"budgets": { "prompts/**": 2000, "prompts/system.txt": 4000 },
|
|
105
128
|
"maxGrowth": 100,
|
|
129
|
+
"baseline": { "path": "trazum.baseline.json", "maxGrowthTokens": 500 },
|
|
106
130
|
"pricing": "./prices.json"
|
|
107
131
|
}
|
|
108
132
|
```
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@trazum/cli",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.9.0",
|
|
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.
|
|
40
|
+
"@trazum/core": "1.9.0"
|
|
41
41
|
},
|
|
42
42
|
"devDependencies": {
|
|
43
43
|
"@types/node": "^26.2.0",
|