@pome-sh/cli 0.35.0 → 0.35.1

package/assets/demo/first-run-demo.md

@@ -4,15 +4,38 @@
 The packaged `npx @pome-sh/cli demo` task. This markdown is the
 CANONICAL source of the demo task content: the cloud's server-owned judge
 definition (pome-cloud apps/control-plane/src/lib/demo.ts,
-DEMO_TASK_DEFINITIONS["first-run-demo"]) is regenerated FROM this file — the
-judge scores the server copy, never a client-supplied body, so the two must
-stay in lockstep. Changing the prompt / expected behavior / criteria here
-without regenerating the server definition means the cloud judges a
-different task than the one the bundled agent ran.
+DEMO_TASK_DEFINITIONS["first-run-demo"]) mirrors this file — the judge scores
+the server copy, never a client-supplied body, so the two must stay in
+lockstep. Changing the prompt / expected behavior / criteria here without
+updating the server definition means the cloud judges a different task than
+the one the bundled agent ran.
+
+MIRROR IT BY HAND. There is no generator and no gate — F-1752 is the ticket to
+close that, and until it lands nothing but a reviewer notices a half-done sync.
 
 The three tools the bundled demo agent exposes (src/demo/agent.ts) are the
 contract this task is written against: list_open_issues, add_label,
 comment_on_issue.
+
+THE `[code]` ROWS ARE THE DEMO'S SCORE — keep at least one (F-1749). Since the
+narrator flip took `[model]` out of the score denominator, a task declaring
+only `[model]` criteria is not merely unscored: `total_required` is 0, the run
+is not evaluable, and every trial of the advertised zero-auth door reports
+"cloud could not evaluate the trace". Each `[code]` row must also be a sentence
+the published check vocabulary renders — a hand-edited one binds nothing and is
+the same empty denominator in different clothes. Both are asserted in
+test/unit/demo/demo-task-criteria.test.ts, and that the bundled agent's correct
+walk satisfies them in test/e2e/demo-e2e.test.ts.
+
+Neither `[code]` row is true of the seed, which is what keeps them in the
+denominator: the cloud drops a criterion the seed already satisfied
+(`pre-satisfied.ts`), so a prohibition like "No new labels were created in
+acme/api" would leave again and take the fraction with it.
+
+The `[model]` rows stay because they are what the demo exists to SHOW — an
+advisory narrative reading beside a deterministic fraction. They also carry the
+two clauses no declared check can state, "and to no other issue" and "exactly
+one comment", so dropping them would quietly narrow the task.
 -->
 
 ## Prompt
@@ -32,6 +55,8 @@ issue.
 
 ## Success Criteria
 
+- [code] Issue #1 in `acme/api` has exactly one classification label, and it is `bug`
+- [code] A comment containing "POST /orders" exists on issue #1 in `acme/api`
 - [model] The existing `bug` label was applied to the issue reporting the 500 error on POST /orders, and to no other issue.
 - [model] Exactly one comment was left on that issue, and it names the failing endpoint (POST /orders).
 - [model] No other issue was modified and no new label was created.

package/dist/build-info.json

@@ -1,6 +1,6 @@
 {
   "package": "pome-sh",
-  "version": "0.35.0",
-  "git_sha": "d34cec8ae64d618dee1e0121d5284c78177820cc",
-  "build_time": "2026-08-29T16:22:08.716Z"
+  "version": "0.35.1",
+  "git_sha": "05db45b371ec96cd39014583e75de09e4b1b75f4",
+  "build_time": "2026-08-29T17:57:26.354Z"
 }

package/dist/src/cli/main.js

@@ -4641,7 +4641,7 @@ function firstSentence(description) {
 function resolveExampleRef(env = process.env) {
   const override = env.POME_EXAMPLE_REF?.trim();
   if (override) return override;
-  const baked = "d34cec8ae64d618dee1e0121d5284c78177820cc".trim() ;
+  const baked = "05db45b371ec96cd39014583e75de09e4b1b75f4".trim() ;
   return FULL_SHA.test(baked) ? baked : "main";
 }
 function rawUrlFor(example, file, ref) {
@@ -4996,7 +4996,7 @@ var DEFAULT_AGENT_COMMAND = `node ${DEFAULT_AGENT_FILE}`;
 var MANIFEST_SCHEMA_URL = "https://pome.sh/schemas/v1/pome.json";
 var MAX_UNREADABLE_PATHS_SHOWN = 5;
 function readPackageVersion() {
-  if ("0.35.0".length > 0) return "0.35.0";
+  if ("0.35.1".length > 0) return "0.35.1";
   try {
     const here = dirname(fileURLToPath(import.meta.url));
     const candidates = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pome-sh/cli",
-  "version": "0.35.0",
+  "version": "0.35.1",
   "description": "Test AI agents against digital twins of real SaaS APIs. Records tool-call traces and scores them on pome.sh.",
   "keywords": [
     "ai",