@balise.dev/cli 0.1.3 → 0.3.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 +19 -0
- package/dist/index.js +1038 -265
- package/package.json +4 -1
package/README.md
CHANGED
|
@@ -61,6 +61,25 @@ Tokens are written to a plaintext JSON file with restrictive permissions:
|
|
|
61
61
|
|
|
62
62
|
If you need OS-keychain-grade protection, set `BALISE_CREDENTIALS_FILE` to a path on an encrypted volume, or feed `BALISE_TOKEN` from your existing secret manager.
|
|
63
63
|
|
|
64
|
+
## Build-time policy patterns
|
|
65
|
+
|
|
66
|
+
`balise init` ships with two compile-time pattern lists baked into the bundle via tsup `define`:
|
|
67
|
+
|
|
68
|
+
| Env var (build) | Used for | SSOT contract |
|
|
69
|
+
|---|---|---|
|
|
70
|
+
| `BALISE_BAN_PATTERNS` | Directories the extractor will never read (`.git`, `node_modules`, …). Displayed as 🔒 read-only in the `balise init` ignore tree. | **MUST** match the worker-side env var of the same name (read by `balise_mcp/diff_loc.py`). Changing one without the other breaks the SSOT verrou between credit estimate and what the agent sees. |
|
|
71
|
+
| `BALISE_DEFAULT_PATTERNS` | Globs pre-checked-out in the ignore tree as a sensible default (lockfiles, minified assets, snapshots, …). User remains free to scan them — they just pay the tokens. | CLI-only. |
|
|
72
|
+
|
|
73
|
+
Override at build time:
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
BALISE_BAN_PATTERNS=.git,node_modules,dist \
|
|
77
|
+
BALISE_DEFAULT_PATTERNS='*.lock,*.min.js' \
|
|
78
|
+
npm run build
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
The defaults baked when these env vars are unset are visible in `cli/tsup.config.ts`.
|
|
82
|
+
|
|
64
83
|
## Dev
|
|
65
84
|
|
|
66
85
|
```bash
|