@respan/cli 0.14.1 → 0.14.2

package/dist/lib/demo/seed-prompts.js

@@ -9,19 +9,19 @@
 import { DEMO_PROMPTS } from './prompt-fixtures.js';
 /** Prompts in the account whose name exactly matches a demo fixture name.
  *
- * Queried with the `name` `iexact` filter, one query per fixture name. NOTE: the
- * `icontains`/`iexact` filters do NOT OR-match across a multi-value array — a
- * single `value: [a, b, c]` matches nothing — so each name must be queried on
- * its own. Server matching is case-insensitive, so we re-confirm with an exact,
- * case-sensitive match client-side. Returns every match (so duplicates are all
- * found, for clear). */
+ * Queried with the `name` exact-match filter (operator `''`), one query per
+ * fixture name. The backend rejects `iexact` with a 400, and `icontains` does
+ * NOT OR-match across a multi-value array — a single `value: [a, b, c]` matches
+ * nothing — so each name is queried on its own. Matches are re-confirmed
+ * client-side with an exact, case-sensitive comparison. Returns every match (so
+ * duplicates are all found, for clear). */
 async function findExistingPrompts(ctx) {
     const found = [];
     for (const fixture of DEMO_PROMPTS) {
         const response = await ctx.client.prompts.listPrompts({
             Authorization: ctx.authHeader,
             page_size: 100,
-            filters: { name: { operator: 'iexact', value: [fixture.name] } },
+            filters: { name: { operator: '', value: [fixture.name] } },
         });
         for (const row of response.results ?? []) {
             if (row.id && row.name === fixture.name) {

package/dist/lib/demo/trace-fixtures.d.ts

@@ -1,10 +1,19 @@
 /**
- * Frozen snapshot of the demo traces, supplied by the team as ready-to-POST OTLP v2
- * bodies (the `trace-bodies/` dataset: a 22-span, 6-LLM-call multi-agent AI Service
- * Desk run across two tenants). Source of truth for the traces portion of `respan demo`.
+ * Frozen snapshot of the demo traces as ready-to-POST OTLP v2 bodies: a multi-agent
+ * AI Service Desk run across two tenants, 17 spans each. Four agents (triage,
+ * identity, knowledge, notification) hand off to each other, each making one
+ * gpt-6.1-sol call and one tool call, plus a RAG embedding. Source of truth for the
+ * traces portion of `respan demo`.
  *
- * Each `body` is a complete OTLP/JSON payload for `POST /api/v2/traces`, captured
- * VERBATIM. The seeder (`seed-traces.ts`) re-stamps fresh trace/span ids and recent
+ * Span names follow the SDKs' semantic style (`llm.<model>`, `agent.<name>`,
+ * `tool.<name>`, `handoff.<from>_to_<to>`, `embedding`; see
+ * contribution/writing-instrumentations.md), and handoff spans carry
+ * `respan.entity.log_type: handoff`. Derived from the team's original
+ * `trace-bodies/` dataset by dropping the Vercel AI SDK wrapper spans
+ * (`ai.generateText`, `ai.embed`) and moving the LLM calls to gpt-6.1-sol.
+ *
+ * Each `body` is a complete OTLP/JSON payload for `POST /api/v2/traces`. The
+ * seeder (`seed-traces.ts`) re-stamps fresh trace/span ids and recent
  * timestamps on each fresh seed, and sets the root span's name to `workflow` (below)
  * so it shows in the dashboard Workflow column and is unique per trace — the dataset
  * repeats some scenarios with a byte-identical root span, and a unique root name keeps