@pome-sh/checks 0.3.3 → 0.3.4

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @pome-sh/checks
 
+## 0.3.4 — 2026-08-23
+
+**No consumer-visible change.** Internal tracker ids were removed from comments
+in the shared declaration bundler (`scripts/bundle-declarations.mjs`) and the CI
+gates around it. Comment text only: the bundle's inputs, outputs and export
+surface are unchanged. Listed only because that script sits on a path the next
+release carries.
+
 ## 0.3.3 — 2026-08-22
 
 **No consumer-visible change.** The repo's top-level `examples/` directory is now

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

@@ -8,7 +8,7 @@
  * "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`, `legacy-shim`, and the
+ *     `semconv`, `nano`, `project`, `map-span`, and the
  *     `fixtures/` corpus. pome-cloud CONSUMES this surface (FDRS-654 swaps it
  *     onto the published package); it does not fork it.
  *   - INGEST-side utilities are cloud-owned consumers and intentionally do NOT
@@ -21,5 +21,4 @@ export * from "./nano.js";
 export * from "./project.js";
 export * from "./span-event.js";
 export * from "./map-span.js";
-export * from "./legacy-shim.js";
 export * from "./event-schema.js";

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

@@ -5,8 +5,7 @@
  * on an `OtelSpanEvent` are PROJECTIONS of the verbatim `attributes` bag, never
  * an independent source of truth. This module is the ONE place that derivation
  * lives, so:
- *   - the span mapper (`map-span.ts`) builds projections from `attributes`,
- *   - the legacy shim (`legacy-shim.ts`) builds them the same way, and
+ *   - the span mapper (`map-span.ts`) builds projections from `attributes`, and
  *   - the schema (`span-event.ts`) re-derives them in a `superRefine` and
  *     rejects any event whose typed fields drift from `attributes`
  *     (review finding #4 — projection drift; finding #7 — centralize).

package/package.json

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

package/dist/_types/wire/otel/legacy-shim.d.ts

@@ -1,105 +0,0 @@
-/**
- * otel/legacy-shim — legacy event → `OtelSpanEvent` translation (M1.2 / FDRS-481).
- *
- * The compatibility layer for the transition window: the CLI keeps uploading its
- * current JSONL (no flag day), and OTel-aware downstream (M3 correlation, the
- * native waterfall) reads `OtelSpanEvent`. This shim translates the three legacy
- * variants — `TwinHttpEvent`, `LlmCallEvent`, `ToolUseEvent` — up into spans so
- * legacy and new data share one path.
- *
- * Guarantees:
- *   - **Lossless.** The ENTIRE original record is preserved verbatim as a JSON
- *     string under `attributes["pome.legacy.record_json"]` — serialized from the
- *     raw input BEFORE Zod strips any additive fields (review finding #3). The
- *     mapped fields are ALSO written as canonical OTel attributes, from which
- *     the typed projections are derived by the SAME projector the schema checks.
- *   - **Deterministic.** No clock, no randomness. Same record (+ same `run_id`
- *     option) → byte-identical span, every run.
- *   - **OTel-correct status** (review findings #5/#9). HTTP client spans: 1xx–3xx
- *     leave status UNSET; 4xx/5xx and transport errors are ERROR. (OTel does not
- *     set OK on a merely-successful span.)
- *
- * IDs are namespaced `legacy:<source-id>` so a stored span always declares it
- * originated from a pre-OTel record (the canonical schema accepts either real
- * W3C ids or `legacy:` ids).
- *
- * Pinned convention: the shim targets `OTEL_GENAI_SCHEMA_VERSION` (see `./semconv`).
- */
-import { z } from "zod";
-import { type OtelSpanEvent } from "./span-event.js";
-export declare const LEGACY_SHIM_SEMCONV_VERSION: "1.42.0";
-export declare const LEGACY_ATTR_NAMESPACE: "pome.legacy";
-export declare const LEGACY_ID_PREFIX: "legacy:";
-export declare const shimmableLegacyEventSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
-    ts: z.ZodString;
-    run_id: z.ZodString;
-    twin: z.ZodString;
-    request_id: z.ZodString;
-    correlation_id: z.ZodOptional<z.ZodString>;
-    task_step_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    scenario_step_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    step_id: z.ZodNullable<z.ZodString>;
-    tool_call_id: z.ZodNullable<z.ZodString>;
-    method: z.ZodString;
-    path: z.ZodString;
-    request_body: z.ZodUnknown;
-    request_headers: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodString>>;
-    tool: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    status: z.ZodNumber;
-    response_body: z.ZodUnknown;
-    latency_ms: z.ZodNumber;
-    fidelity: z.ZodEnum<{
-        semantic: "semantic";
-        unsupported: "unsupported";
-    }>;
-    state_mutation: z.ZodBoolean;
-    state_delta: z.ZodNullable<z.ZodObject<{
-        before: z.ZodNullable<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        after: z.ZodNullable<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$strip>>;
-    idempotency_dedupe: z.ZodOptional<z.ZodBoolean>;
-    error: z.ZodNullable<z.ZodString>;
-    kind: z.ZodLiteral<"TwinHttpEvent">;
-    event_id: z.ZodString;
-    parent_event_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    parent_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-}, z.core.$strip>, z.ZodObject<{
-    kind: z.ZodLiteral<"LlmCallEvent">;
-    host: z.ZodString;
-    port: z.ZodNumber;
-    latency_ms: z.ZodNumber;
-    bytes_in: z.ZodNumber;
-    bytes_out: z.ZodNumber;
-    url: z.ZodNullable<z.ZodString>;
-    method: z.ZodNullable<z.ZodString>;
-    status: z.ZodNullable<z.ZodNumber>;
-    model: z.ZodNullable<z.ZodString>;
-    prompt_tokens: z.ZodNullable<z.ZodNumber>;
-    completion_tokens: z.ZodNullable<z.ZodNumber>;
-    cost_usd: z.ZodNullable<z.ZodNumber>;
-    ts: z.ZodString;
-    event_id: z.ZodString;
-    parent_event_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    parent_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-}, z.core.$strip>, z.ZodObject<{
-    kind: z.ZodLiteral<"ToolUseEvent">;
-    tool_use_id: z.ZodString;
-    tool_name: z.ZodString;
-    input: z.ZodUnknown;
-    ts: z.ZodString;
-    event_id: z.ZodString;
-    parent_event_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    parent_id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-}, z.core.$strip>], "kind">;
-export type ShimmableLegacyEvent = z.infer<typeof shimmableLegacyEventSchema>;
-export interface LegacyShimOptions {
-    run_id?: string;
-}
-/**
- * Translate a single legacy `TwinHttpEvent` / `LlmCallEvent` / `ToolUseEvent`
- * into a validated `OtelSpanEvent`.
- *
- * Throws a typed `ZodError` if `rawRecord` is not one of those three shapes,
- * or a plain `Error` if an LLM/tool record is missing the required `run_id`.
- */
-export declare function shimLegacyEventToSpan(rawRecord: unknown, options?: LegacyShimOptions): OtelSpanEvent;