@vexyo/core 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,11 @@
+# @vexyo/core
+
+Conformance and regression engine for [vexyo](https://github.com/vexyohq/vexyo) — testing Model
+Context Protocol (MCP) servers.
+
+Defines the `Rule` abstraction, the `Runner` (which owns the connection lifecycle over stdio and
+Streamable HTTP), the `RunResult` contract that reporters consume, and the golden-set regression
+engine (record + drift detection with deterministic, Prettier-stable goldens). Built on the
+official `@modelcontextprotocol/sdk`.
+
+Part of the [vexyo](https://github.com/vexyohq/vexyo) monorepo. Apache-2.0.

package/dist/index.d.ts

@@ -0,0 +1,400 @@
+import { Client } from '@modelcontextprotocol/sdk/client/index.js';
+import { Implementation, ServerCapabilities } from '@modelcontextprotocol/sdk/types.js';
+import { z } from 'zod';
+
+/**
+ * The public result contract consumed by every reporter.
+ *
+ * CLAUDE.md hard rule #7: reporters consume `RunResult` only; breaking this
+ * shape is a semver-major event. Keep it stable and additive.
+ */
+/**
+ * MCP spec versions this harness knows about. A run targets exactly one
+ * (CLAUDE.md hard rule #2 — spec versions never mix). Only the stable version
+ * is wired up today; `2026-07-28` is a scaffolding slot for the RC.
+ */
+type SpecVersion = '2025-11-25' | '2026-07-28';
+/** The stable spec version this build fully supports. */
+declare const STABLE_SPEC_VERSION: SpecVersion;
+type Severity = 'error' | 'warning' | 'info';
+type Category = 'initialization' | 'discovery' | 'error-semantics' | 'transport' | 'security' | 'regression';
+/**
+ * Outcome of running one rule:
+ * - `pass`  — rule ran and produced no findings.
+ * - `fail`  — rule produced at least one `error`-severity finding.
+ * - `warn`  — rule produced findings, but none above `warning`/`info` severity.
+ * - `skip`  — rule was not applicable (e.g. capability not advertised).
+ * - `error` — rule threw unexpectedly (server crash or harness bug).
+ */
+type RuleStatus = 'pass' | 'fail' | 'warn' | 'skip' | 'error';
+/** A single problem detected by a rule. A rule with zero findings passed. */
+interface Finding {
+    ruleId: string;
+    severity: Severity;
+    /** What is wrong. */
+    message: string;
+    /** What to do next (CLAUDE.md: every user-facing failure states the fix). */
+    remediation: string;
+    /** Spec section citation, e.g. "Base Protocol §Lifecycle". */
+    specRef: string;
+    /** Optional machine-readable context (offending payload, error, etc.). */
+    detail?: unknown;
+}
+interface RuleResult {
+    ruleId: string;
+    title: string;
+    category: Category;
+    severity: Severity;
+    specVersion: SpecVersion;
+    /** Spec section citation for this rule, surfaced by reporters. */
+    specRef: string;
+    status: RuleStatus;
+    /**
+     * Why the rule was skipped. A skip means either "not applicable" (capability
+     * absent) or "a prerequisite is unavailable" (e.g. `tools/list` failed, so
+     * rules that consume it skip rather than cascade errors).
+     */
+    skipReason?: string;
+    findings: Finding[];
+    durationMs: number;
+}
+interface RunTarget {
+    transport: 'stdio' | 'http';
+    /** Human-readable description of what we connected to. */
+    description: string;
+}
+interface RunSummary {
+    pass: number;
+    fail: number;
+    warn: number;
+    skip: number;
+    error: number;
+    total: number;
+}
+interface RunResult {
+    specVersion: SpecVersion;
+    target: RunTarget;
+    /** ISO-8601 timestamps. */
+    startedAt: string;
+    finishedAt: string;
+    results: RuleResult[];
+    summary: RunSummary;
+    /** 0 = pass, 1 = findings at/above threshold, 2 = harness/config error. */
+    exitCode: 0 | 1 | 2;
+}
+
+/** Which transport a connection uses, plus transport-specific facts rules may inspect. */
+type TransportInfo = {
+    kind: 'stdio';
+} | {
+    kind: 'http';
+    sessionId?: string;
+};
+/** How to spawn a stdio MCP server under test. */
+interface StdioTargetConfig {
+    command: string;
+    args?: string[];
+    cwd?: string;
+    env?: Record<string, string>;
+}
+/** How to reach a running Streamable HTTP MCP server. */
+interface HttpTargetConfig {
+    url: string;
+    headers?: Record<string, string>;
+}
+/** A connection target: exactly one transport (CLAUDE.md hard rule #2 spirit). */
+type ConnectTarget = {
+    transport: 'stdio';
+    stdio: StdioTargetConfig;
+} | {
+    transport: 'http';
+    http: HttpTargetConfig;
+};
+interface ConnectedClient {
+    client: Client;
+    transport: TransportInfo;
+    /** Closes the client connection (and, for stdio, the spawned server process). */
+    close: () => Promise<void>;
+}
+
+/**
+ * Everything a rule needs to make its assessment. The runner owns the
+ * connection lifecycle; a rule never spawns processes or manages sockets
+ * (CLAUDE.md hard rule #1 + architecture note).
+ */
+interface RuleContext {
+    /** Connected MCP client (handshake already completed). */
+    readonly client: Client;
+    /** Server identity captured during initialization. */
+    readonly serverInfo: Implementation | undefined;
+    /** Capabilities the server advertised during negotiation. */
+    readonly capabilities: ServerCapabilities | undefined;
+    /** The transport in use, plus transport-specific facts (e.g. HTTP session id). */
+    readonly transport: TransportInfo;
+    readonly specVersion: SpecVersion;
+}
+/**
+ * A rule is a pure, declarative conformance check. It returns the findings it
+ * detected; an empty array means the server passed. Applicability is signalled
+ * by throwing {@link SkipRule}.
+ */
+interface Rule {
+    readonly id: string;
+    /** Exactly one spec version (CLAUDE.md hard rule #2). */
+    readonly specVersion: SpecVersion;
+    readonly category: Category;
+    readonly severity: Severity;
+    readonly title: string;
+    /** Spec section citation surfaced to users, e.g. "Base Protocol §Lifecycle". */
+    readonly specRef: string;
+    run(ctx: RuleContext): Promise<Finding[]>;
+}
+/**
+ * Thrown by a rule to declare itself not applicable to this server (e.g. the
+ * relevant capability was never advertised). The runner records a `skip`
+ * rather than a pass or fail.
+ */
+declare class SkipRule extends Error {
+    readonly reason: string;
+    constructor(reason: string);
+}
+/** Build a {@link Finding}, prefilling identity fields from the rule. */
+declare function finding(rule: Pick<Rule, 'id' | 'severity' | 'specRef'>, message: string, remediation: string, detail?: unknown): Finding;
+
+/** Rules that target the given spec version, in registration order. */
+declare function rulesForSpecVersion(version: SpecVersion): Rule[];
+/** The full catalog (all versions) — used for introspection/tests. */
+declare function allRules(): readonly Rule[];
+
+/**
+ * Spawn the target server over stdio and complete the MCP handshake using the
+ * official SDK (CLAUDE.md hard rule #1). Over stdio the client transport owns
+ * the spawned process, so `close()` also terminates the server. Callers must
+ * always `close()` the returned handle to avoid leaking the child process.
+ */
+declare function connectStdio(target: StdioTargetConfig): Promise<ConnectedClient>;
+
+/**
+ * Connect to a running Streamable HTTP MCP server and complete the handshake
+ * using the official SDK. The server is not ours to manage — over HTTP the
+ * runner owns only the connection: `connect()` performs initialize (and the SDK
+ * captures the `Mcp-Session-Id` the server issues), `close()` ends the session
+ * (the SDK sends the terminating `DELETE`). Rules never touch the session or
+ * HTTP verbs; the negotiated session id is surfaced via {@link ConnectedClient.transport}.
+ */
+declare function connectHttp(target: HttpTargetConfig): Promise<ConnectedClient>;
+
+/** Connect to a target over whichever transport it declares. */
+declare function connectTarget(target: ConnectTarget): Promise<ConnectedClient>;
+
+interface RunSuiteOptions {
+    specVersion: SpecVersion;
+    target: ConnectTarget;
+    /** Severity at/above which findings cause a non-zero exit. Default `error`. */
+    failOn?: Severity;
+    /**
+     * Optional extra checks run against the *same* connection after the
+     * conformance rules (e.g. regression drift). Their results are appended.
+     */
+    extraChecks?: (ctx: RuleContext) => Promise<RuleResult[]>;
+}
+/**
+ * Connect to the target server, run every rule for the requested spec version
+ * (plus any extra checks), and assemble a {@link RunResult}. Connection/
+ * handshake failures throw (the CLI maps them to exit code 2); per-rule
+ * failures are captured as findings.
+ */
+declare function runSuite(opts: RunSuiteOptions): Promise<RunResult>;
+/**
+ * Run a set of rules against an already-connected context. Extracted from
+ * {@link runSuite} so rule-outcome handling is unit-testable without a live
+ * server connection.
+ */
+declare function runRules(ctx: RuleContext, rules: readonly Rule[]): Promise<RuleResult[]>;
+declare function summarizeResults(results: RuleResult[]): RunSummary;
+/**
+ * Exit 1 if any rule errored, or any finding is at/above the `failOn` severity;
+ * otherwise 0. Harness/config errors (exit 2) surface as thrown exceptions.
+ */
+declare function computeExitCode(results: RuleResult[], failOn: Severity): 0 | 1;
+
+/**
+ * Normalizers collapse volatile values (timestamps, ids, paths) to stable
+ * placeholders so a re-recorded golden matches. Both `record` and the
+ * regression comparison run the *same* pipeline, so a normalized field can
+ * never register as drift.
+ */
+type NormalizerFn = (value: unknown) => unknown;
+/** A normalizer is either a builtin name or an inline `{ name, apply }` object. */
+interface NormalizerObject {
+    name: string;
+    apply: NormalizerFn;
+}
+type NormalizerRef = string | NormalizerObject;
+declare const BUILTIN_NORMALIZER_NAMES: readonly string[];
+declare function normalizerName(ref: NormalizerRef): string;
+/** Apply a normalizer pipeline (in order) to a value. */
+declare function applyNormalizers(value: unknown, refs: readonly NormalizerRef[]): unknown;
+/**
+ * Given a changed field's before/after, return builtin normalizer names that
+ * would collapse it — i.e. whose pattern matches BOTH sides. This is what turns
+ * a noisy diff into "add this normalizer" guidance instead of blind re-record
+ * (CLAUDE.md hard rule #6).
+ */
+declare function suggestNormalizer(before: unknown, after: unknown): string[];
+
+/** One recorded invocation of a tool: a case name plus the arguments to send. */
+interface GoldenCaseSpec {
+    case: string;
+    arguments: Record<string, unknown>;
+}
+/** Recording plan for a single tool (explicit opt-in — see `record`). */
+interface GoldenToolSpec {
+    cases: GoldenCaseSpec[];
+    /** Overrides the default normalizers for this tool. */
+    normalizers?: NormalizerRef[];
+}
+/** The regression engine's view of the config (built by the CLI from zod). */
+interface GoldenConfig {
+    specVersion: string;
+    defaultNormalizers: NormalizerRef[];
+    /** Tools to record/compare, keyed by tool name. Empty = record nothing. */
+    tools: Record<string, GoldenToolSpec>;
+}
+
+/**
+ * Golden-file format contract. This becomes public the moment a user commits a
+ * golden, so it is versioned: bump {@link GOLDEN_FORMAT_VERSION} to evolve the
+ * shape, and readers reject a mismatched version with a clear error rather than
+ * silently misinterpreting old goldens.
+ */
+declare const GOLDEN_FORMAT_VERSION = 1;
+declare const GoldenManifestSchema: z.ZodObject<{
+    formatVersion: z.ZodLiteral<1>;
+    specVersion: z.ZodString;
+    server: z.ZodObject<{
+        name: z.ZodString;
+        version: z.ZodString;
+    }, z.core.$strip>;
+    tools: z.ZodArray<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
+    resources: z.ZodArray<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
+    prompts: z.ZodArray<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
+}, z.core.$strip>;
+type GoldenManifest = z.infer<typeof GoldenManifestSchema>;
+declare const GoldenCaseSchema: z.ZodObject<{
+    case: z.ZodString;
+    arguments: z.ZodRecord<z.ZodString, z.ZodUnknown>;
+    normalizers: z.ZodArray<z.ZodString>;
+    result: z.ZodUnknown;
+}, z.core.$strip>;
+type GoldenCase = z.infer<typeof GoldenCaseSchema>;
+declare const GoldenRecordingSchema: z.ZodObject<{
+    formatVersion: z.ZodLiteral<1>;
+    tool: z.ZodString;
+    cases: z.ZodArray<z.ZodObject<{
+        case: z.ZodString;
+        arguments: z.ZodRecord<z.ZodString, z.ZodUnknown>;
+        normalizers: z.ZodArray<z.ZodString>;
+        result: z.ZodUnknown;
+    }, z.core.$strip>>;
+}, z.core.$strip>;
+type GoldenRecording = z.infer<typeof GoldenRecordingSchema>;
+/** The full committed golden set: one manifest + one recording file per tool. */
+interface GoldenSet {
+    manifest: GoldenManifest;
+    recordings: GoldenRecording[];
+}
+declare const FieldDiffSchema: z.ZodObject<{
+    path: z.ZodString;
+    before: z.ZodOptional<z.ZodUnknown>;
+    after: z.ZodOptional<z.ZodUnknown>;
+}, z.core.$strip>;
+type FieldDiff = z.infer<typeof FieldDiffSchema>;
+type RegressionKind = 'schema' | 'behavioral' | 'coverage';
+declare const RegressionDetailSchema: z.ZodObject<{
+    kind: z.ZodEnum<{
+        schema: "schema";
+        behavioral: "behavioral";
+        coverage: "coverage";
+    }>;
+    target: z.ZodObject<{
+        type: z.ZodEnum<{
+            tool: "tool";
+            resource: "resource";
+            prompt: "prompt";
+        }>;
+        name: z.ZodString;
+        case: z.ZodOptional<z.ZodString>;
+    }, z.core.$strip>;
+    change: z.ZodEnum<{
+        added: "added";
+        removed: "removed";
+        changed: "changed";
+    }>;
+    before: z.ZodOptional<z.ZodUnknown>;
+    after: z.ZodOptional<z.ZodUnknown>;
+    fieldDiffs: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        path: z.ZodString;
+        before: z.ZodOptional<z.ZodUnknown>;
+        after: z.ZodOptional<z.ZodUnknown>;
+    }, z.core.$strip>>>;
+    suggestedNormalizers: z.ZodOptional<z.ZodArray<z.ZodString>>;
+}, z.core.$strip>;
+type RegressionDetail = z.infer<typeof RegressionDetailSchema>;
+
+/**
+ * Capture a golden set from a connected server: a schema manifest (always safe —
+ * read-only list calls) plus behavioral recordings for the explicitly-configured
+ * tools only. A tool absent from `cfg.tools` is never invoked (opt-in per
+ * CLAUDE.md side-effect safety).
+ */
+declare function recordGoldens(client: Client, cfg: GoldenConfig): Promise<GoldenSet>;
+
+/**
+ * Compare the server's current behavior against a committed golden set and
+ * return one {@link RuleResult} per drift (plus a `pass` per matching case).
+ * Three drift classes, each with its own severity:
+ *  - schema     (error):   a definition changed
+ *  - behavioral (error):   a recorded call's normalized output changed
+ *  - coverage   (error/warn): a golden's target was removed / a live target has no golden
+ */
+declare function runRegression(client: Client, golden: GoldenSet, cfg: GoldenConfig): Promise<RuleResult[]>;
+
+/** Raised for missing/malformed/version-mismatched golden files (exit 2). */
+declare class GoldenError extends Error {
+    constructor(message: string, cause?: unknown);
+}
+/** Write the golden set as `manifest.json` + `recordings/<tool>.json`, deterministically. */
+declare function writeGoldenSet(dir: string, set: GoldenSet): Promise<string[]>;
+/** Read and validate a golden set. Throws {@link GoldenError} with a clear message. */
+declare function readGoldenSet(dir: string): Promise<GoldenSet>;
+
+/**
+ * The single choke-point for golden-file determinism. Every golden is written
+ * through {@link stableStringify}, which recursively sorts object keys and emits
+ * JSON that is a **fixed point of Prettier** (2-space indent, trailing newline):
+ * running `prettier --check` on a freshly written golden makes no changes. This
+ * matters because users commit goldens into repos that run Prettier — our output
+ * must survive that byte-identically, not get reformatted on the next commit.
+ *
+ * The rule mirrors Prettier's JSON printer (with the default `objectWrap:
+ * "preserve"`): a container is printed on one line if that flat form fits within
+ * the print width at its column, otherwise it breaks one entry per line. Objects
+ * use `{ ... }` (inner spaces); arrays use `[...]`; a broken array of only
+ * numbers is packed ("fill") the way Prettier packs number lists.
+ */
+/** Deterministic, Prettier-stable JSON: sorted keys, 2-space indent, trailing newline. */
+declare function stableStringify(value: unknown): string;
+
+/**
+ * The single source of truth for the product name (CLAUDE.md: "the name lives
+ * in one constant pending final branding"). Rename here only.
+ */
+declare const BRAND: {
+    /** Display name of the product. */
+    readonly name: "vexyo";
+    /** CLI command / binary name. */
+    readonly bin: "vexyo";
+};
+
+export { BRAND, BUILTIN_NORMALIZER_NAMES, type Category, type ConnectTarget, type ConnectedClient, type FieldDiff, type Finding, GOLDEN_FORMAT_VERSION, type GoldenCase, type GoldenCaseSpec, type GoldenConfig, GoldenError, type GoldenManifest, GoldenManifestSchema, type GoldenRecording, GoldenRecordingSchema, type GoldenSet, type GoldenToolSpec, type HttpTargetConfig, type NormalizerFn, type NormalizerObject, type NormalizerRef, type RegressionDetail, RegressionDetailSchema, type RegressionKind, type Rule, type RuleContext, type RuleResult, type RuleStatus, type RunResult, type RunSuiteOptions, type RunSummary, type RunTarget, STABLE_SPEC_VERSION, type Severity, SkipRule, type SpecVersion, type StdioTargetConfig, type TransportInfo, allRules, applyNormalizers, computeExitCode, connectHttp, connectStdio, connectTarget, finding, normalizerName, readGoldenSet, recordGoldens, rulesForSpecVersion, runRegression, runRules, runSuite, stableStringify, suggestNormalizer, summarizeResults, writeGoldenSet };