@withgauge/cli 0.15.0 → 0.17.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.
Files changed (3) hide show
  1. package/README.md +66 -3
  2. package/dist/index.js +539 -394
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -181,7 +181,25 @@ Paths are repository-relative, case-sensitive globs; matching any pattern runs
181
181
  the checks. `**` matches nested directories, including hidden files. Use 1–32
182
182
  patterns; exclusions (`!`) are not supported. Changes to `gauge.json` or your
183
183
  configured case paths always count. Deleted files and both names of renamed
184
- files are included. Without `checks`, every eligible PR update runs as before.
184
+ files are included. Without root `checks`, every eligible PR update reaches case
185
+ selection.
186
+
187
+ With CLI 0.16.0 or later, a case can narrow its own automatic PR triggers in its
188
+ Markdown frontmatter (alongside its other `config` settings):
189
+
190
+ ```yaml
191
+ config:
192
+ agents:
193
+ - agent: CODEX_CLI
194
+ checks:
195
+ paths: ["cli/**", "packages/shared/**"]
196
+ ```
197
+
198
+ Root `checks.paths`, when present, must match first. The App then runs matching
199
+ cases and all cases without a filter. Changes to `gauge.json` select every case;
200
+ editing a case selects that case regardless of its filter. If no cases match,
201
+ the check is skipped before preparing inputs or reserving credits. `config.inputs`
202
+ only chooses inputs; it does not define change triggers.
185
203
 
186
204
  The first check uses the PR diff. After a passing evaluation, later updates
187
205
  compare against that evaluated commit, so unrelated follow-up edits can skip.
@@ -254,8 +272,8 @@ They are fetched live rather than snapshotted. See the [preview source examples
254
272
  limitations](../specs/docs-web-inputs.md), including Astro's existing bot comment.
255
273
 
256
274
  Editor schemas are published at
257
- `https://agents.withgauge.com/schemas/gauge/v2.4.0/gauge.json` and
258
- `https://agents.withgauge.com/schemas/gauge/v2.4.0/case.json`. Associate them in editor
275
+ `https://agents.withgauge.com/schemas/gauge/v2.6.0/gauge.json` and
276
+ `https://agents.withgauge.com/schemas/gauge/v2.6.0/case.json`. Associate them in editor
259
277
  settings; `gauge.json` does not accept a `$schema` field. These release URLs are
260
278
  immutable. Update earlier pilot configs by moving workflows into input sources,
261
279
  replacing `use` with input `type` and `path`/`paths`, and moving cases into
@@ -418,3 +436,48 @@ stored credentials (useful in CI). Exit codes: `0` ok · `1` error ·
418
436
  ## Support
419
437
 
420
438
  Questions or problems: [support@withgauge.com](mailto:support@withgauge.com).
439
+
440
+
441
+ ### Git-authored Agent Preference
442
+
443
+ A committed Markdown case may declare `preference` instead of `criteria`.
444
+ Use exactly one; the Markdown body is always the coding agent's user request.
445
+
446
+ ```markdown
447
+ ---
448
+ preference:
449
+ kind: open-ended
450
+ config:
451
+ agents:
452
+ - agent: CODEX_CLI
453
+ sampleCount: 5
454
+ inputs: [docs]
455
+ ---
456
+
457
+ I need product analytics for a small SaaS application.
458
+ We need funnels, retention analysis, and EU data residency.
459
+ What should we use?
460
+ ```
461
+
462
+ Here `docs` names an input declared in `gauge.json`. Existing repository/persona
463
+ settings and automatic path filters apply unchanged. Add `branded: true` when an
464
+ open-ended prompt names a brand. For a comparison, use:
465
+
466
+ ```yaml
467
+ preference:
468
+ kind: head-to-head
469
+ brandA: PostHog
470
+ brandB: Amplitude
471
+ ```
472
+
473
+ Write both brands in the prompt itself; metadata is only for analysis and never
474
+ rewrites the task. `gauge evals verify`, `plan`, and `run` support mixed experience
475
+ and preference suites. These fields require the CLI version containing this
476
+ feature; CLI 0.16.0 and earlier reject them.
477
+
478
+ Preference uses the existing app analyst: ranked picks for open-ended cases,
479
+ and a winner (or neither) for head-to-head. Results are advisory. Preference-only
480
+ GitHub checks finish neutral; experience criteria still gate mixed suites.
481
+ `gauge run-requests wait` exits successfully for `MEASURED` or `PASSED`;
482
+ input, execution, and analysis errors remain errors. Results describe the
483
+ candidate revision and do not infer a base/head delta.