@withgauge/cli 0.16.0 → 0.17.1

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 CHANGED
@@ -14,13 +14,9 @@ gauge orgs use <org> # set your default organization
14
14
 
15
15
  Requires Node.js ≥ 22.12.
16
16
 
17
- Installing or upgrading the CLI also installs the
17
+ To install the optional
18
18
  [`gauge-agents` skill](https://github.com/gauge-sh/gauge-skills/tree/main/gauge-agents)
19
- globally through the `skills` installer, without prompts. It uses the installer's
20
- agent detection for tools such as Codex and Claude Code. Skill installation
21
- needs network access; failures leave the CLI installed and print a retry command.
22
- It is skipped in CI or when `GAUGE_SKIP_SKILL_INSTALL=1` is set. If you install
23
- with `--ignore-scripts`, install the skill manually:
19
+ globally, run:
24
20
 
25
21
  ```sh
26
22
  npx --yes skills@1.5.0 add gauge-sh/gauge-skills --skill gauge-agents --global --yes
@@ -272,8 +268,8 @@ They are fetched live rather than snapshotted. See the [preview source examples
272
268
  limitations](../specs/docs-web-inputs.md), including Astro's existing bot comment.
273
269
 
274
270
  Editor schemas are published at
275
- `https://agents.withgauge.com/schemas/gauge/v2.5.0/gauge.json` and
276
- `https://agents.withgauge.com/schemas/gauge/v2.5.0/case.json`. Associate them in editor
271
+ `https://agents.withgauge.com/schemas/gauge/v2.6.0/gauge.json` and
272
+ `https://agents.withgauge.com/schemas/gauge/v2.6.0/case.json`. Associate them in editor
277
273
  settings; `gauge.json` does not accept a `$schema` field. These release URLs are
278
274
  immutable. Update earlier pilot configs by moving workflows into input sources,
279
275
  replacing `use` with input `type` and `path`/`paths`, and moving cases into
@@ -436,3 +432,48 @@ stored credentials (useful in CI). Exit codes: `0` ok · `1` error ·
436
432
  ## Support
437
433
 
438
434
  Questions or problems: [support@withgauge.com](mailto:support@withgauge.com).
435
+
436
+
437
+ ### Git-authored Agent Preference
438
+
439
+ A committed Markdown case may declare `preference` instead of `criteria`.
440
+ Use exactly one; the Markdown body is always the coding agent's user request.
441
+
442
+ ```markdown
443
+ ---
444
+ preference:
445
+ kind: open-ended
446
+ config:
447
+ agents:
448
+ - agent: CODEX_CLI
449
+ sampleCount: 5
450
+ inputs: [docs]
451
+ ---
452
+
453
+ I need product analytics for a small SaaS application.
454
+ We need funnels, retention analysis, and EU data residency.
455
+ What should we use?
456
+ ```
457
+
458
+ Here `docs` names an input declared in `gauge.json`. Existing repository/persona
459
+ settings and automatic path filters apply unchanged. Add `branded: true` when an
460
+ open-ended prompt names a brand. For a comparison, use:
461
+
462
+ ```yaml
463
+ preference:
464
+ kind: head-to-head
465
+ brandA: PostHog
466
+ brandB: Amplitude
467
+ ```
468
+
469
+ Write both brands in the prompt itself; metadata is only for analysis and never
470
+ rewrites the task. `gauge evals verify`, `plan`, and `run` support mixed experience
471
+ and preference suites. These fields require the CLI version containing this
472
+ feature; CLI 0.16.0 and earlier reject them.
473
+
474
+ Preference uses the existing app analyst: ranked picks for open-ended cases,
475
+ and a winner (or neither) for head-to-head. Results are advisory. Preference-only
476
+ GitHub checks finish neutral; experience criteria still gate mixed suites.
477
+ `gauge run-requests wait` exits successfully for `MEASURED` or `PASSED`;
478
+ input, execution, and analysis errors remain errors. Results describe the
479
+ candidate revision and do not infer a base/head delta.