@vostride/agent-qa-analytics 0.2.3 → 0.2.4

package/dist/index.d.cts

@@ -12,33 +12,14 @@ import { RunEventEnvelope } from '@vostride/agent-qa-schema';
  */
 declare const ANALYTICS_VOCABULARY_META_KEY = "analyticsVocabulary";
 declare const ANALYTICS_KNOWN_ID_MARKER = "known-id";
-/**
- * The known-id fields' guards, as FUNCTIONS a host can call (398-10).
- *
- * Published beside the schemas because an emitter has to make the same decision the schema makes
- * and has to make it BEFORE capture: nothing parses an event on the way to the transport, so a
- * foreign string put on `run_id` is not refused, it is SENT — and `run_id` is a known-id codec
- * precisely so that cannot happen. A host filtering ids for itself would need `@vostride/agent-qa-ids`,
- * which the surface firewall does not admit; asking the package that owns the union is the route
- * that exists. Anything that is not a canonical id becomes an absence, which every field allows.
- */
 declare function analyticsRunId(value: unknown): string | undefined;
 declare function analyticsTestId(value: unknown): string | undefined;
 declare function analyticsSuiteId(value: unknown): string | undefined;
-/**
- * WHICH HOST EMITTED, and deliberately NOT the 397 D-04 surface roster.
- *
- * 2026-08-17. The roster answers "which invocation doors does the parity suite measure" and is
- * pinned closed at `chat` and `mcp`. This list answers a different question — which process sent
- * the event — and `cli` and `daemon` are real answers to it while being no kind of surface. Tying
- * the two would make a roster change an analytics schema change for no reason, and would make this
- * list wrong the moment a host emits that is not a door.
- */
 declare const ANALYTICS_EMITTING_HOSTS: readonly ["cli", "chat", "mcp", "daemon"];
 declare const ANALYTICS_RUNTIME_CONTEXTS: readonly ["user", "ci"];
 declare const ANALYTICS_AGENT_PRODUCTS: readonly ["claude_code", "cursor", "gemini_cli", "augment", "goose", "opencode", "codex", "cline", "amp", "unknown"];
 declare const ANALYTICS_TRIGGER_SOURCES: readonly ["cli", "chat", "mcp", "daemon", "unknown"];
-declare const ANALYTICS_RUNNERS: readonly ["local", "browserstack", "unknown"];
+declare const ANALYTICS_RUNNERS: readonly ["local", "unknown"];
 declare const ANALYTICS_PLATFORMS: readonly ["web", "android", "ios", "unknown"];
 declare const ANALYTICS_RUN_STATUSES: readonly ["passed", "failed", "skipped", "cancelled", "timeout", "unknown"];
 declare const ANALYTICS_SUITE_EXECUTION_MODES: readonly ["sequential", "parallel", "unknown"];
@@ -59,31 +40,8 @@ declare const ANALYTICS_CHAT_END_REASONS: readonly ["exit", "interrupt", "error"
  * thing a second transcription does is survive a rename that the first one did not.
  */
 declare const ANALYTICS_MCP_TOOL_NAMES: [string, ...string[]];
-/**
- * The membership, in the order D-18 states it.
- *
- * The names keep the `agent-qa.` prefix the v33 set used: the events land in a project shared with
- * nothing else today, but a prefix costs nothing and un-prefixing later is a rename of history.
- */
 declare const ANALYTICS_EVENT_NAMES: readonly ["agent-qa.test_run.completed", "agent-qa.suite_run.completed", "agent-qa.chat.session.completed", "agent-qa.chat.turn.completed", "agent-qa.daemon.job.completed", "agent-qa.mcp.server.lifecycle", "agent-qa.mcp.tool.invoked", "agent-qa.init.completed", "agent-qa.explain.answered", "agent-qa.explain.abstained"];
 type AnalyticsEventName = (typeof ANALYTICS_EVENT_NAMES)[number];
-/**
- * The v33 names that are NOT members, listed rather than merely absent.
- *
- * 2026-08-17 (Phase 398 plan 03, D-18 · RESEARCH Open Question 2). Two different reasons:
- *
- *   `analytics.initialized` and `analytics.test_event` were TRANSPORT SELF-TESTS — an event whose
- *   only content is "the thing that sends events works" is a diagnostic, and shipping it as product
- *   signal means every dashboard has to remember to exclude it. Dropped outright; the zero-network
- *   differential in plan 06 is the same claim, proven rather than reported.
- *
- *   The three `dashboard.*` rows are dropped BECAUSE THE DASHBOARD IS BEING REBUILT. M5 re-adds
- *   what it needs against this port, which is the right moment to decide what a rebuilt dashboard
- *   is actually worth measuring — carrying the v1 answers forward would have pre-decided it.
- *
- * RETUNE: a name re-added here must be REMOVED from this list in the same change. The disjointness
- * cell fires if it appears in both, so the two lists cannot quietly disagree.
- */
 declare const RETIRED_V33_EVENT_NAMES: readonly ["agent-qa.analytics.initialized", "agent-qa.analytics.test_event", "agent-qa.dashboard.opened", "agent-qa.dashboard.live_mode.started", "agent-qa.dashboard.entity.created"];
 declare const ANALYTICS_EVENT_SCHEMA_BY_NAME: {
     readonly 'agent-qa.test_run.completed': z.ZodObject<{
@@ -125,7 +83,6 @@ declare const ANALYTICS_EVENT_SCHEMA_BY_NAME: {
             runner: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
                 local: "local";
-                browserstack: "browserstack";
             }>>;
             platform: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
@@ -217,7 +174,6 @@ declare const ANALYTICS_EVENT_SCHEMA_BY_NAME: {
             runner: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
                 local: "local";
-                browserstack: "browserstack";
             }>>;
             platform: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
@@ -619,7 +575,6 @@ declare const ANALYTICS_EVENT_MEMBERS: readonly [z.ZodObject<{
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -710,7 +665,6 @@ declare const ANALYTICS_EVENT_MEMBERS: readonly [z.ZodObject<{
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -1103,7 +1057,6 @@ declare const AgentQaAnalyticsEventSchema: z.ZodDiscriminatedUnion<readonly [z.Z
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -1194,7 +1147,6 @@ declare const AgentQaAnalyticsEventSchema: z.ZodDiscriminatedUnion<readonly [z.Z
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -1606,20 +1558,9 @@ interface AnalyticsPort<TEvent extends AnalyticsEventEnvelope = AnalyticsEventEn
     shutdown(): Promise<void>;
 }
 interface AnalyticsPortOptions {
-    /** Absent when opted out or keyless: the port then drops every capture (447-04, D-08). */
+    /** Absent when opted out or keyless: the port then drops every capture. */
     readonly transport?: AnalyticsTransport;
     readonly identity: AnalyticsIdentityResolver;
-    /**
-     * How long `shutdown` will wait for the transport before releasing its caller (T-398-35 / WR-02).
-     *
-     * A host calls `shutdown` on its way OUT — at a terminal exit, in a `finally`, on the error path.
-     * Whatever it waits for is time a person spends looking at a terminal that has already finished
-     * its work. posthog-node's own shutdown defaults to 30 000 ms and races retriable flushes against
-     * it, so an unreachable network turns a completed run into half a minute of dead prompt.
-     *
-     * The default is deliberately small. This is the LAST thing a process does; delivering the final
-     * batch is worth a couple of seconds and no more.
-     */
     readonly shutdownTimeoutMs?: number;
 }
 declare function createAnalyticsPort<TEvent extends AnalyticsEventEnvelope = AnalyticsEventEnvelope>(options: AnalyticsPortOptions): AnalyticsPort<TEvent>;
@@ -1636,15 +1577,6 @@ interface AnalyticsMaskingContext {
  */
 declare function maskEventForSend(payload: AnalyticsCapturePayload, context: AnalyticsMaskingContext | undefined): AnalyticsCapturePayload;
 
-/**
- * The subset of the PostHog client this transport uses.
- *
- * `flush` is REQUIRED, not optional, and that is the whole content of the fix (398-15, CR-01): the
- * interface previously declared only `capture`/`shutdown`, so the type system could not express the
- * correct per-boundary call and the transport reached for `shutdown` instead. An optional member
- * with a shutdown fallback would reinstate the same defect behind a spelling. posthog-node 5.33.2
- * exposes both. The contract being honoured is stated at `port.ts:49-51`.
- */
 interface PosthogAnalyticsClient {
     capture(input: {
         distinctId: string;
@@ -1658,14 +1590,6 @@ interface PosthogTransportOptions {
     readonly projectKey: string;
     readonly host: string;
     readonly disableGeoip?: boolean;
-    /**
-     * posthog-node's own `fetch` option, passed straight through.
-     *
-     * 2026-08-17 (Phase 398 plan 03): this exists for plan 06's sandboxed-sink arm of the zero-network
-     * differential. posthog-node 5.33.2 sends through `this.options.fetch ?? fetch`, so injecting here
-     * observes the SHIPPED send path rather than a parallel one built for the test — which is the
-     * difference between measuring the product and measuring the fixture.
-     */
     readonly fetch?: PostHogOptions['fetch'];
     /** The host's declared-secret mask, applied at the send seam. Absent means no masking. */
     readonly maskingContext?: AnalyticsMaskingContext;
@@ -1688,10 +1612,6 @@ interface ComposeAnalyticsOptions {
     readonly identity?: AnalyticsIdentityResolver;
     readonly projectKey?: string;
     readonly projectHost?: string;
-    /**
-     * The host's declared-secret mask, which the send seam applies (D-19, plan 06). It reaches only
-     * the opted-IN arm: the deny arm has no transport, so there is no payload to mask.
-     */
     readonly maskingContext?: AnalyticsMaskingContext;
     /** Replaces the transport on the OPTED-IN arm only. Never consulted once the answer is deny. */
     readonly transportOverride?: AnalyticsTransport;

package/dist/index.d.ts

@@ -12,33 +12,14 @@ import { RunEventEnvelope } from '@vostride/agent-qa-schema';
  */
 declare const ANALYTICS_VOCABULARY_META_KEY = "analyticsVocabulary";
 declare const ANALYTICS_KNOWN_ID_MARKER = "known-id";
-/**
- * The known-id fields' guards, as FUNCTIONS a host can call (398-10).
- *
- * Published beside the schemas because an emitter has to make the same decision the schema makes
- * and has to make it BEFORE capture: nothing parses an event on the way to the transport, so a
- * foreign string put on `run_id` is not refused, it is SENT — and `run_id` is a known-id codec
- * precisely so that cannot happen. A host filtering ids for itself would need `@vostride/agent-qa-ids`,
- * which the surface firewall does not admit; asking the package that owns the union is the route
- * that exists. Anything that is not a canonical id becomes an absence, which every field allows.
- */
 declare function analyticsRunId(value: unknown): string | undefined;
 declare function analyticsTestId(value: unknown): string | undefined;
 declare function analyticsSuiteId(value: unknown): string | undefined;
-/**
- * WHICH HOST EMITTED, and deliberately NOT the 397 D-04 surface roster.
- *
- * 2026-08-17. The roster answers "which invocation doors does the parity suite measure" and is
- * pinned closed at `chat` and `mcp`. This list answers a different question — which process sent
- * the event — and `cli` and `daemon` are real answers to it while being no kind of surface. Tying
- * the two would make a roster change an analytics schema change for no reason, and would make this
- * list wrong the moment a host emits that is not a door.
- */
 declare const ANALYTICS_EMITTING_HOSTS: readonly ["cli", "chat", "mcp", "daemon"];
 declare const ANALYTICS_RUNTIME_CONTEXTS: readonly ["user", "ci"];
 declare const ANALYTICS_AGENT_PRODUCTS: readonly ["claude_code", "cursor", "gemini_cli", "augment", "goose", "opencode", "codex", "cline", "amp", "unknown"];
 declare const ANALYTICS_TRIGGER_SOURCES: readonly ["cli", "chat", "mcp", "daemon", "unknown"];
-declare const ANALYTICS_RUNNERS: readonly ["local", "browserstack", "unknown"];
+declare const ANALYTICS_RUNNERS: readonly ["local", "unknown"];
 declare const ANALYTICS_PLATFORMS: readonly ["web", "android", "ios", "unknown"];
 declare const ANALYTICS_RUN_STATUSES: readonly ["passed", "failed", "skipped", "cancelled", "timeout", "unknown"];
 declare const ANALYTICS_SUITE_EXECUTION_MODES: readonly ["sequential", "parallel", "unknown"];
@@ -59,31 +40,8 @@ declare const ANALYTICS_CHAT_END_REASONS: readonly ["exit", "interrupt", "error"
  * thing a second transcription does is survive a rename that the first one did not.
  */
 declare const ANALYTICS_MCP_TOOL_NAMES: [string, ...string[]];
-/**
- * The membership, in the order D-18 states it.
- *
- * The names keep the `agent-qa.` prefix the v33 set used: the events land in a project shared with
- * nothing else today, but a prefix costs nothing and un-prefixing later is a rename of history.
- */
 declare const ANALYTICS_EVENT_NAMES: readonly ["agent-qa.test_run.completed", "agent-qa.suite_run.completed", "agent-qa.chat.session.completed", "agent-qa.chat.turn.completed", "agent-qa.daemon.job.completed", "agent-qa.mcp.server.lifecycle", "agent-qa.mcp.tool.invoked", "agent-qa.init.completed", "agent-qa.explain.answered", "agent-qa.explain.abstained"];
 type AnalyticsEventName = (typeof ANALYTICS_EVENT_NAMES)[number];
-/**
- * The v33 names that are NOT members, listed rather than merely absent.
- *
- * 2026-08-17 (Phase 398 plan 03, D-18 · RESEARCH Open Question 2). Two different reasons:
- *
- *   `analytics.initialized` and `analytics.test_event` were TRANSPORT SELF-TESTS — an event whose
- *   only content is "the thing that sends events works" is a diagnostic, and shipping it as product
- *   signal means every dashboard has to remember to exclude it. Dropped outright; the zero-network
- *   differential in plan 06 is the same claim, proven rather than reported.
- *
- *   The three `dashboard.*` rows are dropped BECAUSE THE DASHBOARD IS BEING REBUILT. M5 re-adds
- *   what it needs against this port, which is the right moment to decide what a rebuilt dashboard
- *   is actually worth measuring — carrying the v1 answers forward would have pre-decided it.
- *
- * RETUNE: a name re-added here must be REMOVED from this list in the same change. The disjointness
- * cell fires if it appears in both, so the two lists cannot quietly disagree.
- */
 declare const RETIRED_V33_EVENT_NAMES: readonly ["agent-qa.analytics.initialized", "agent-qa.analytics.test_event", "agent-qa.dashboard.opened", "agent-qa.dashboard.live_mode.started", "agent-qa.dashboard.entity.created"];
 declare const ANALYTICS_EVENT_SCHEMA_BY_NAME: {
     readonly 'agent-qa.test_run.completed': z.ZodObject<{
@@ -125,7 +83,6 @@ declare const ANALYTICS_EVENT_SCHEMA_BY_NAME: {
             runner: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
                 local: "local";
-                browserstack: "browserstack";
             }>>;
             platform: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
@@ -217,7 +174,6 @@ declare const ANALYTICS_EVENT_SCHEMA_BY_NAME: {
             runner: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
                 local: "local";
-                browserstack: "browserstack";
             }>>;
             platform: z.ZodOptional<z.ZodEnum<{
                 unknown: "unknown";
@@ -619,7 +575,6 @@ declare const ANALYTICS_EVENT_MEMBERS: readonly [z.ZodObject<{
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -710,7 +665,6 @@ declare const ANALYTICS_EVENT_MEMBERS: readonly [z.ZodObject<{
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -1103,7 +1057,6 @@ declare const AgentQaAnalyticsEventSchema: z.ZodDiscriminatedUnion<readonly [z.Z
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -1194,7 +1147,6 @@ declare const AgentQaAnalyticsEventSchema: z.ZodDiscriminatedUnion<readonly [z.Z
         runner: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
             local: "local";
-            browserstack: "browserstack";
         }>>;
         platform: z.ZodOptional<z.ZodEnum<{
             unknown: "unknown";
@@ -1606,20 +1558,9 @@ interface AnalyticsPort<TEvent extends AnalyticsEventEnvelope = AnalyticsEventEn
     shutdown(): Promise<void>;
 }
 interface AnalyticsPortOptions {
-    /** Absent when opted out or keyless: the port then drops every capture (447-04, D-08). */
+    /** Absent when opted out or keyless: the port then drops every capture. */
     readonly transport?: AnalyticsTransport;
     readonly identity: AnalyticsIdentityResolver;
-    /**
-     * How long `shutdown` will wait for the transport before releasing its caller (T-398-35 / WR-02).
-     *
-     * A host calls `shutdown` on its way OUT — at a terminal exit, in a `finally`, on the error path.
-     * Whatever it waits for is time a person spends looking at a terminal that has already finished
-     * its work. posthog-node's own shutdown defaults to 30 000 ms and races retriable flushes against
-     * it, so an unreachable network turns a completed run into half a minute of dead prompt.
-     *
-     * The default is deliberately small. This is the LAST thing a process does; delivering the final
-     * batch is worth a couple of seconds and no more.
-     */
     readonly shutdownTimeoutMs?: number;
 }
 declare function createAnalyticsPort<TEvent extends AnalyticsEventEnvelope = AnalyticsEventEnvelope>(options: AnalyticsPortOptions): AnalyticsPort<TEvent>;
@@ -1636,15 +1577,6 @@ interface AnalyticsMaskingContext {
  */
 declare function maskEventForSend(payload: AnalyticsCapturePayload, context: AnalyticsMaskingContext | undefined): AnalyticsCapturePayload;
 
-/**
- * The subset of the PostHog client this transport uses.
- *
- * `flush` is REQUIRED, not optional, and that is the whole content of the fix (398-15, CR-01): the
- * interface previously declared only `capture`/`shutdown`, so the type system could not express the
- * correct per-boundary call and the transport reached for `shutdown` instead. An optional member
- * with a shutdown fallback would reinstate the same defect behind a spelling. posthog-node 5.33.2
- * exposes both. The contract being honoured is stated at `port.ts:49-51`.
- */
 interface PosthogAnalyticsClient {
     capture(input: {
         distinctId: string;
@@ -1658,14 +1590,6 @@ interface PosthogTransportOptions {
     readonly projectKey: string;
     readonly host: string;
     readonly disableGeoip?: boolean;
-    /**
-     * posthog-node's own `fetch` option, passed straight through.
-     *
-     * 2026-08-17 (Phase 398 plan 03): this exists for plan 06's sandboxed-sink arm of the zero-network
-     * differential. posthog-node 5.33.2 sends through `this.options.fetch ?? fetch`, so injecting here
-     * observes the SHIPPED send path rather than a parallel one built for the test — which is the
-     * difference between measuring the product and measuring the fixture.
-     */
     readonly fetch?: PostHogOptions['fetch'];
     /** The host's declared-secret mask, applied at the send seam. Absent means no masking. */
     readonly maskingContext?: AnalyticsMaskingContext;
@@ -1688,10 +1612,6 @@ interface ComposeAnalyticsOptions {
     readonly identity?: AnalyticsIdentityResolver;
     readonly projectKey?: string;
     readonly projectHost?: string;
-    /**
-     * The host's declared-secret mask, which the send seam applies (D-19, plan 06). It reaches only
-     * the opted-IN arm: the deny arm has no transport, so there is no payload to mask.
-     */
     readonly maskingContext?: AnalyticsMaskingContext;
     /** Replaces the transport on the OPTED-IN arm only. Never consulted once the answer is deny. */
     readonly transportOverride?: AnalyticsTransport;

package/dist/index.js

@@ -12,21 +12,7 @@ var BestEffortAnalyticsPort = class {
     this.identity = options.identity;
     this.shutdownTimeoutMs = options.shutdownTimeoutMs ?? DEFAULT_ANALYTICS_SHUTDOWN_TIMEOUT_MS;
   }
-  /**
-   * There is NO try/catch here, and the absence is deliberate — measured, not assumed.
-   *
-   * 2026-08-17 (Phase 398 plan 03, mutation leg M6). This method was first written with the v1
-   * module's `try { ... } catch {}` wrapper around the body. Deleting that wrapper outright left
-   * every cell green, including the one named "never throws into the host", because there is no
-   * synchronous throw for it to catch: an `async` function body's throw — including one out of the
-   * identity resolver, the only caller-supplied code reachable from here — becomes a REJECTED
-   * PROMISE, never a synchronous exception. The wrapper read like the boundary and guarded nothing.
-   *
-   * The real boundary is the `.catch` below, attached in the same tick the promise is created so a
-   * rejection cannot become an unhandled rejection even if `flush()` is never called — which is the
-   * normal case for a host that emits on a path it does not await. Leg M8 removes that `.catch` and
-   * reds; that is the guard this method actually has.
-   */
+  // An async body never throws synchronously; the `.catch` below, attached at once, is the guard.
   capture(event) {
     const transport = this.transport;
     if (transport === void 0) return;
@@ -43,17 +29,7 @@ var BestEffortAnalyticsPort = class {
       })
     );
   }
-  /**
-   * EDGE ANLY-01/empty. A flush with nothing captured touches the transport at ALL — not "makes no
-   * network call", but makes no call. The distinction matters because `flush` on the PostHog
-   * transport is a send, so a host that flushes on every command return would otherwise poke the
-   * wire once per invocation whether or not anything happened. Zero captures in, zero calls out,
-   * and the promise still resolves.
-   *
-   * 2026-10-21 (447-07, D-20): flush awaits the local captures and STARTS the send without awaiting
-   * it, so a stalled network never holds a run's verdict or a command's return; `shutdown` waits
-   * for the started sends inside its bound.
-   */
+  // Zero captures make no transport call; `flush` starts the send without awaiting it.
   async flush() {
     const transport = this.transport;
     if (transport === void 0) return;
@@ -150,15 +126,7 @@ var PosthogTransport = class {
       ...options.fetch ? { fetch: options.fetch } : {}
     });
   }
-  /**
-   * THE SEND CHOKE POINT. Masking is the first thing that happens here and it happens exactly once
-   * (a cell counts the call sites in shipped source and refuses any number but one).
-   *
-   * `flush`/`shutdown` are not second seams: everything they drain arrived through this method, so
-   * masking here ranges the whole queue. `is_internal` is added AFTER the mask because it is a
-   * boolean this file writes — there is no caller string in it to mask. It is an event property,
-   * sent only when true (447-07, D-13).
-   */
+  // The one masking site; `is_internal` is added after the mask because this file writes it.
   capture(payload) {
     let masked;
     try {
@@ -267,7 +235,7 @@ var ANALYTICS_AGENT_PRODUCTS = [
   "unknown"
 ];
 var ANALYTICS_TRIGGER_SOURCES = ["cli", "chat", "mcp", "daemon", "unknown"];
-var ANALYTICS_RUNNERS = ["local", "browserstack", "unknown"];
+var ANALYTICS_RUNNERS = ["local", "unknown"];
 var ANALYTICS_PLATFORMS = ["web", "android", "ios", "unknown"];
 var ANALYTICS_RUN_STATUSES = [
   "passed",
@@ -340,10 +308,6 @@ var RunCompletionShape = {
   failure_category: z.enum(ANALYTICS_FAILURE_CATEGORIES).optional(),
   duration_ms: NonNegativeNumber.optional(),
   run_id: RunIdSchema.optional(),
-  // 2026-08-28 (405-13, D-21/DETL-06). The parent-link property was deleted here. It was declared
-  // with no producer anywhere in this package — 402-09 put one run row per run and moved member
-  // identity onto handles, and 405-07 then deleted the column it named — so it could only ever
-  // have travelled as `undefined`. Same disposition and same reason as the healing counter below.
   step_count: NonNegativeInteger.optional(),
   passed_step_count: NonNegativeInteger.optional(),
   failed_step_count: NonNegativeInteger.optional(),
@@ -770,10 +734,7 @@ function createAnalyticsRunSubscriber(options) {
       retry_count: record.retryCount,
       is_flaky: record.retryCount !== void 0 ? status === "passed" && record.retryCount > 0 : void 0,
       ...steps,
-      // 405 D-07. Spread in only when the member measured at least one step. `definedProperties`
-      // would drop three `undefined`s anyway, but building them unconditionally would mean writing
-      // `input_tokens: tokens?.input ?? 0` somewhere — and that `?? 0` is exactly the fabricated
-      // measurement this whole path refuses to make.
+      // Spread in only when a step is measured; a `?? 0` here would fabricate a measurement.
       ...record.steps.tokens === void 0 ? {} : {
         input_tokens: record.steps.tokens.input,
         output_tokens: record.steps.tokens.output,