@pome-sh/checks 0.3.4 → 0.3.5

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @pome-sh/checks
 
+## 0.3.5 — 2026-08-23
+
+**No consumer-visible change.** Internal tracker ids were removed from source
+comments, JSDoc and test names across the workspace, and the comment blocks
+touched in test files were cut to the claim they document. Prose only: no
+export, schema, tool, route, status code or response body moved.
+
 ## 0.3.4 — 2026-08-23
 
 **No consumer-visible change.** Internal tracker ids were removed from comments

package/dist/_types/sdk/db.d.ts

@@ -39,6 +39,6 @@ export interface OpenTwinDatabaseOptions {
  * Open a twin database with the pome pragma set applied:
  * `busy_timeout = 5000`, `journal_mode = WAL` (file-backed), and
  * `foreign_keys = ON` — the exact pragmas every twin's hand-rolled db.ts
- * applied before F-681 centralized them.
+ * applied before centralized them.
  */
 export declare function openTwinDatabase(path?: string, options?: OpenTwinDatabaseOptions): TwinDatabase;

package/dist/_types/twin-github/src/seed.d.ts

@@ -116,7 +116,7 @@ export type ParsedGitHubStateSeed = z.output<typeof seedSchema>;
 export declare function parseSeed(input: unknown): ParsedGitHubStateSeed;
 /**
  * Boot-time seed loader: prefer `POME_SEED_JSON` env (set by the cloud
- * control-plane from the CLI-supplied scenario seed; see FDRS-353) and
+ * control-plane from the CLI-supplied scenario seed; ) and
  * fall back to `defaultSeedState()` when the env is absent. Throws on
  * malformed JSON or schema-invalid seed, so a misconfigured cloud
  * deploy fails the twin server's healthz instead of silently booting

package/dist/_types/twin-github/src/types.d.ts

@@ -87,7 +87,7 @@ export type SeedRepository = {
 };
 /**
  * A conversation comment on an issue OR a pull request — one shape, because
- * they are one table and one route on GitHub too (F-1151).
+ * they are one table and one route on GitHub too.
  */
 export type SeedComment = {
     body: string;
@@ -245,7 +245,7 @@ export type ReleaseRow = {
     prerelease: 0 | 1;
     author_login: string;
     created_at: string;
-    /** F-1459 — GitHub's release `updated_at`. Equal to `created_at` on a release
+    /** GitHub's release `updated_at`. Equal to `created_at` on a release
      * that has never been edited, which is every release this twin serves: it has
      * no release-update route. */
     updated_at: string;

package/dist/_types/twin-gmail/src/check-state.d.ts

@@ -2,7 +2,7 @@ import { type CheckOutcome } from "../../sdk/checks.js";
 /** A resolver must be able to say WHY it found nothing: the ways of finding
  *  nothing get different verdicts. Same shape and same reason as twin-github's.
  *
- *  F-1197 added the pointers, also twin-github's: `path` is where the resolution
+ * The pointers follow twin-github's: `path` is where the resolution
  *  landed, `searched` is the collection a failed lookup scanned. Both optional on
  *  the missing arm because gmail's commonest refusal is `state_incomplete` — the
  *  collection is absent from the export entirely, so there is nowhere to point
@@ -110,7 +110,7 @@ export declare function resolveMessage(state: GmailCheckState, id: string): Reso
  * regardless.
  *
  * ⚠️ THAT FALLBACK IS SYSTEM-LABELS-ONLY, and the sentence above used to stop
- * short of saying so, which is why the gap read as intentional (F-1441). It
+ * short of saying so, which is why the gap read as intentional. It
  * holds when `id === name` — `INBOX`, `UNREAD`, `STARRED`. A USER label's
  * minted id differs from its display name by construction (the default seed
  * ships `{ id: "Label_follow_up", name: "Follow Up" }`), so with `labels`
@@ -121,7 +121,7 @@ export declare function resolveMessage(state: GmailCheckState, id: string): Reso
  * indistinguishable from "the label was never applied". **Every caller must
  * decide what an absent or capped `labels` collection means before calling**.
  *
- * THERE ARE THREE CALLERS, not the two F-1441 counted, and the third is in this
+ * THERE ARE THREE CALLERS, not the two first counted, and the third is in this
  * very file:
  *   * `gmail.mailbox-label-count` and `gmail.one-message-per-recipient` in
  *     check-messages.ts REFUSE — `state_incomplete` / `collection_truncated` —
@@ -133,7 +133,7 @@ export declare function resolveMessage(state: GmailCheckState, id: string): Reso
  *     the direction is safe — but safe-by-polarity is how this class survives
  *     review, so it is measured rather than assumed. `section-read-sweep.test.ts`
  *     in @pome-sh/checks deletes `labels` from that check's own passing world on
- *     every run and asserts the verdict MOVES; before F-1437 it did not, because
+ * every run and asserts the verdict MOVES; before it did not, because
  *     that world minted the label with `id === name` and the fallback above
  *     answered the join unaided.
  *
@@ -166,7 +166,7 @@ export declare function resolveLabelByName(state: GmailCheckState, name: string)
  * the caller decides whether that emptiness is answerable.
  *
  * ⚠️ Same shape as `labelIdsFor`, same rule, and the reason is written down
- * rather than left to be rediscovered (F-1441): `state.messages ?? []` cannot
+ * rather than left to be rediscovered: `state.messages ?? []` cannot
  * tell an absent collection from one that holds no match, so this function
  * cannot refuse either. It is safe TODAY only because its sole caller
  * null-checks `final.messages` first (`check-drafts.ts:63`) — safe-by-caller,

package/dist/_types/twin-linear/src/check-state.d.ts

@@ -69,7 +69,7 @@ export type Resolved<T> = {
     skip: boolean;
     searched?: string;
 };
-/** The exported collections a pointer can address (F-1197). Named because seven
+/** The exported collections a pointer can address. Named because seven
  *  declarations reach for them. */
 export declare const ISSUES_PATH: string;
 export declare const COMMENTS_PATH: string;
@@ -78,7 +78,7 @@ export declare const WORKFLOW_STATES_PATH: string;
 export declare const USERS_PATH: string;
 /**
  * A pointer at `key` on the row `base` addresses, falling back to the row when
- * the export does not carry that key (F-1197).
+ * the export does not carry that key.
  *
  * The fallback is the whole point and it is not defensive padding. An UNSET
  * estimate and an ABSENT assignee are both real, common, and exactly the
@@ -90,7 +90,7 @@ export declare const USERS_PATH: string;
 export declare function fieldPath(base: string, row: object, key: string): string;
 /** The one place an unresolved selector becomes an outcome.
  *
- *  F-1197 — it also carries the citation, so the rule "a refusal names where it
+ *  It also carries the citation, so the rule "a refusal names where it
  *  looked" is written once rather than at fourteen call sites. */
 export declare function unresolved(r: {
     missing: string;

package/dist/_types/twin-linear/src/types.d.ts

@@ -6,10 +6,10 @@ export type LinearTokenActorType = "user" | "app";
 export type LinearIssuePriority = 0 | 1 | 2 | 3 | 4;
 /** Linear's `AgentActivityType` enum, member-for-member — the `content` discriminator. */
 export type LinearAgentActivityType = "thought" | "elicitation" | "action" | "response" | "error" | "prompt";
-/** Linear's `AgentActivitySignal` enum, member-for-member (F-1176). */
+/** Linear's `AgentActivitySignal` enum, member-for-member. */
 export type LinearAgentActivitySignal = "stop" | "continue" | "auth" | "select";
 /**
- * Linear's `AgentActivityContent` union, member-for-member (F-1176).
+ * Linear's `AgentActivityContent` union, member-for-member.
  *
  * Upstream this is a real GraphQL union discriminated on `type`, whose six
  * members are `AgentActivity{Thought,Action,Response,Elicitation,Error,Prompt}
@@ -42,7 +42,7 @@ export type LinearAgentActivityContent = {
     result?: string | null;
     resultData?: unknown;
 };
-/** Linear's `AgentSessionStatus` enum, member-for-member (F-1172). */
+/** Linear's `AgentSessionStatus` enum, member-for-member. */
 export type LinearAgentSessionStatus = "pending" | "active" | "awaitingInput" | "complete" | "error" | "stale";
 /** One entry of Linear's `AgentSession.externalUrls` JSON payload. */
 export type LinearAgentSessionExternalUrl = {

package/dist/_types/twin-slack/src/check-state.d.ts

@@ -31,7 +31,7 @@ export interface SlackCheckState {
  *  able to say WHY it found nothing, because the three ways of finding nothing
  *  get three different verdicts.
  *
- *  F-1197 added the pointers, and they follow twin-github exactly: `path` is the
+ * The pointers follow twin-github exactly: `path` is the
  *  address the resolution walked to, `searched` is the collection a failed
  *  lookup scanned. `searched` is optional because `state_incomplete` means the
  *  export carried no `channels` key at all — there is genuinely nowhere to
@@ -62,7 +62,7 @@ export declare function missSkip(miss: {
 /**
  * Is this a channel a non-member of the workspace could read?
  *
- * `null` means UNDECLARED, and it is not a convenience. F-1028: guessing
+ * `null` means UNDECLARED, and it is not a convenience. Guessing
  * "public" false-fails a correct agent whose hit was in a private channel;
  * guessing "private" false-passes a leaking one. Neither is permitted, so the
  * criterion leaves the denominator instead.
@@ -84,7 +84,7 @@ export declare function isPublicChannel(channel: SlackCheckStateChannel): boolea
 export declare function publicChannels(state: SlackCheckState): Resolved<SlackCheckStateChannel[]>;
 /**
  * The channel a criterion names, with the three outcomes a negative criterion
- * must tell apart (F-1028, carried over verbatim from the cloud's rule):
+ * must tell apart (carried over verbatim from the cloud's rule):
  *   - no `channels` key at all → `state_incomplete`; we cannot attest a negative
  *   - present but this channel absent → `channel_not_found`; a wrong agent over a
  *     partial export must not score a free pass

package/dist/_types/twin-slack/src/types.d.ts

@@ -45,7 +45,7 @@ export type SeedEmoji = {
     alias?: string;
 };
 /**
- * A file present in the world before the agent touches it (F-1509).
+ * A file present in the world before the agent touches it.
  *
  * Until this existed the `files` table had exactly ONE writer — `filesUpload`,
  * a mutation — so every read of `files.list` / `files.info` against a freshly

package/dist/_types/twin-stripe/src/check-state.d.ts

@@ -51,7 +51,7 @@ export interface StripeCheckState {
  *  resolver must be able to say WHY it found nothing, because the ways of
  *  finding nothing get different verdicts.
  *
- *  F-1197 added the pointers, also twin-github's: `path` is where the resolution
+ * The pointers follow twin-github's: `path` is where the resolution
  *  landed, `searched` is the collection a failed lookup scanned — absent when the
  *  export carried no such collection, because a citation that resolves to
  *  nothing is the affordance-to-nowhere that ticket removes. */
@@ -62,7 +62,7 @@ export type Resolved<T> = {
     missing: string;
     searched?: string;
 };
-/** The exported collections a pointer can address (F-1197). Named because seven
+/** The exported collections a pointer can address. Named because seven
  *  declarations reach for them, and because these are WIRE names — `refunds`,
  *  not `refund_rows` — which is exactly the distinction this file's header
  *  spends thirty lines on. A literal typed out at each call site is a chance to

package/dist/_types/twin-stripe/src/seed.d.ts

@@ -189,10 +189,10 @@ export declare const seedSchema: z.ZodObject<{
 export declare function parseSeed(input: unknown): SeedState;
 /**
  * Boot-time seed loader: prefer `POME_SEED_JSON` env (set by the cloud
- * control-plane from the CLI-supplied scenario seed; see FDRS-353 +
- * FDRS-361) and fall back to `defaultSeed()` when the env is absent.
+ * control-plane from the CLI-supplied scenario seed;  +
+ * and fall back to `defaultSeed()` when the env is absent.
  *
- * Unwrap contract (FDRS-365 + FDRS-369): scenarios may send the
+ * Unwrap contract: scenarios may send the
  * canonical wrapped shape `{ stripe: { seed: {...} } }` (what scenario
  * 14 uses) or the flat shape `{ payment_intents: [...], ... }`. We peel
  * `body.stripe?.seed ?? body` so both shapes work end-to-end without

package/dist/_types/wire/index.d.ts

@@ -6,14 +6,14 @@
  * of that union (`otel/`), and the secret redactor applied on the way to disk
  * (`redaction.ts`). Every twin, the sdk, the adapter and the CLI depend on this
  * package; NOTHING ON THIS BARREL knows about sessions, tasks, runs or the
- * cloud REST surface — those live in `cli/src/contract/` (F-942).
+ * cloud REST surface — those live in `cli/src/contract/`.
  *
- * F-1416 NARROWED THAT CLAIM ONCE, and this is the whole of the narrowing: the
+ * THAT CLAIM WAS NARROWED ONCE, and this is the whole of the narrowing: the
  * package now also ships `@pome-sh/wire/run-completeness`, four symbols that
  * read two fields of a `criteria_results` row (`skipped`, `reason`) and return
  * whether a finished run has a verdict to state. That is the one predicate
  * pome-cloud's dashboard and control plane and this repo's CLI all have to
- * agree on, and until F-1416 the CLI's agreement test kept a hand-written copy
+ * agree on, and until the CLI's agreement test kept a hand-written copy
  * of it that went stale green. It is run-ADJACENT, so the sentence above would
  * be false if it said "this package"; it is not run vocabulary, because it
  * names no session, task, run id, REST route or column, imports nothing, and
@@ -23,15 +23,15 @@
  *
  * Three SUBPATH-ONLY surfaces are deliberately absent from this barrel.
  * `@pome-sh/wire/otel/fixtures` (the golden-fixture corpus, a test/dev
- * artifact) and `@pome-sh/wire/correlation` (F-950 — the agent-side
+ * artifact) and `@pome-sh/wire/correlation` (the agent-side
  * AsyncLocalStorage + fetch-patching plumbing that stamps
  * `x-pome-correlation-id`) are absent because only some consumers should pay to
  * LOAD them: importing correlation constructs an AsyncLocalStorage, and no twin
- * is the agent side of that protocol. `@pome-sh/wire/run-completeness` (F-1416)
+ * is the agent side of that protocol. `@pome-sh/wire/run-completeness`
  * is absent for a different reason — SCOPE, not cost. The five twins, the sdk
  * and the adapter import this barrel and not one of them has a run to ask
  * about, so a symbol they cannot use has no business in their namespace, and an
- * opt-in subpath is what makes the F-942 boundary above a thing CI can check.
+ * opt-in subpath is what makes the boundary above a thing CI can check.
  * `test/export-surface.test.ts` pins all three: each subpath's own surface, and
  * its absence from the snapshot below.
  *

package/dist/_types/wire/otel/event-schema.d.ts

@@ -1,5 +1,5 @@
 /**
- * otel/event-schema — the OTel-inclusive event union (M1.1 / FDRS-480).
+ * otel/event-schema — the OTel-inclusive event union (M1.1).
  *
  * `eventSchema` in `recorder-events.ts` is the FROZEN v1 legacy union (the
  * recording-spec contract under the repo's change-lock policy). Rather than
@@ -14,9 +14,9 @@
  * `eventSchema` and recognize `OtelSpanEvent` separately.
  *
  * This union is FORMAT surface and canonical HERE (ownership boundary settled
- * at FDRS-653 — see `./index.ts`). pome-cloud consumes it; its earlier
+ * — see `./index.ts`). pome-cloud consumes it; its earlier
  * cloud-local composition of the same union collapses into this one at the
- * FDRS-654 consumer swap.
+ * the consumer swap.
  */
 import { z } from "zod";
 export declare const otelEventSchema: z.ZodUnion<readonly [z.ZodPipe<z.ZodDiscriminatedUnion<[z.ZodObject<{

package/dist/_types/wire/otel/index.d.ts

@@ -4,12 +4,12 @@
  * Barrel re-export. The golden-fixture corpus under `./fixtures/` is a
  * test/dev artifact and is intentionally NOT re-exported from the public barrel.
  *
- * OWNERSHIP BOUNDARY (settled at FDRS-653; supersedes the earlier
+ * OWNERSHIP BOUNDARY (settled; supersedes the earlier
  * "pome-cloud mirrors this directory verbatim" claim, which no longer held):
  *   - FORMAT schemas are canonical HERE, in `pome-sh/pome-twins`
  *     `@pome-sh/shared-types` v0.5.0+ (now `@pome-sh/wire`): `span-event`, `event-schema`,
  *     `semconv`, `nano`, `project`, `map-span`, and the
- *     `fixtures/` corpus. pome-cloud CONSUMES this surface (FDRS-654 swaps it
+ * `fixtures/` corpus. pome-cloud CONSUMES this surface (the consumer swap it
  *     onto the published package); it does not fork it.
  *   - INGEST-side utilities are cloud-owned consumers and intentionally do NOT
  *     live here: OTLP wire decoding (`decode-otlp.ts`), redaction/allowlist

package/dist/_types/wire/otel/map-span.d.ts

@@ -1,5 +1,5 @@
 /**
- * otel/map-span — pure OTel span → `OtelSpanEvent` mapping (M1.1 / FDRS-480).
+ * otel/map-span — pure OTel span → `OtelSpanEvent` mapping (M1.1).
  *
  * Deterministic: same input → byte-identical event, every run. Has no clock,
  * no randomness; `ts` is derived from the span's start time.

package/dist/_types/wire/otel/nano.d.ts

@@ -1,6 +1,6 @@
 /**
  * otel/nano — uint64 decimal-string arithmetic + nanosecond↔ISO conversion
- * (M1.1 / FDRS-480).
+ * (M1.1).
  *
  * OTLP encodes `*_unix_nano` timestamps as uint64 decimal STRINGS because the
  * values exceed Number.MAX_SAFE_INTEGER. These helpers validate and compare

package/dist/_types/wire/otel/project.d.ts

@@ -1,5 +1,5 @@
 /**
- * otel/project — the single attribute→projection function (M1.1 / FDRS-480).
+ * otel/project — the single attribute→projection function (M1.1).
  *
  * The typed `gen_ai_*` / `http_*` / `url_*` / `server_*` / `error_type` fields
  * on an `OtelSpanEvent` are PROJECTIONS of the verbatim `attributes` bag, never

package/dist/_types/wire/otel/semconv.d.ts

@@ -1,5 +1,5 @@
 /**
- * otel/semconv — pinned OpenTelemetry semantic-convention surface (M1.1 / FDRS-480).
+ * otel/semconv — pinned OpenTelemetry semantic-convention surface (M1.1).
  *
  * The ONE place an upstream spec change is absorbed. Every attribute name the
  * span mapper / shim reads is a constant here; the convention versions are
@@ -24,7 +24,7 @@
  *
  * This module is the canonical home of the pinned OTel convention surface;
  * pome-cloud consumes it as part of `@pome-sh/wire` (ownership
- * boundary settled at FDRS-653 — see `./index.ts`).
+ * boundary settled — see `./index.ts`).
  */
 export declare const OTEL_CORE_SEMCONV_VERSION: "1.41.1";
 export type OtelCoreSemconvVersion = typeof OTEL_CORE_SEMCONV_VERSION;

package/dist/_types/wire/otel/span-event.d.ts

@@ -1,5 +1,5 @@
 /**
- * otel/span-event — the `OtelSpanEvent` Zod schema (M1.1 / FDRS-480).
+ * otel/span-event — the `OtelSpanEvent` Zod schema (M1.1).
  *
  * The canonical internal representation of a single OpenTelemetry span, mapped
  * onto Pome's event union. From M1 on, OTel spans are the canonical model;

package/dist/{chunk-E2AKLQVI.js → chunk-6AXGU7BV.js}

@@ -833,7 +833,7 @@ var toolWasCalled = defineCheck({
   params: { tool: toolActionName },
   substrate: "tape",
   // Nothing in the seed can satisfy it and only the examinee acting can, which
-  // is the whole property: declared, never inferred from the English (F-1070).
+  // is the whole property: declared, never inferred from the English.
   polarity: () => "positive",
   // The action name IS a caller-supplied literal hunted for in a substrate, so
   // it is declared — and the engine's door-side skip matters MORE here than on
@@ -912,7 +912,7 @@ var GITHUB_CHECKS = [
   // that assert about the RUN rather than the world it left behind.
   noUnsupportedEndpoint,
   toolNeverCalled,
-  // F-1338. Adjacent to its prohibition for the reason the two repo-scoped
+  // Adjacent to its prohibition for the reason the two repo-scoped
   // deltas sit together above: an author reaching for one usually wants to see
   // the other, and these two are the same predicate read in opposite
   // directions off one closed set of actions. It is appended rather than
@@ -937,7 +937,7 @@ var seedSchema = z.object({
       color: z.string().default("ededed"),
       description: z.string().default("")
     })).default([]),
-    // F-1500 — `renamed_from` is how a seed expresses a MOVE, and with it the
+    // `renamed_from` is how a seed expresses a MOVE, and with it the
     // `status: "renamed"` the row type has always declared and no world could
     // reach. A seeded branch is created from the default branch and inherits
     // every path, and a plain `files[]` entry can only add or overwrite, so
@@ -983,7 +983,7 @@ var seedSchema = z.object({
         });
       }
     })).default([]),
-    // F-1421 — milestones, tags and releases are repository-level entities the
+    // Milestones, tags and releases are repository-level entities the
     // twin already SERVES (`GET /milestones`, `/tags`, `/releases`,
     // `/releases/latest`, `/releases/tags/:tag`) and the seed could not
     // express. Zod strips unknown keys, so a seed naming one reached the
@@ -1029,7 +1029,7 @@ var seedSchema = z.object({
       labels: z.array(z.string().min(1)).default([]),
       assignees: z.array(z.string().min(1)).default([]),
       // The issue's conversation timeline, served at
-      // `GET /repos/:o/:r/issues/:n/comments` (F-1421). `author` is
+      // `GET /repos/:o/:r/issues/:n/comments`. `author` is
       // seeded honestly rather than taken from the write path, which
       // stamps every comment `pome-agent`: a world in which the agent
       // under test wrote every comment on the issue it is being asked to
@@ -1062,9 +1062,9 @@ var seedSchema = z.object({
         state: z.enum(["error", "failure", "pending", "success"]).default("success"),
         description: z.string().default("")
       })).default([]),
-      // F-1421 — the PR's CONVERSATION timeline. Same table, same route
+      // The PR's CONVERSATION timeline. Same table, same route
       // and same number space as an issue's comments, because GitHub
-      // models a pull request as an issue (F-1151). This is the third
+      // models a pull request as an issue. This is the third
       // thing a reader could call "a comment on the PR" and the seed
       // keeps all three apart: `reviews[].body` is the prose on a review
       // verdict, `review_comments[]` below is anchored to a file and
@@ -1073,7 +1073,7 @@ var seedSchema = z.object({
         body: z.string().min(1),
         author: z.string().min(1).optional()
       })).default([]),
-      // F-1421 — inline review comments, served at
+      // Inline review comments, served at
       // `GET /repos/:o/:r/pulls/:n/comments`. Seeded through the domain's
       // own write path, so `path` must name a file the PR changes and
       // `line` must exist in it: a seeded review comment is one

package/dist/{chunk-ZXS3NTSQ.js → chunk-OEGRXQ6W.js}

@@ -180,7 +180,7 @@ var noReactionAdded = defineCheck({
   polarity: () => "negative",
   // The reaction name, because that is the literal this predicate compares
   // against `reactions[].name` — the line below has said so since the check
-  // shipped, and this field said `null` anyway (F-1157).
+  // shipped, and this field said `null` anyway.
   //
   // It is the sharpest case in the vocabulary for why that mattered. A NEGATIVE
   // criterion asserting a scanned literal is absent reads a redactor's work as
@@ -380,7 +380,7 @@ var seedSchema = z.object({
       reactions: z.array(z.object({ name: z.string(), user: z.string() })).default([])
     })).default([])
   })).default([]),
-  // F-1509. Files present in the world before the agent runs. `user` and
+  // Files present in the world before the agent runs. `user` and
   // `channels` are seed HANDLES (a user/channel `name`) or ids — the same
   // currency `channels[].members` and `channels[].messages[].user` already use.
   files: z.array(z.object({

package/dist/github.js

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

package/dist/index.js

@@ -1,12 +1,12 @@
 import './chunk-ZXE6LAM3.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 { GITHUB_CHECKS } from './chunk-6AXGU7BV.js';
+export { GITHUB_CHECKS, defaultSeedState as defaultGitHubSeed, seedSchema as githubSeedSchema, parseSeed as parseGitHubSeed } from './chunk-6AXGU7BV.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';
 export { LINEAR_CHECKS, defaultSeedState as defaultLinearSeed, linearSeedSchema, parseSeed as parseLinearSeed } from './chunk-THOSO63W.js';
-import { SLACK_CHECKS } from './chunk-ZXS3NTSQ.js';
-export { SLACK_CHECKS, defaultSeedState as defaultSlackSeed, parseSeed as parseSlackSeed, seedSchema as slackSeedSchema } from './chunk-ZXS3NTSQ.js';
+import { SLACK_CHECKS } from './chunk-OEGRXQ6W.js';
+export { SLACK_CHECKS, defaultSeedState as defaultSlackSeed, parseSeed as parseSlackSeed, seedSchema as slackSeedSchema } from './chunk-OEGRXQ6W.js';
 import { STRIPE_CHECKS } from './chunk-XOUAZPNB.js';
 export { STRIPE_CHECKS, defaultSeed as defaultStripeSeed, parseSeed as parseStripeSeed, seedSchema as stripeSeedSchema } from './chunk-XOUAZPNB.js';
 export { REDACTION_PLACEHOLDER, VACUITY_SENTINEL, VACUITY_SENTINEL_NUMBER, VACUITY_SENTINEL_SNAKE, checkNearMissPattern, checkPattern, checksDigest, childStatePath, defineCheck, isRedacted, oneOf, parseCheck, probeDiscrimination, probeRedactionSurvival, probeStateCitation, renderCheck, repoRef, resolveStatePath, statePath, templateSlots } from './chunk-W2JNYULF.js';

package/dist/slack.js

@@ -1,2 +1,2 @@
-export { SLACK_CHECKS, defaultSeedState, parseSeed, seedSchema } from './chunk-ZXS3NTSQ.js';
+export { SLACK_CHECKS, defaultSeedState, parseSeed, seedSchema } from './chunk-OEGRXQ6W.js';
 import './chunk-W2JNYULF.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pome-sh/checks",
-  "version": "0.3.4",
+  "version": "0.3.5",
   "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",