@pome-sh/checks 0.2.1 → 0.3.0

package/CHANGELOG.md

@@ -1,5 +1,50 @@
 # @pome-sh/checks
 
+## 0.3.0 — 2026-08-14
+
+**`` `add_issue_comment` was called `` binds, and the github tape slot widens
+from two names to three** (F-1521). No check is added or removed —
+`GITHUB_CHECKS` stays at sixteen — but `github.tool-was-called` and
+`github.tool-never-called` share one slot type generated from the twin's
+`TAPE_ASSERTABLE_TOOLS`, so both of their compiled patterns move:
+
+```
+before  ^`((?:create_commit_status|create_check_run))` was (never )?called$
+after   ^`((?:create_commit_status|create_check_run|add_issue_comment))` was (never )?called$
+```
+
+**Minor, and the pattern is the whole reason.** `checksDigest` hashes
+`{id, substrate, pattern}` per check, so a widened alternation moves the digest
+and every pin must catch up:
+
+```
+before  sha256:3e426067133135045418b88dedaf98050f19e58610481799d1f81a38ecf3adfc
+after   sha256:fcaef7734f88d874e1e0da85eeab06ff6521e6036134d78c8112a9ed62ad7cd2
+```
+
+Until the cloud pins this version, `pome checks add --check
+github.tool-was-called` reports `this CLI has it, the cloud does not` and
+declines to write the new sentence — the same handshake 0.2.0 describes,
+working as designed rather than a defect. Nothing that binds today changes
+verdict: every sentence that parsed against the old pattern parses against the
+new one, and both predicates read `event.tool` exactly as before.
+
+**Why one name and not F-1342's sweep.** M0's slice task needs to prove the
+examinee actually left its comment, and only a positive tape assertion can say
+so — a prohibition cannot separate *"held the line"* from *"never showed up"*.
+The vocabulary for that shipped in 0.2.0; the sentence the slice wanted did not
+bind, because the twin's REST comment route was unstamped and the stamping
+invariant refuses positive assertions on unstamped names. So one route was
+stamped and its both-doors probe paid for. `merge_pull_request` and
+`add_issue_labels` are still unstamped and their sentences still correctly refuse
+to bind, in both directions.
+
+**Consumers pinning `@pome-sh/sandbox-domains` must move both together.** That
+package re-exports the same `GITHUB_CHECKS` tuple, and
+`checks-package-drift.test.ts` demands the two declare an identical binding
+surface per twin — so this release and its `@pome-sh/sandbox-domains` sibling are
+cut from one `main` commit and must be pinned as a pair.
+
 ## 0.2.1 — 2026-08-13
 
 No change to the vocabulary: every check id, template, polarity and seed schema

package/dist/{chunk-XTSASWF4.js → chunk-E2AKLQVI.js}

@@ -2,7 +2,11 @@ import { oneOf, defineCheck, repoRef, VACUITY_SENTINEL_NUMBER, childStatePath, V
 import { z } from 'zod';
 
 // ../twin-github/dist/src/tape-assertable-tools.js
-var TAPE_ASSERTABLE_TOOLS = ["create_commit_status", "create_check_run"];
+var TAPE_ASSERTABLE_TOOLS = [
+  "create_commit_status",
+  "create_check_run",
+  "add_issue_comment"
+];
 
 // ../twin-github/dist/src/check-params.js
 var entityNumber = (name) => ({
@@ -787,7 +791,7 @@ var toolNeverCalled = defineCheck({
   // that a verified fact rather than an assumption.
   subject: (args) => args.tool,
   // Null, and admitted in `HONEST_NULL_MUTANTS`. The only slot is a closed set,
-  // so there is no value guaranteed to be false: a mutant naming the OTHER
+  // so there is no value guaranteed to be false: a mutant naming ANOTHER
   // assertable action asserts something that may well also be true, and a value
   // outside the set does not re-bind at all — which reads as "the verdict moved"
   // and would bless the very criterion the probe exists to catch.
@@ -837,9 +841,9 @@ var toolWasCalled = defineCheck({
   // nothing, i.e. failing an agent that did the work.
   subject: (args) => args.tool,
   // Null, and admitted in `HONEST_NULL_MUTANTS`. Same closed-set argument as the
-  // sibling: the only substitutable value is the OTHER assertable action, which
-  // an agent may well have called too, and a value outside the set does not
-  // re-bind at all.
+  // sibling: every substitutable value is ANOTHER assertable action, which an
+  // agent may well have called too, and a value outside the set does not re-bind
+  // at all.
   vacuityMutant: () => null,
   // A POSITIVE check, so the passing world is the one where the action WAS
   // called. The failing world is deliberately NOT an empty tape: `[]` fails

package/dist/github.js

@@ -1,2 +1,2 @@
-export { GITHUB_CHECKS, defaultSeedState, parseSeed, seedSchema } from './chunk-XTSASWF4.js';
+export { GITHUB_CHECKS, defaultSeedState, parseSeed, seedSchema } from './chunk-E2AKLQVI.js';
 import './chunk-W2JNYULF.js';

package/dist/index.js

@@ -1,6 +1,6 @@
 import './chunk-ZXE6LAM3.js';
-import { GITHUB_CHECKS } from './chunk-XTSASWF4.js';
-export { GITHUB_CHECKS, defaultSeedState as defaultGitHubSeed, seedSchema as githubSeedSchema, parseSeed as parseGitHubSeed } from './chunk-XTSASWF4.js';
+import { GITHUB_CHECKS } from './chunk-E2AKLQVI.js';
+export { GITHUB_CHECKS, defaultSeedState as defaultGitHubSeed, seedSchema as githubSeedSchema, parseSeed as parseGitHubSeed } from './chunk-E2AKLQVI.js';
 import { GMAIL_CHECKS } from './chunk-KTTJCEDH.js';
 export { GMAIL_CHECKS, defaultSeedState as defaultGmailSeed, gmailSeedSchema, parseSeed as parseGmailSeed } from './chunk-KTTJCEDH.js';
 import { LINEAR_CHECKS } from './chunk-THOSO63W.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pome-sh/checks",
-  "version": "0.2.1",
+  "version": "0.3.0",
   "description": "Pome's grading vocabulary — the check declarations, seed schemas and default seeds of all five digital twins, plus the check DSL they are written in. Declarations only: no twin server, no database, no routes, no tools.",
   "private": false,
   "type": "module",